Migration discipline
Platform migrations with phased cutovers, such as ServiceNow to Salesforce and SharePoint 2013 to SharePoint Online.
- Phased cutovers
- ServiceNow to Salesforce
- SharePoint 2013 to Online
Many businesses have run Dynamics NAV for 10 or 20 years, with customizations nobody wants to touch. NAV to Business Central migration is not a simple version bump: the right route depends on your NAV version, customizations, data and integrations. MoreYeahs assesses your NAV or Navision environment, plans the upgrade and migration path, moves and reconciles your data, and rebuilds what still matters as Business Central extensions.
Hi, ask me anything about NAV to Business Central Migration at MoreYeahs: products, implementation, cost or the projects we have delivered.
AI answers can be wrong. ·
Trusted by teams in the USA, UK, Australia and India











Whether and when to migrate depends on your NAV version, support status, technical dependencies and ERP strategy. Not every NAV customer must move immediately.
Why migrate from Dynamics NAV to Business Central? Ageing customizations, servers to maintain and an upgrade project every time you want new features. Older NAV versions are past or nearing the end of Microsoft support, so check your version's lifecycle.
What we usually build
Dynamics NAV vs Business Central: Business Central is Microsoft's current ERP for small and mid-sized businesses and the successor to NAV, which was formerly Navision. The migration path depends on NAV version, database, customizations, add-ons and integrations.
What we usually build
A Dynamics NAV upgrade moves you to a newer NAV version. Migration moves you to Business Central, on-premises and then often online. Older NAV versions must first be upgraded to Business Central on-premises (version 14 or later) before cloud migration.
What we usually build
Navision is the original name of the product that became Microsoft Dynamics NAV. If you still call your ERP Navision, the steps are the same. Very old Navision versions usually need extra intermediate upgrade steps or a reimplementation with clean data.
What we usually build
Standard migration activities differ from custom development, such as AL conversion or new extensions, which is scoped separately.
A NAV environment assessment finds the version, customizations, add-ons and integrations that shape the route.
Chooses a full upgrade or a reimplementation, then sets phases and cutover.
Maps your NAV processes to standard Business Central features.
Decides what to rebuild as AL extensions, replace with apps or retire.
Data migration planning, cleansing and mapping that keeps history and balances accurate.
Learn moreSets up the target Business Central environment.
Reconnects your other systems to Business Central.
Learn moreProves processes and numbers before go-live.
Training, deployment and post-migration support for a smooth cutover and early-life support.
No two migrations are identical. Duration depends on your NAV or Navision version, database size and quality, customizations, add-ons, integrations, data scope, process changes, UAT and cutover. An accurate estimate needs an assessment of your source environment and target requirements.
Plan your projectVersion, database, customizations, add-ons, integrations, processes, reports and infrastructure.
Required features, process gaps, compatibility, customizations to replace, integrations and data scope.
The route (a full upgrade through Business Central on-premises, or a reimplementation with essential data), scope, data strategy, extension strategy, testing, deployment and training.
Extraction, cleansing, mapping, transformation, test migration, validation and reconciliation.
Standard features first. AL extensions only where needed.
Integrations, workflows, financial validation, UAT, permissions and reports.
Cutover plan, final data validation and user readiness.
Issue resolution, user questions and agreed optimizations.
Migration carries risk. Assessment, planning, testing and validation reduce it. These are the challenges we plan for: inventory customizations and rebuild, replace or retire each; check add-ons for Business Central versions; cleanse data before migration, not after; check trial balances and sub-ledgers at each test run; rehearse cutover and plan a quiet period.
A partner that delivers, then stays to support what it built.
Platform migrations with phased cutovers, such as ServiceNow to Salesforce and SharePoint 2013 to SharePoint Online.
Mapping, cleansing and reconciliation on CRM migrations.
Dynamics 365 and Power Platform projects across five regions.
Separate test environments and UAT before go-live.
Donan Consulting
“We’re most impressed by their technical expertise and problem-solving approach.”
Repeat support tickets fell by about 70%.
Flyersoft
“MoreYeahs has been a dependable partner, consistently providing strong Microsoft Dynamics 365 support.”
AbdoReview summary
The team challenges requirements instead of just following user stories, and a client portal removed 60 to 70% of support cases.
Acquiresoft SolutionsReview summary
A Dynamics CRM and SharePoint migration cut the reconciliation workload by 60%.
Dynamics GP and Dynamics NAV are different products, so a GP migration needs its own assessment. Microsoft provides a cloud migration path from Dynamics GP to Business Central online. Typical considerations:
GP customers have time to plan; Business Central is one option to evaluate based on requirements and migration feasibility.
Short answers below. For anything specific to your org, ask a NAV to Business Central Migration consultant.
Ask a consultantMoving your ERP data, processes and needed customizations from Microsoft Dynamics NAV to Dynamics 365 Business Central.
Yes, from supported versions. Older versions need intermediate upgrades, and versions before Business Central 14 must go through Business Central on-premises before moving online.
Business Central is NAV's successor: cloud-ready, updated regularly, and customized through AL extensions instead of base-code changes.
Upgrading application code and data to a newer version, re-merging or converting customizations, and testing.
Yes, usually through upgrade steps or a reimplementation that brings master data, opening balances and setup.
It depends on version, data, customizations, add-ons and integrations. An assessment gives a realistic estimate.
Not as they are. C/AL customizations must be converted to AL extensions, replaced with standard features or apps, or retired.
Typically master data, open documents, balances and agreed history. Some customized table data needs special handling.
Yes. Microsoft provides a cloud migration path from Dynamics GP to Business Central online. GP and NAV are different products, so a GP migration needs its own assessment.
NAV version, customizations, add-ons, integrations, data quality, reports, processes and users.
Customizations, data quality, integrations, financial reconciliation, reporting changes and cutover.
Ask about NAV versions they have migrated, AL conversion, data reconciliation, testing, cutover planning and post-go-live support.
Share your NAV or Navision version, main customizations and add-ons, data size and the systems connected to it. We will assess the route and recommend a migration plan.
We use cookies to keep the site secure, understand how it is used, and improve it. You choose what we are allowed to load: analytics and marketing stay off until you say otherwise. Privacy Policy
Strictly necessary Always on
Required for the site to work: security checks on our forms and basic session handling. These cannot be switched off.
Analytics
Google Analytics, so we can see which pages are useful and where people get stuck. Aggregated, and never used to identify you personally.
Marketing
Lets us measure which campaigns bring people here and show you more relevant ads on other sites.
Functional
Remembers smaller conveniences, like a banner you have already dismissed, so we do not show it again.