Business Central & NAV / NAV-to-BC migration
NAV-to-Business Central migration with automation and hands-on expertise.
I developed an automated NAV-to-BC migration tool to support the data-migration work, and I bring 17 years with Dynamics NAV and 8 with Business Central to the records being moved. The scope is defined around your source system, the data you need in BC, and how the results will be reconciled.
Scope
What the engagement establishes
Your NAV version and customizations
Which release you are on, what has been customized, and what that means for the source data.
The business data required in BC
Master data, open items, balances, and whichever history the business genuinely needs.
Mapping and transformation needs
Where NAV structures and BC structures differ, and how each difference is handled.
Configuration and cleanup responsibilities
Who configures BC, who cleans source data, and in what order.
Testing and acceptance criteria
How trial migrations are run and what 'accepted' means before cutover.
Fit with the wider implementation
How the migration workstream relates to the team implementing BC — yours, ours, or a partner's.
Reconciliation
The migration is accepted on reconciled results, not row counts.
Source and destination totals and exceptions are reviewed as part of agreeing and validating the migration. Automation moves and transforms the data; reconciliation confirms the business result before cutover.
Historical information means different things: native BC records, posted transactions, or an accessible archive. We establish which representation each requirement needs and what the migration approach supports before it becomes part of the scope.
Areas of expertise
The parts of a migration that deserve careful assessment
These are areas of experience and assessment. Which are automated for your migration, and how, is established per engagement — not assumed.
Opening balances
General ledger, customer, vendor, and bank balances that must agree at the cutover date.
Inventory valuation
Quantities are the easy part; costing method and valuation are where migrations go wrong.
Historical transactions
What is needed, how it will be represented in BC, and what stays in an archive.
Payment applications
Applied and unapplied entries carried across so the ledgers still agree.
Dimensions
Dimension structures and values mapped so reporting keeps working on day one.
Questions
Common questions.
Can you migrate from older NAV versions?+
My migration work includes legacy NAV, including NAV 2009. The approach for your system depends on its version, customizations, source data, and the agreed BC target.
Can you bring our transaction history into BC?+
Historical-data requirements are assessed explicitly. We agree which records are needed, how they will be represented, and what the migration approach supports before committing to the scope.
Can you handle the migration while our existing partner implements BC?+
Yes. The migration can be a defined workstream alongside the team responsible for the wider implementation, with responsibilities and acceptance criteria agreed up front.
Is this a tool we buy and run ourselves?+
The current offer is a migration service delivered using our tooling and expertise, rather than a self-service software product.
Related work
Evidence from consulting engagements and in-house roles.
Consulting engagement (current)
NAV-to-Business Central upgrade with EDI and marketplace integrations
International CPG manufacturer and distributor
Upgrading from Dynamics NAV to Business Central, with customer EDI through TrueCommerce, custom AS2 for vendors, and Amazon, Shopify, and TikTok store integrations built on .NET APIs and AL extensions.
Already working with a Microsoft partner or MSP? We can take on an agreed integration, EDI, migration, or remediation workstream alongside your existing team.
Start the conversation
Tell me what needs to connect, migrate, or work better.
Describe the systems involved and what you're trying to accomplish. I review every inquiry personally and will tell you directly whether the project is a fit.
Discuss your NAV migration