Why the history doesn't come along
Every Business Central migration needs a scope decision. Many projects bring over open transactions, balances, and selected master records such as customers, vendors, items, and the chart of accounts. Older posted history may remain outside the new ERP because the posting logic, multicurrency handling, dimensions, and document structures do not map cleanly. The correct answer depends on the business and retention requirements; it should be written down rather than assumed.
The problem is that "correctly left behind" still means "left behind." The questions don't stop when GP does:
- ✓Auditors, annually. "Show me all invoices to this customer in FY2019 with supporting documents."
- ✓Tax reviews. Finance may need transactions and supporting detail from years before the migration.
- ✓Customer disputes and warranty claims. "We bought this in 2017 — what was the serial number and the terms?"
- ✓Staff turnover. The controller who knew GP leaves. The replacement has never seen it.
Business Central cannot answer these. The data was never loaded.
Decide explicitly where old history will live
A common design sends active operational data to Business Central and historical data to a purpose-built archive. This keeps the new ERP focused on current work while preserving direct access to older records. The same planning decision appears in migrations to other ERP systems, although the exact split varies by business.
New work happens in Business Central. Old questions are answered from the archive, which holds the agreed GP history, record notes and third-party tables that were outside the destination scope.
How the questions get answered afterward
With a purpose-built archive, the recurring requests become searches, not projects:
- ✓Audit request. Select a company and date range, then export the supporting documents, transactions and accounting totals together.
- ✓Tax query. Search AR, AP, SOP, POP, inventory and GL for a customer name, invoice, purchase order or serial number, then export the results.
- ✓Dispute. Open the historical document with its header, lines and totals, then save a PDF.
- ✓A new controller. Search with business names instead of learning GP table numbers or restoring the old application.
Timing: extract before cutover, not after
The archive works best when extraction happens alongside the migration. A test archive lets the team inspect historical values, save queries, settle mappings, and create typed CSV or XLSX source extracts before go-live. The production extract runs from the frozen or snapshotted cutover state. Reconcile it against GP, run both in parallel for an agreed period, and decommission only after approval. The full sequence is in how to decommission Dynamics GP, and the cost comparison is in GP data archive cost.