Key points
- Version and customizations determine the migration path.
- Historical data needs a clear reason to move.
- Test real workflows and reconcile totals.
Why this is more than an upgrade
Old installations can contain years of changes, reports and undocumented integrations. Business Central uses a modern extension and update model, so some adaptations need redesign.
Migration is a chance to remove obsolete processes and data. Copying every old limitation adds cost without progress.
Technical and operational inventory
Record version, database, companies, volume, modified objects, reports, jobs and integrations. Connect every item to a process owner who can confirm whether it is used.
Observe a real operating period. Some features appear only at month-end, stock count, seasonal work or annual reporting.
Standard, extension or removal
Look for current standard functionality before rebuilding a customization. If the gap remains, decide whether configuration, an extension or an integrated service is appropriate.
Keep customization only when it supports an important process and has an owner who will test it.
The data strategy
Decide which operational data must be active in the new system and which history can remain in an accessible archive. More data does not automatically mean a better migration.
Clean customers, suppliers, items, dimensions and accounts. Run trial migrations and reconcile balances, stock, open documents and totals.
Integrations and reports
Inventory ecommerce, banking, payroll, warehouse, EDI and reporting connections. Check current APIs and authentication rather than assuming an old integration can move unchanged.
Classify reports as operational, financial, regulatory or historical. Some can use new pages or analytics; others need exact reproduction.
Rehearsing cutover
Create a timetable for shutdown, export, import, verification and reopening. Rehearse in a test environment and measure the duration.
Define success and rollback criteria. After launch, review differences, integrations and critical tasks daily until stable.
Relevant Webmate resources
Continue with guides, services and examples directly connected to the topic of this article.
Frequently asked questions
Must all historical data be migrated?
No. Move what operations and obligations need, and keep the rest in a verifiable archive where appropriate.
Can NAV customizations remain?
Some can be rebuilt as extensions, some replaced by standard features and others removed. Evaluate them individually.
Must Business Central run in the cloud?
Business Central has different deployment considerations. The right route depends on version, requirements and current Microsoft and partner policy.
