QuickBooks Desktop
↓
QuickBooks Online
A step-by-step guide to migrating your accounting data cleanly and safely — covering pre-migration prep, the transfer itself, post-cutover validation, and InterWeave integration reconnection.
Create a verified local backup (.QBB) before touching anything. Store it in a location outside the normal working directory — on a network drive or external storage. This is your permanent audit record and cannot be recreated after migration.
QuickBooks Desktop 2020 or later migrates cleanly via Intuit's built-in export tool. Older versions must be upgraded to QBD 2020 at minimum before starting — the migration tool does not support end-of-life versions.
QBO has a target count limit of approximately 750,000 combined transactions, customers, and vendors. Before migrating, run the Company File Diagnostic in QBD:
- Go to File → Utilities → Verify Data
- Review the transaction count summary
- If near or over the limit, archive historical data or consider a clean-start migration with opening balances only
A clean source file produces a clean migration. Before exporting, complete the following:
- Merge duplicate customers, vendors, and accounts
- Reconcile all bank and credit card accounts through the cutover date
- Clear or write off old, uncleared transactions
- Remove inactive items that are no longer needed
- Run the Condense Data utility if file size is excessive
Create a second verified local backup (.QBB) after cleanup is complete — before initiating the export. Store it alongside your initial backup. Having a pre-export snapshot separate from your pre-cleanup snapshot protects you in both directions.
Not everything transfers automatically. Plan for manual re-entry of the following after go-live:
- Payroll history & settings — must be reconfigured in QuickBooks Payroll
- Inventory assemblies — convert to simple inventory items before migrating
- Custom invoice & estimate templates — will need to be rebuilt in QBO
- Memorized reports — must be recreated manually
- Fixed asset manager data
- Loan manager records
Select the plan that matches your operational needs before provisioning the QBO account:
| Plan | Best For | Key Features |
|---|---|---|
| Simple Start / Essentials | Very small businesses, solo operators | Basic A/R, A/P, bank feeds |
| Plus | Businesses tracking inventory, projects, or departments | Inventory, project costing, class & location tracking |
| Advanced | Larger teams needing custom roles or automation | Higher user count, batch actions, custom fields, priority support |
- Open your QBD company file
- Go to Company → Export Company File to QuickBooks Online
- Sign in with (or create) your Intuit account
- Select or create the target QBO company
- Choose whether to include inventory (see warning below)
- Click Export — this takes 15 minutes to several hours depending on file size
Inventory migration is the most error-prone area of a QBD-to-QBO transfer. If you have complex inventory — assemblies, lot tracking, or multiple warehouse locations — consider migrating without inventory and manually re-entering opening balances and active items in QBO instead.
Intuit sends a confirmation email when the export is complete. Do not close the QBD file during the transfer. If the migration fails partway through, Intuit support can run a clean re-import against a blank QBO company — do not attempt to retry against a partially populated company.
Run all of the following in both QBD and QBO as of the cutover date. Every total must match before go-live:
- Balance Sheet (as of migration date)
- Profit & Loss (year-to-date through migration date)
- Accounts Receivable Aging Summary
- Accounts Payable Aging Summary
- Trial Balance
QBO may automatically rename or consolidate account types during migration. Verify:
- All accounts are present and correctly typed
- Opening balances match QBD exactly
- Parent/sub-account relationships are intact
Check for duplicates, missing records, and unmapped payment terms or tax codes. Pay special attention to:
- Customers with open balances
- Vendors with open purchase orders
- 1099 vendor flags — must be manually re-enabled in QBO
QBO bank connections are not transferred and must be set up from scratch in the new instance:
- Go to Banking → Link Account
- Search for and connect each financial institution
- Set the start date to the day after your last reconciled period in QBD to prevent duplicate transactions
- Payroll: Reconfigure QuickBooks Payroll or reconnect your third-party provider
- Recurring transactions: Recreate memorized templates in QBO
- Invoice templates: Rebuild under Gear → Custom Form Styles
- User access: Invite team members and assign roles under Gear → Manage Users
- Third-party integrations: Reconnect all apps from the QBO App Store
Once QBO is fully validated and live, set a closing date and password in QBD under Company → Set Closing Date. Archive the QBD file — do not delete it. It remains your permanent historical audit record.
These steps apply if you use InterWeave integrations — Salesforce, Creatio, Sage, payment processors (Stripe, Authorize.net, Braintree, Square), or eCommerce connectors. Complete all steps in Phase 03 before beginning this phase.
The QBO instance referenced by InterWeave changes on migration. A new OAuth token must be issued before any SmartFlow can sync:
- Log into the InterWeave Admin Panel
- Navigate to Connector Ecosystem → QuickBooks Online
- Click Reconnect and complete the Intuit OAuth authorization flow
- Confirm the new company name and Realm ID appear correctly
QuickBooks Online assigns new internal IDs to customers, vendors, and accounts upon migration. Any InterWeave field maps referencing QBD internal IDs must be verified and updated:
- Run the Entity Sync Report from InterWeave for the QBO connector
- Identify records flagged as Unmapped or Not Found
- Update field mappings in the SmartFlow configuration for each affected flow
After remapping, run end-to-end smoke tests for each active SmartFlow before resuming live operations:
- Trigger a test transaction in the source system (e.g., Salesforce opportunity close or Creatio order)
- Confirm the record creates correctly in QBO with the right accounts and amounts
- Validate in both directions if bidirectional sync is active
If the client uses InterWeave Payment Cloud (Stripe, Authorize.net, Braintree, or Square) with QBO as the ledger target:
- Open the Payment Cloud Admin Panel
- Under Ledger Connections, select QuickBooks Online
- Re-authorize and remap income, fee, and refund accounts to the updated QBO Chart of Accounts
- Run a test payment end-to-end before enabling live transaction posting
InterWeave has accounting resources that can assist you in this migration process, and with accounting validation once the migration has been completed. Please contact us at support@interweave.biz