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.
| NAV table | Business Central target | Method | Records | Load minutes per 1000 | Load time (min) | Status | Owner | |
|---|---|---|---|---|---|---|---|---|
1.3 | ||||||||
16.8 | ||||||||
7.2 | ||||||||
75 | ||||||||
18 | ||||||||
4.75 | ||||||||
84 | ||||||||
0 |
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.
Related Tools
Business Central Core Table Numbers Reference
Look up the base application table number and name for ledger entries, documents, master data and manufacturing objects in Business Central and NAV.
Microsoft DynamicsBusiness Central Go-Live Readiness Checklist
A cutover checklist for Business Central implementations covering opening balances, setup, security, integrations, training and fallback.
Microsoft DynamicsBusiness Central On-Premises Extension Deploy PowerShell Generator
Creates the PowerShell sequence to publish, sync, install or upgrade a Business Central extension on an on-premises server instance.
Microsoft DynamicsBusiness Central Item Setup Options Reference
Plain-language meaning of the item card options in Business Central that drive costing and planning, with guidance on when each fits.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment
New to Microsoft Dynamics NAV and Business Central on-prem? Start with the Microsoft Dynamics NAV and Business Central on-prem guide and toolkit.
Keep exploring
Free tools
- NAV to Business Central Upgrade AssessmentAnswer ten questions about your Dynamics NAV environment to see how ready you are to upgrade to Business Central and what to tackle first.
- Business Central Data Migration Field Mapping WorksheetMap every legacy source field to a Business Central table and field, record the transformation rule and volume, and see how much data is ready to load.
- Dynamics NAV to Business Central On-Prem Code Upgrade Effort CalculatorCount your modified and new objects, set per-object hours, and see code, data, test and total effort for the NAV to BC14 to v25 to current upgrade path.
ERP fixes and how-tos
- Business Central Upgrade Path: From NAV and Older BC Versions to CurrentBusiness Central upgrade paths explained: NAV to BC 14, BC 14 to later versions, the data upgrade sequence and cloud migration as an alternative.
- Business Central Manufacturing Setup: Items, BOMs, Routings and Production OrdersSet up Business Central manufacturing: Manufacturing Setup, work centers, production BOMs, routings, item settings, manufacturing policy and demo data.
- Business Central Item Templates and Customer TemplatesCreate and use item templates and customer templates in Business Central to default posting groups, costing method and dimensions on every new record.
AI on your ERP
- AI for Dynamics GP and NAV, Before the Business Central DecisionDynamics GP mainstream support is ending and NAV is long retired from active development. Add a private LLM over GP or NAV data now, on-prem, without a forced Business Central move.
- AI for Dynamics 365 Business Central, on-premises or SaaS, beyond CopilotAI for Business Central beyond Copilot: grounded question answering over BC's data via OData and APIs, for on-premises and SaaS tenants alike.
Integrations
- How to add AI agents to Microsoft Dynamics NAVHow to add AI agents to Microsoft Dynamics NAV: a tool layer over NAV web services or SQL, human approval before writes, and on-prem models for legacy installs.
- How to add WhatsApp to Microsoft Dynamics 365 Business CentralHow to connect WhatsApp to Dynamics 365 Business Central: API v2.0 or custom API pages, webhooks, template messages, and two-way replies that post back safely.
Software
- Microsoft Dynamics 365 Business CentralDynamics 365 Business Central explained for manufacturers: modules, APIs, AL extensions, deployment, strengths, limits and alternatives for small and mid-size firms.
- Microsoft Dynamics 365 Finance and Supply ChainDynamics 365 Finance and Supply Chain Management explained for manufacturers: modules, data entities, OData, deployment, strengths, limits and alternatives.