Fix guide
Shopify-QuickBooks connector migration problems
You migrated from one Shopify-QuickBooks connector to another - by choice or because the old one was retired - and the books haven't felt right since. Merchants who went through the early-2026 forced migration to the official connector reported exactly this: sync gaps, doubled tax treatment, recurring breakage needing support cases several times a month.
A migration is the single most damage-prone event in the life of a Shopify-QBO integration, because it can produce all three failure classes at once: a gap (orders placed between old-pipe-off and new-pipe-on that neither posted), an overlap (a window where both pipes ran and everything posted twice), and changed posting behavior (the new connector posts different transaction types, to different accounts, with different tax treatment than the old one did).
The fix is not more migrating. It's an audit of the migration window, order by order, so every gap gets recorded, every overlap gets reversed, and the new posting behavior gets verified before months of history build on top of it.
The symptoms
- A cluster of missing orders dated around the cutover, that never backfilled
- Duplicated transactions in an overlap window where both connectors were briefly live
- Transactions posting differently since the migration - different types, accounts, or tax amounts
- Recurring sync errors since the switch, each leaving its own small gap
Why it happens
The cutover gap
The old connector stops on one date; the new one starts syncing from another. Orders in between belong to nobody, and new connectors typically sync forward from activation rather than backfilling history. The gap sits silently until a reconciliation or a tax return exposes it.
The overlap double-post
If the old connector wasn't disconnected before the new one activated, both posted the same orders for however long they coexisted. Everything in that window is duplicated - revenue and tax overstated by the full amount of the overlap.
Changed posting behavior
Connectors differ in what they post (sales receipts vs. invoices vs. journal entries), where (which income, fee, and clearing accounts), and how they treat tax (inclusive vs. exclusive - the mechanism behind the doubled-VAT reports on migrated setups). Reports that compare pre- and post-migration periods can mislead until the mapping differences are understood.
How to check and fix it by hand
- 01
Establish the exact window
Find the last order the old connector posted and the first order the new one posted. Everything between those timestamps is your audit window - plus a few days on each side for the overlap check.
- 02
Diff the window order by order
List every paid Shopify order in the window and check each against QBO: present once, present twice, or absent. This is tedious by hand and exactly what a line-by-line diff automates - LedgerClear's free scan runs it read-only and separates real gaps from settlement timing.
- 03
Record the gaps, reverse the overlaps
Missing orders get recorded (sales receipt or journal entry per your setup). Duplicates get reversing entries, not deletions, so the audit trail survives. Tax components matter on both: a missing order also missed its tax; a duplicate doubled its tax.
- 04
Verify the new connector's posting on a sample
Take five post-migration orders and check amounts, accounts, and tax treatment against the orders themselves - especially if your prices are tax-inclusive. Ten minutes here catches a systematic setting problem before it compounds across months. Then keep a periodic independent check running; migrations are also when recurring breakage tends to start.
Common questions
- The new connector says everything is synced - why are my books still wrong?
- Connectors report on what they posted, not on what they never saw. Orders in the cutover gap predate the new connector's activation, so they're invisible to it. Only an independent comparison of Shopify against QBO across the migration window finds them.
- Will the new connector backfill orders from before I activated it?
- Typically no, or only partially and on request. Verify the window order by order rather than assuming - and if you trigger a backfill or re-sync, check for duplicates afterwards, since re-syncs are the classic duplicate source.
- Should I audit before or after fixing the connector settings?
- Snapshot the damage first, read-only - it's your baseline and it doesn't change while you adjust settings. Then fix settings, then record the corrections. LedgerClear audits per-order syncs (the official connector, Synder) today and runs alongside summary-posting tools like A2X without touching their entries.
LedgerClear doesn’t replace your sync. It audits per-order syncs today - the official connector and Synder. Summary-posting tools like A2X and Link My Books: auditing support is coming later, and LedgerClear runs alongside them without touching their entries. If the right answer for you is switching tools, the scan report is the damage report to migrate with.