ERP Migration & SelectionFree worksheetPDF, Excel, Word exportMicrosoft Dynamics 365 Business Central

NAV to Business Central Data Migration Mapping Worksheet

Moving from Dynamics NAV to Business Central means deciding, table by table, what to migrate, how, and how long it will take. This worksheet makes those decisions visible and gives you a first estimate of load time.

Download:
NAV tableBusiness Central targetMethodRecordsLoad minutes per 1000Load time (min)StatusOwner
1.3
16.8
7.2
75
18
4.75
84
0
Total records
51,700
Total load time (min)
207.05
Estimated load hours
3.4508
Average minutes per 1000 records
4.0048

Minutes per 1000 records are planning inputs that you measure in a test load, the example values are not benchmarks. A technical upgrade moves data in place and does not need per-table loading, so use this for selective or fresh-start migrations.

NAV database profile

Optionally ask for a read-only profile of table sizes, duplicates and dormant records.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

List every NAV table or data set that matters, including custom tables. Choose the target in Business Central and the method. Enter record counts from a SQL query or the Table Information page, and a measured load rate from a test load. The tool computes load time per row and in total. Update the status column during the project, and filter by owner for weekly status calls.

  • Include custom tables and fields from add-ons
  • Decide early which history is migrated and which stays archived
  • Record the reconciliation evidence for each master data set

Choosing a migration method

A technical upgrade converts the whole database and keeps history but needs the customization converted to extensions first. A fresh start with configuration packages loads clean master data and opening balances, and is common when the old database has years of clutter. Journal imports are used for opening balances. Custom scripts handle structures such as BOMs. Choose the lightest method that meets audit needs.

Estimating and testing loads

Load time depends on validation logic, number of subscribers and hardware, so measure it in a test environment. Run at least two full test loads before cutover. The first finds mapping errors, the second proves the timing and the reconciliation. Use the totals here to plan the cutover window and to decide whether to freeze the legacy system for hours or a weekend.

Common mistakes

Migrating everything by default is the main mistake, since old history makes the new system slower and harder to reconcile. Another is ignoring custom fields that carry business meaning. Teams also forget to load numbering state so new documents start with duplicates of old numbers. Finally, not reconciling each load immediately makes errors hard to trace.

Frequently Asked Questions

Should we do a technical upgrade or a fresh start?

A technical upgrade keeps all history but requires converting customizations to extensions. A fresh start is cleaner and often faster for heavily customized or cluttered databases. The choice depends on audit needs, customization volume and how much history users need online.

How do I get record counts from NAV?

On the NAV client use the Table Information window, or run a COUNT query against the SQL database for on-premises installations. Count per company if you have several, because each company has its own table instances.

What is a configuration package?

It is a Business Central feature to export and import data between companies or environments using packages of tables. It validates fields on import, so it is slower than raw SQL but safer for master data.

How many test loads are enough?

Plan at least two complete rehearsals. The first reveals mapping and data quality problems, the second confirms timing and reconciliation. Large or complex databases often need three before the team is comfortable.

If your NAV database needs profiling before a migration, we can analyze it on-premises and report duplicates, dormant records and custom table usage.