A machine that stays on
The SDK talks to the company file over COM, so something Windows has to be running with QuickBooks installed — your server, a hosted instance at Right Networks, or a small VM we help you set up.
Services · integration
QuickBooks Desktop runs a meaningful share of American businesses between $5M and $50M, and it has no cloud API. Getting data out means the SDK, a Windows machine, and a company file somebody still opens on Tuesdays. It is roughly three times the work of the online edition, which is why we quote it separately.
Tell us your QuickBooks Desktop version, hosting, and file count. We will scope it.
The situation
Five hops instead of one, and one of them involves a machine that has to stay on.
The SDK talks to the company file over COM, so something Windows has to be running with QuickBooks installed — your server, a hosted instance at Right Networks, or a small VM we help you set up.
QBXML returns records in pages and the file locks under load. A full historical extract is measured in days rather than hours, and we schedule it around your working pattern.
Desktop files accumulate duplicate customers, merged-then-unmerged vendors, orphaned classes, and items pointing at deleted accounts. Cleaning that is most of the engagement.
Many groups run one file per entity with no consolidation. We extract each and consolidate in the graph, including intercompany elimination that currently happens in a spreadsheet.
Once the initial load is done, a nightly tie-out to the trial balance in each file, so divergence is caught rather than discovered.
Read-only, always, on Desktop. The file stays exactly as your bookkeeper left it, which matters more here than on a cloud system.
QuickBooks Online is a REST API and a mapping exercise. Desktop is an SDK over COM against a file that locks, on hardware you own, with a data model that has accumulated fifteen years of workarounds.
Quoting the two identically would mean either overcharging Online customers or discovering the gap mid-engagement on Desktop ones. We would rather state it plainly: Desktop starts at $9,500 against $6,500, and it takes three to four weeks rather than two.
The technical extraction is tedious but solved. What consumes the engagement is that a fifteen-year-old company file contains four versions of the same customer, vendors that were merged and then recreated, classes used for three incompatible purposes across different eras, and items pointing at accounts that no longer exist.
None of that stops QuickBooks working, because a bookkeeper who knows the file navigates around it. It does stop any downstream reporting being trustworthy, so it has to be resolved — and the resolution is a series of decisions only your team can make.
We do not modify your company file. No repairs, no merges, no condensing, no rebuilds. The cleanup happens in the graph, where it is reversible and logged, and your file stays exactly as it was.
That is a deliberate constraint. Desktop files are fragile, backups are inconsistent, and a botched merge inside QuickBooks is not something we would want to be responsible for.
Groups running one file per entity typically consolidate in Excel, monthly, by hand, with intercompany eliminated from memory. It is slow and it is the single most error-prone thing in their close.
Extracting every file into one graph makes consolidation continuous and the elimination explicit. For multi-file customers this is usually the outcome that justifies the engagement on its own.
Frequently not. Desktop’s inventory and job costing are better than Online’s, and companies that migrate for the API often find they gave up capability for connectivity they could have had anyway. We will give you an opinion rather than a recommendation to migrate.
Where to start
Version, hosting arrangement, file size, user count, and where the SDK connection will run. Occasionally the answer is that you need a small VM first.
Full history pulled over several days, scheduled outside your working hours because the file locks under load.
Duplicates, orphans, and class inconsistencies surfaced with proposed resolutions. Your team decides; we apply it in the graph, never in the file.
Nightly tie-out per file, consolidation where there are several, and the reporting you could not previously produce.
Questions
Tell us your version, hosting, and file count. We will scope it without touching your file.