Skip to content
Get a quote

How do I migrate data from one ERP to another?

Short answer

Migrate in layers. Start with the chart of accounts and dimensions, then customers, vendors and items, then opening balances or full transaction history, then open documents such as unpaid invoices and open POs. Cut over at a period end and reconcile trial balances between the two systems. Most ERPs import through templates, like Business Central's configuration packages.

By

The layers, in order

  1. Configuration: fiscal calendar, currencies, tax codes, dimensions, posting groups.
  2. Chart of accounts: mapped account by account, including parent/child structure.
  3. Master data: customers, vendors, items, price lists, warehouses.
  4. Balances or history: either an opening trial balance at cutover, or posted transactions for N years.
  5. Open documents: unpaid sales invoices and bills, open sales and purchase orders, on-hand inventory with costs.
  6. 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

DestinationNative importWhere it stops
Business CentralConfiguration packages (Excel); Cloud Migration from BC on-premises, GP, SL and custom SQL; QuickBooks extensionsMicrosoft 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
NetSuiteCSV Import Assistant25,000 records or 50 MB per import job; transactions should stay under 5,000 lines (10,000 for journal entries)
OdooCSV or XLSX import on any objectRelationships 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.

Questions, answered

A few useful answers.

Opening balances or full history?

Opening balances are faster and cleaner; full history keeps drill-down in one system. A common middle path is detailed history for a few years plus balances before that, with the old ERP archived for audits.

When should we cut over?

At a month or year end, after the old period is closed. Mid-period cutovers make accruals and reconciliation much harder.

Do reports and approval workflows migrate?

No. Saved reports, financial statement layouts, custom forms and approval workflows are rebuilt in the destination ERP.

A closer look

Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

Get a quote