Your QuickBooks Desktop history lives in a sealed, verifiable bundle. Your QuickBooks Online starts clean at the cutover date. Most QBD-to-QBO services call themselves migrations and move history forward, where it can silently change later. We don't.
A migration moves everything from one system to another and expects the destination to behave like the source. With QuickBooks Desktop and QuickBooks Online, that expectation fails. QBO is a different product with different rules, especially around how historical transactions are stored and recalculated. Forcing history into QBO and calling it a migration produces a result that drifts from the source over time.
An integration is different. It connects two systems with a defined boundary between them. QBD remains the historical record (via a sealed bundle). QBO becomes the operational system going forward. The boundary is the cutover date. Each side does what it does well, and neither is asked to be the other.
Every QBD-to-QBO integration faces the same question: what do we do with the history?
Most tools answer "move it all into QBO." That sounds reasonable until you understand what QuickBooks Online actually does with historical transactions. Once they are in QBO, your old numbers can change underneath you — without warning, without an audit trail, without an off switch — when any of the following happens:
Your books no longer match your filed tax returns. Reconciled bank statements no longer tie out. Prior-period reports change. Your accountant calls. You spend weeks figuring out what happened.
The community forums are full of these stories. Most never get a real answer.
Sealed Ledger's integration is built on a different model:
The biggest risk in any QBD-to-QBO move is not the day of the integration — it's the years afterward. Once history is in QBO, the customer is exposed to silent recalculation for as long as that data is in there.
We remove that risk by removing the history from QBO. There is nothing for QBO to recalculate.
This is not a compromise. It is a deliberate architectural choice. If your historical books must be queryable, audited, or referenced — they will be, through the bundle. The bundle is purpose-built for that role. QBO is purpose-built for current operations.
The engagement is intentionally short and bounded. Most QBD-to-QBO services are open-ended projects spanning months. Ours is structured to complete in a defined window, with explicit gates between each phase.
Download the Sealed Ledger utility and run it against your QuickBooks Desktop file. The utility uses Sealed Accounting Ledger Technology or SALT to read the file and write a sealed bundle. The bundle is hashed with SHA-256 and timestamped by an independent Time-Stamp Authority. The bundle can be uploaded to Sealed Ledger for analysis and integration engagement. Bundles come with a 30 day evaluation period and can be unlocked via a perpetual lincense. The fee charged is redeemable for integration services for upto 1 year from creation.
Before any data moves toward QBO, you receive a Pre-Flight Document listing exactly what will be created in QBO and exactly what will be dropped, with reasons. You review it and raise any questions or objections at this stage.
The full integration is run against a QBO sandbox so you can see the result before it lands in your real QBO. Documents, reports, and balances are produced for your review. Once you approve the sandbox result and sign off on the Pre-Flight, the live run is scheduled. Nothing is written to your live QBO until that approval.
Your QBD chart of accounts is created in QBO, with type and subtype translations documented in the Pre-Flight. For each account, you've already approved what should happen — carry from bundle, keep matched QBO, adopt bundle over matched QBO, or inactivate QBO-only.
Vendors, customers, items, terms, payment methods, and classes — cleansed and complete. Unreferenced or stale entries are dropped per the published rules. Duplicates are resolved. The lists that move into QBO are the ones you'll actually use going forward. Entries dropped here remain preserved in the bundle.
Open invoices, open bills, open purchase orders, and open estimates — the documents that are still active at cutover. They carry their original dates, amounts, and references. AR and AP balances emerge correctly because they're driven by the same open documents that produced them in QBD.
Once Stages 0–2 are complete, you receive a Completion Document recording everything that was created in your QBO, with API IDs, and any anomalies encountered. The Completion Document is the operational record of the integration; the bundle is the historical record of your QBD data. They serve different purposes and live separately.
Note on duration. Most integrations take 1–3 sessions over a week or two, depending on chart-of-accounts complexity and the volume of open documents. Engagements end with handoff; we don't roll into ongoing bookkeeping.
The SALT bundle contains:
The bundle is a SQLite database, queryable with standard tools. Sealed Ledger provides access for non-technical users when historical lookups are needed. Your CPA, your tax preparer, your auditor — anyone who needs to look at your historical books — works through the bundle. They don't need QuickBooks Desktop running. They don't need to call you.
Intuit's tool moves history into QBO and enables Automated Sales Tax as part of the new-company setup. That combination is exactly the configuration that produces the silent-recalculation problems we've designed our approach to avoid. The tool is free; the long-term cost of using it is often paid in CPA hours years later.
These services also move historical transactions into QBO — typically two years by default, more for an added fee. They handle the conversion mechanics with more accuracy than Intuit's free tool, but the historical data still ends up in QBO and is still subject to the same silent-recalculation behavior. Neither service produces a sealed, independently verifiable archive of the source QBD file. If you later need to confirm what your original QBD records actually said, neither service gives you a way to do that.
A fresh start with opening balances is similar to what we do, but without the bundle. You start QBO with current balances and lose access to history unless you keep QBD running. Our approach gives you the fresh start plus a sealed, queryable archive of everything that came before.
Many QBD users will not move. Intuit's end-of-sale for QuickBooks Desktop creates pressure, but for some customers, the right answer is to keep QBD running as long as possible, or capture a bundle and treat that as the permanent record. We support that decision. The bundle alone is valuable, even without an integration. Many of our customers will purchase only the bundle.
You download the Sealed Ledger utility and capture your QuickBooks Desktop file into a sealed SALT bundle. The bundle is held in Sealed Ledger custody and accessed through us when historical reference is needed. Many companies will find this is all they need — your CPA, your tax preparer, your auditor can access your books without QuickBooks Desktop running. A keep-your-own-copy option is available for an additional fee.
Includes the bundle, plus the staged integration to QuickBooks Online described above. Your QBO starts clean at the cutover date with the data you need to operate. Your history lives in the bundle.
Pricing for both is published at the engagement quote. Bundle Only is a fixed price. Bundle + Integration is scoped per engagement based on chart-of-accounts complexity and the volume of open documents.
You're a fit if:
You are not a fit if:
If you fall in the "not a fit" category, we'll point you toward a service that does what you need.
Reach out with a few sentences about your situation and we'll go from there.