The layers, in order
- Configuration: fiscal calendar, currencies, tax codes, dimensions, posting groups.
- Chart of accounts: mapped account by account, including parent/child structure.
- Master data: customers, vendors, items, price lists, warehouses.
- Balances or history: either an opening trial balance at cutover, or posted transactions for N years.
- Open documents: unpaid sales invoices and bills, open sales and purchase orders, on-hand inventory with costs.
- Reconciliation: trial balance, AR and AP agings and inventory valuation compared between the old and new systems.
What the native tools do / where they stop
| Destination | Native import | Where it stops |
|---|---|---|
| Business Central | Configuration packages (Excel); Cloud Migration from BC on-premises, GP, SL and custom SQL; QuickBooks extensions | Microsoft calls configuration packages “advanced functionality” and suggests a partner. The QuickBooks Online migration brings a beginning balance, not full history, and no sales or purchase orders |
| NetSuite | CSV Import Assistant | 25,000 records or 50 MB per import job; transactions should stay under 5,000 lines (10,000 for journal entries) |
| Odoo | CSV or XLSX import on any object | Relationships need External IDs; related records have to be imported first |
Every one of these imports data. None of them maps your chart of accounts to the new one or proves the balances match afterwards. That’s where ERP migrations take longest.
Choosing how much history
Legal retention isn’t the same as migration scope. In the US, the IRS says to keep records for 3 years in most cases and longer in some. You can meet that from an archive of the old ERP. Bringing the history into the new ERP is a business choice: drill-down and comparisons with prior years, weighed against migration effort and messy legacy postings.
Where FlitStack AI fits
FlitStack AI migrates ERP transactions at line level, with a before-and-after trial balance reconciliation report and a configurable cutoff for history. Most customers migrate 3–7 years. See ERP migrations or talk to us.