Migrating QuickBooks to Sage Intacct requires restructuring your flat COA into dimensions, sequencing imports by dependency order, and managing API tier limits — not a simple export-and-import.
QuickBooks to Sage Intacct is not a lift-and-shift — it is a structural data transformation. QuickBooks uses a flat Chart of Accounts with classes and locations bolted on as tags. Sage Intacct uses a dimensional general ledger where every transaction can be sliced by location, department, project, and custom dimensions independently. This architectural gap means account numbers that encode segments (e.g., 5100-NYC-Rent) must be decomposed into base accounts plus dimension values. QuickBooks locations that represent legal entities must become Intacct Entities, not location dimensions. Classes doing triple duty as department, region, and program must be split. Migration requires COA redesign, multi-entity consolidation planning, strict dependency-sequenced imports, vendor/customer deduplication across files, and careful API transaction limit management to avoid overage fees.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
QuickBooks Location is the trap
If a QuickBooks Location represents a legal entity with its own books, it belongs in Sage Intacct as an Entity, not a reporting Location. Intacct's developer docs are explicit: an entity is a type of location used in multi-entity shared companies. (developer.intacct.com) Getting this wrong means your consolidation structure is broken from day one.
Do not recreate your flat QuickBooks COA inside Intacct
If your current COA has 400+ accounts because you encoded location or department into account numbers (e.g., 5100-NYC-Rent, 5100-LA-Rent), collapse those into a single base account and tag them with the appropriate dimension values. Bringing a bloated COA into a dimensional system defeats the entire purpose of the migration.
Do not attempt this mapping manually in Excel if you have more than a few thousand transactions
Human error in dimensional mapping will permanently corrupt your historical reporting in Sage Intacct. Use automated transformation scripts.
Set your cutover date at a period end
Set a cutover date at a period end so opening balances in Intacct align with QuickBooks. Year-end is often the cleanest option, though month-end is considered the minimum best practice. Note that mid-year cutover has tax recognition implications — consult your tax advisor before choosing a cutover date that falls outside a fiscal year boundary.
If classes or locations have to be reinterpreted during migration, old transaction detail
If classes or locations have to be reinterpreted during migration, old transaction detail loses value fast. Badly mapped detail is worse than summarized history you can trust. Keep the reporting need, not the workaround.
Template gotcha
When importing AP Bills, Purchasing transactions, AR Invoices, or Order Entry transactions, it is important to fill out the Customer/Vendor field on both the header and the transaction line details — these are two separate columns. The auto-population behavior that works in the UI does not apply to CSV imports.
What about iPaaS / middleware? Tools like Boomi or MuleSoft are designed for repeatable,
What about iPaaS / middleware? Tools like Boomi or MuleSoft are designed for repeatable, ongoing integrations — syncing invoices between systems on a schedule. They are not designed to decide whether "West:Sales:Arizona" should be a department, a class, or an entity. Use iPaaS for post-go-live sync, not for structural migration work.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Scope the ledger, the subledgers and the audit obligations.
Objective Agreed scope across master data, open transactions and historical balances, with finance and audit signed up.
Keep these open
-
Inventory master data and transaction volumes in QuickBooks
Count GL accounts, customers, vendors, items, fixed assets, open AR and AP, and transaction lines by year. Transaction line volume, not header count, is what determines your load time.
Data Profiler Get real record counts instead of estimating from memory -
Decide the history strategy with finance and audit
Choose between opening balances only, open items plus balances, or full transactional history. This is the single biggest scope decision in an ERP migration: full history multiplies effort many times over, and most organisations land on balances plus open items plus a read-only archive.
Full transactional history is rarely worth the cost. Confirm what your auditor actually requires before assuming you need it.
Vendor Evaluator Score Sage Intacct against alternatives on weighted criteria -
Consult the external auditor early
The auditor has views on cut-over timing, audit-trail retention and how you evidence that balances carried across correctly. Finding this out after go-live can mean a qualified opinion, so get it in writing now.
-
Review the chart of accounts and decide whether to redesign
A migration is the natural moment to restructure the COA, and also the riskiest one. If you redesign, you need a mapping from old to new for every historical balance, plus a plan to restate comparatives.
Redesigning the chart of accounts mid-migration doubles the reconciliation burden. Treat it as a separate, sequenced project if you can.
-
Catalogue integrations and statutory reporting
List banking feeds, payment gateways, tax filing, payroll, CRM, e-commerce, warehouse and BI. Then list every statutory and tax filing obligation with its deadline — those deadlines constrain your window absolutely.
-
Pick a period-aligned go-live date
ERP cutovers align to a period boundary — ideally the start of a fiscal year, otherwise the start of a clean month. Mid-period cutover means split-period reporting for the rest of the year.
QuickBooks → Sage Intacct specifics
- Which QuickBooks locations are legal entities?
- If they need separate balance sheets and tax IDs, they become Intacct entities, not location dimensions.
- Which class values really represent separate dimensions?
- If one class tree is doing triple duty as department, region, and program, it needs to be decomposed — not imported as-is.
- How much history needs to live inside Intacct on day one?
- If the answer is "everything," push back. Two to three years of monthly summaries plus open items is the right scope for almost every company.
Don't move on until
- Chart of accounts and master-data counts confirmed
- History strategy agreed: balances, open items, or full transactional detail
- External auditor consulted on the migration approach
02 Data Audit Reconcile the source before you migrate it — you cannot fix a ledger later.
Objective A source ledger that balances, with master data cleansed and every open item agreed.
Keep these open
-
Produce and sign off a source trial balance
Run the trial balance in QuickBooks and have the controller sign it. This is your migration baseline: without a signed pre-migration position you have nothing to reconcile the target against, and any later discrepancy is unarguable.
Without a signed, dated source trial balance you cannot prove the migration preserved the ledger. Do this before anything else.
-
Reconcile subledgers to the general ledger
Confirm AR, AP, inventory and fixed-asset subledgers tie to their GL control accounts. Pre-existing breaks must be resolved in QuickBooks: migrating an out-of-balance ledger makes the break permanently unattributable.
Data Profiler Profile the QuickBooks export for nulls, outliers and type drift -
Clean and deduplicate master data
Deduplicate customers, vendors and items, and identify records that should not carry forward. Duplicate vendors are also a fraud-control weakness, so this has value beyond the migration.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Agree open AR and AP item by item
Every open invoice, credit note and payment on account needs an owner and an agreed amount, including partially-paid items and foreign-currency balances. Open items are what customers and vendors will dispute in week one.
-
Validate export structure, encoding and precision
Check numeric precision and rounding on the export, and confirm dates and currency codes are unambiguous. Precision loss on amounts is silent, cumulative and produces penny differences that take days to trace.
Amounts exported at reduced precision will not re-total. Verify decimal places before you accept the export.
CSV Validator Catch broken headers and ragged rows in the raw export -
Scan for regulated data and produce masked test data
ERP data holds bank details, tax IDs and payroll information. Scan it, restrict who can see it, and generate a masked copy for the sandbox and for any implementation partner.
PII & Compliance Scanner Find regulated fields before they land in a new system
Don't move on until
- Trial balance in QuickBooks balances and is signed by the controller
- AR and AP subledgers reconcile to the GL control accounts
- Master data deduplicated and inactive records identified
03 Field Mapping Map the COA, the dimensions and the subledger structures.
Objective A signed mapping covering the chart of accounts, dimensions, tax codes and currency handling.
Keep these open
-
Map the chart of accounts account by account
Every source account maps to exactly one target account, or to a documented split with agreed proportions. The controller reviews and signs this line by line — an unreviewed COA map is how a balance sheet stops balancing.
Schema Mapper Opens pre-loaded with the QuickBooks → Sage Intacct field pair -
Map dimensions, cost centres and analysis codes
ERPs differ structurally here: segments, dimensions, tracking categories and classes are not interchangeable. Confirm how Sage Intacct models analysis and whether your existing reporting hierarchy survives the translation.
-
Map tax codes, rates and jurisdictions
Map every tax code with its rate, jurisdiction and reporting treatment, then verify the mapping reproduces your last filed return. Tax errors are statutory exposure, not reporting inconvenience.
A tax-code mapping that has not been tested against a previously filed return is untested. Reproduce a real filing before sign-off.
-
Decide multi-currency and exchange-rate handling
Confirm functional and reporting currencies, and how historical rates are stored. Revaluing historical transactions at current rates rewrites reported results and will not tie to filed accounts.
Historical transactions must retain their original transaction-date rates, or your comparatives will not match filed statements.
-
Map master data and subledger structures
Map customer and vendor records with their payment terms, credit limits and tax registrations, and item records with units of measure and costing method. Costing-method differences change inventory valuation, which changes the balance sheet.
-
Set load order and freeze the spec
COA, then dimensions, then master data, then opening balances, then open items, then any historical detail. Version and sign off the spec with the controller before the pilot.
Don't move on until
- Account-by-account COA mapping reviewed by the controller
- Tax codes and jurisdictions mapped and verified against filings
- Multi-currency and rate handling agreed with finance
04 Test Migration Prove the ledger balances in the target before you trust it.
Objective A sandbox load whose trial balance matches the signed source position to the penny.
Keep these open
-
Configure the Sage Intacct sandbox with the agreed structures
Build the COA, dimensions, tax codes, currencies, fiscal calendar and posting rules before loading anything. Every one of these affects how a posted transaction lands, so an unconfigured sandbox produces meaningless results.
-
Load master data and validate it
Load customers, vendors and items first and verify counts, payment terms, tax registrations and costing methods. Transactions cannot post correctly against wrong master data, so this gate comes before any balance work.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Load opening balances and prove the trial balance ties
Load opening balances and run a trial balance in Sage Intacct, comparing to the signed source position. It must match exactly — a rounding difference here is a mapping defect, not a rounding difference.
Any variance at all between source and target trial balance must be explained line by line. "Close enough" is never acceptable in a ledger.
-
Load open items and reconcile the subledgers
Load open AR and AP with their ageing intact, then confirm subledger totals tie to GL control accounts and that ageing buckets match. Ageing that shifts means transaction dates mapped wrongly.
-
Run a full period-end close in the sandbox
Execute the whole close: revaluation, accruals, depreciation, tax calculation, and financial statement generation. Compare every statement to QuickBooks for the same period. The close is where structural mapping errors finally become visible.
-
Test transactions end to end and reproduce a tax filing
Post a sales order to cash and a purchase order to payment, then generate the tax return for a previously filed period and compare it to what you filed. If both reconcile, the configuration is sound.
Don't move on until
- Target trial balance matches the signed source trial balance exactly
- Subledgers reconcile to control accounts in the target
- A full period-end close has been run in the sandbox
05 Cutover Switch the ledger on a period boundary, with balances proven.
Objective Balances and open items live in Sage Intacct, transacting resumed, and a signed post-load trial balance.
Keep these open
-
Close the final period in QuickBooks and freeze posting
Complete the period-end close, then lock posting entirely. An ERP freeze is absolute: a single journal posted to the old system after the final export leaves the two ledgers permanently divergent.
One journal posted in the old ERP after the final export breaks the reconciliation permanently. Lock posting at the system level, not by asking people nicely.
-
Publish the cutover runbook with the abort point
A timed, owner-named sequence for load, balance verification, integration switch and go/no-go, with an explicit abort criterion. The trial-balance check is the gate — nothing proceeds until it ties.
-
Load balances and open items into production
Load the final opening balances and open AR/AP into Sage Intacct production, following the pilot-proven sequence. Do not improvise the order under time pressure.
-
Reconcile and sign the post-load trial balance
Run the trial balance in Sage Intacct and reconcile it to the signed source position, then have the controller sign the result. This signature is your evidence for the auditor and your go/no-go gate.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint banking, payment and tax integrations
Switch bank feeds, payment gateways, tax filing connections, payroll and BI, then process one real low-value payment and one bank reconciliation end to end. Banking errors move real money, so verify with live traffic.
Payment integrations left connected to the old ERP can duplicate real payments. Disable them before switching, not after.
-
Go/no-go, then open for transacting with daily reconciliation
Call the decision on the signed trial balance, open Sage Intacct for posting, and reconcile daily for the first two weeks with finance support on hand. Keep QuickBooks read-only for statutory retention — this is an audit requirement, not a preference.
Don't move on until
- Post-load trial balance signed by the controller
- Banking, tax and payment integrations verified live
- Users transacting and the first daily reconciliation clean
06 Validation Prove the statements, the tax position and the audit trail.
Objective Financial statements reproducing the source position, a clean tax filing, and auditor acceptance.
Keep these open
-
Reconcile the full ledger and all subledgers
Reconcile trial balance, AR, AP, inventory, fixed assets and bank against the signed source position. Produce a single reconciliation pack that goes to the auditor.
Migration Validation Tool Reconcile QuickBooks and Sage Intacct record-for-record -
Reproduce the financial statements
Generate balance sheet, P&L and cash flow in Sage Intacct and compare to the pre-migration statements. Every variance needs a documented explanation traced to a specific mapping decision.
-
Complete and review the first period-end close
Run the first real close in Sage Intacct with extra review at every step. Compare its duration and outcome to your historical close, and treat anything unexpected as a live finding.
Data Profiler Prove field completeness held up through the load -
Verify the tax position and file
Generate and review the first tax filing from Sage Intacct, reconciling it to the underlying transactions before submission. Have the tax lead review it independently.
The first statutory filing out of a new ERP should be reconciled manually to source transactions before submission.
-
Confirm controls, segregation of duties and audit trail
Verify user permissions, approval limits, segregation of duties and audit logging in Sage Intacct. Controls do not migrate, and a control gap found by an auditor is far more expensive than one you find yourself.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Obtain auditor acceptance and retain the archive
Walk the auditor through the reconciliation pack, get written acceptance, and retain QuickBooks read-only for the full statutory retention period. Diarise the retention expiry rather than the contract renewal.
QuickBooks → Sage Intacct specifics
- Total assets
- compare Intacct total assets to QuickBooks closing trial balance. Fix any gap before continuing.
- Total liabilities
- same comparison. A discrepancy here often signals a missed AP bill or unposted credit memo.
- Retained earnings
- verify the retained earnings roll-forward matches. Errors here compound across every future period close.
- AR aging
- open invoices in Intacct must match the QuickBooks AR aging report by customer and amount.
- AP aging
- open bills in Intacct must match the QuickBooks AP aging report by vendor and amount.
Don't move on until
- Financial statements match the pre-migration position
- First period-end close completed and reviewed in Sage Intacct
- Auditor satisfied and archive retained for the statutory period
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Chart of Accounts | high | Flat QBO accounts with embedded segments must be restructured into base accounts plus dimensions. Name and number conflicts across entities must be resolved before import. |
| Classes | high | Must be mapped to the correct Intacct dimension (Department, Class, or UDD) by business meaning. Classes overloaded with multiple concepts must be decomposed. |
| Locations | high | Locations representing legal entities must become Intacct Entities, not Location dimensions. Getting this wrong breaks the consolidation structure. |
| Sub-Accounts | medium | Nested QBO sub-accounts should be flattened into base accounts with the segment extracted into a dimension value. |
| Vendors & Customers | medium | Shared lists in Intacct require deduplication across multiple QuickBooks files by name, tax ID, and address before import. |
| Open AR Invoices | medium | Must be imported at line-level detail with correct customer, terms, dimension, and account references already loaded. |
| Open AP Bills | medium | Both header and line-level vendor fields must be populated explicitly — Intacct CSV imports do not auto-populate like the UI. |
| Historical GL Transactions | medium | Best migrated as monthly summary journal entries. Full detail migration inflates API usage and forces mapping of obsolete records. |
| Payroll History | low | Rarely importable into Intacct. Typically kept in QuickBooks or the payroll system of record. |
| Audit Trail & Change Logs | low | System-generated metadata that does not transfer between platforms. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
COA Dimensional Redesign
Segment-encoded account numbers must be decomposed into base accounts plus dimension values. A 500-account flat COA should compress to roughly 80 base accounts with dimensions.
Multi-Entity Consolidation
Separate QuickBooks files must be merged into one Intacct company with shared COA, vendor, and customer lists — requiring standardization and deduplication before import.
Dependency-Sequenced Imports
Intacct rejects transactions if referenced records (dimensions, terms, vendors) do not already exist. Imports must follow a strict parent-before-child order.
API Tier Overage Costs
Performance Tier 1 includes 100,000 API transactions per month. A high-volume migration can exceed this and incur overage fees at $0.15 per pack of 10 transactions.
Historical Data Scoping
Migrating all transactional history adds weeks and inflates API usage. Most companies should migrate 2–3 years of monthly summary journal entries plus open AR/AP.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
How do QuickBooks classes map to Sage Intacct dimensions?
QuickBooks classes typically map to the Department dimension or a user-defined dimension (UDD) in Sage Intacct, depending on what the classes represent. QuickBooks Locations usually map to the Location dimension, but if a location represents a legal entity with its own balance sheet, it should become an Intacct Entity instead. Sub-accounts with embedded segments (e.g., 5100-NYC-Rent) should be flattened into a base account plus dimension values.
How much historical data should I migrate from QuickBooks to Sage Intacct?
Most companies migrate 2–3 years of transaction history as monthly summary journal entries, plus full detail for open AR/AP and current master data. Older history stays in QuickBooks as a read-only archive. Migrating every transaction adds weeks to the timeline, inflates API usage, and provides little operational value beyond the most recent years.
What are Sage Intacct's API limits during migration?
Sage Intacct's standard Performance Tier 1 includes 100,000 API transactions per month at no additional cost. Overages are billed at $0.15 per pack of 10 transactions. A high-volume migration can easily exceed this limit, resulting in unexpected fees of hundreds or thousands of dollars. Transactions from authorized Marketplace Partners do not count against your tier.
What order should I import data into Sage Intacct?
Import in strict dependency order: dimensions and configuration values first (locations, departments, terms), then master data (GL accounts, vendors, customers), then transactions (AR invoices, AP bills, journal entries). If a referenced record doesn't exist when a transaction tries to import, the entire import for that record will fail.
Can I consolidate multiple QuickBooks files into one Sage Intacct company?
Yes. Sage Intacct's multi-entity architecture supports multiple entities under one company with a shared chart of accounts, vendor list, and customer list. You must standardize your COA across all QuickBooks files and deduplicate vendor/customer records before migration, since Intacct enforces a single shared record per entity.