There is no real API
Desktop exposes QBXML through an SDK that runs against the company file on a Windows machine. Extraction is paged, rate-limited, and occasionally has to be run overnight against a copy.
Migration · QuickBooks Desktop
Desktop and Online are treated as one line item by most vendors and they are not remotely the same job. Desktop has no modern API, the data lives in a file on a machine, and a decade of workarounds is usually encoded in the class list. Roughly three times the elapsed work of an Online conversion.
Version, entity count, inventory, and payroll history. We come back with a scope, a price, and a real timeline.
Why it is harder
Desktop exposes QBXML through an SDK that runs against the company file on a Windows machine. Extraction is paged, rate-limited, and occasionally has to be run overnight against a copy.
A .QBW on a specific PC, sometimes in a hosted Citrix environment, sometimes with a single-user lock that blocks extraction while anyone is working.
Department, location, and often entity encoded into one field because Desktop offered nowhere else. Untangling that into real dimensions is the highest-value part of the job.
Customers, vendors, items, and jobs with duplicates, inactive records still referenced by transactions, and sub-customers used as projects.
Desktop values inventory on average cost with its own quirks. Reproducing the valuation exactly, rather than approximately, is a specific piece of work.
Where Desktop payroll was used, year-to-date figures must reconcile to filed returns before anyone can rely on the new system in January.
A single-company Desktop conversion with two years of history runs six to ten weeks and is quoted after a diagnostic — typically between $28,000 and $55,000 depending on inventory, payroll history, and how many company files are being consolidated.
We quote after looking at the file rather than before, because the range within Desktop is wider than the gap between Desktop and Online. A clean single-user file with no inventory converts in six weeks. Three company files with Desktop payroll, average-cost inventory, and eight years of classes used as a chart of accounts is a different engagement entirely.
Extraction runs against a backup restored to a machine we control, never against your live file. That removes the single-user lock problem, means nobody has to stop working, and guarantees nothing we do can affect your books during the conversion.
In most Desktop files that have been in use for more than five years, the class list is doing several jobs at once — a department, a location, sometimes a whole entity, and often a project. It grew that way because Desktop offered one dimension and the business needed three.
Splitting that into proper dimensions is where the value of the conversion actually sits. Done well, you get department, location, and entity reporting that Desktop could never produce. Done carelessly, the classes are carried across as-is and you have paid to move a workaround into a system that did not need one. It is also the part that needs decisions from your controller rather than work from us, which is why it drives the timeline.
Right Networks, Ace Cloud, and similar hosting providers change the logistics rather than the work. We coordinate a backup with your host, which usually adds a few days at the start. Enterprise on a hosted desktop is otherwise identical to the on-premise case.
Intuit retires older Desktop versions on a rolling basis, and a discontinued version losing payroll and security updates is what turns a considered project into an urgent one. If your version has an announced end date, start the diagnostic at least two quarters ahead — Desktop conversions do not compress well.
Questions
We look at the actual file before quoting, because the range within Desktop is wider than the gap to Online.