Service
NAV to Business Central Migration
One of the first NAV partners in North America 25 years ago. We help organizations move from NAV to modern Business Central, preserving customizations, data, and team expertise.
What we build.
Six disciplines, from first architecture to production support.
Why migrate from NAV
Mainstream support has ended for NAV 2018 and earlier, but the upgrade path is well-defined.
- Mainstream support ended for older NAV versions
- AL development framework your team already knows
- Cloud, mobile, and AI capabilities added
- Not a rip-and-replace, a defined upgrade path
Upgrade compatibility
The right path depends on your current NAV or BC version.
- BC v14-v16: direct upgrade to latest BC
- NAV 2018: two-step upgrade via BC v14
- NAV 2015-2017: requires C/AL to AL conversion
- NAV 2013 and earlier: technical assessment required
Our three-phase methodology
Built from 25 years of NAV expertise and hundreds of migrations.
- Analyze: environment and fit-gap assessment
- Execute: code conversion and data migration
- Validate: testing, UAT, and cutover execution
- Parallel-run option before final go-live
What we handle
End-to-end coverage of your NAV environment and everything built on it.
- Full customization and ISV add-on audit
- C/AL to AL extension conversion
- On-premises to cloud transition
- Integration reconnection and modernization
Proven results
A heavily customized NAV migration delivered real manufacturing growth.
- Defense manufacturer: NAV 2017 to BC 24
- 12% YoY manufacturing growth
- Full Pebblestone and Lanham integration
- Teams integration and embedded analytics
Track record
Deep, proven Dynamics expertise across decades.
- 25+ years as a NAV/BC partner
- 100s of NAV migrations completed
- Gold Microsoft Partner status
- Parallel-run and rollback planning on every project
Why Aedista
Why Aedista for your NAV migration
Our stack
Modern tools we build with
.NET Core
Enterprise web and service backends
Java
Large-scale enterprise systems
Node.js
APIs and real-time services
PHP
High-volume web platforms
React
Modern web front ends
Angular
Enterprise front ends
Next.js
Server-rendered React apps
Swift
Native iOS apps
Kotlin
Native Android apps
Azure
Cloud infrastructure and DevOps
AWS
Cloud infrastructure at scale
Docker
Containerized deployment
Engagement models
Three ways to work with us
Fixed cost
A defined scope, priced upfront, and paid by milestone. Best when requirements are clear and stable.
Time and materials
Built for evolving scope. You pay for delivered work, and priorities can shift as you learn.
Dedicated team
Our engineers work as an extension of your team, on your priorities, at your cadence.
Aedista didn't just advise, they built the system alongside us. They understood our operations, made the complex parts simple, and delivered something our teams actually use every day. The result was immediate and, more importantly, built to last.
Trusted by global brands
Frequently asked questions
Why should I migrate from Dynamics NAV to Business Central?
Microsoft has ended mainstream support for Dynamics NAV 2018 and all earlier versions, meaning no new feature updates, regulatory updates, or non-security hotfixes. Business Central is the direct successor to NAV built on the same AL development framework, so your team's existing knowledge transfers directly. Migrating to Business Central gives you cloud deployment with Microsoft-managed infrastructure, embedded Power BI analytics, AI-powered cash flow forecasting, native Microsoft Teams integration, mobile access from any device, and access to thousands of extensions on Microsoft AppSource. Organizations that stay on unsupported NAV versions face increasing security risks, compliance gaps, and difficulty finding qualified NAV developers and consultants.
Which Dynamics NAV versions can be migrated to Business Central?
All Dynamics NAV versions can be migrated to Business Central, though the upgrade path varies by version. Business Central versions 14, 15, and 16 can upgrade directly to the latest Business Central release. Dynamics NAV 2018 follows a two-step upgrade path through BC version 14 first, then to the latest version. NAV 2015 through 2017 also upgrade through BC v14 but require C/AL to AL extension conversion as part of the process. Dynamics NAV 2013 and earlier versions require a technical assessment and may need intermediate upgrade steps or a reimplementation approach. Aedista has completed hundreds of NAV migrations across all versions and can recommend the most efficient path for your specific environment.
How long does a NAV to Business Central migration take?
A typical NAV to Business Central migration takes 3 to 8 months depending on the complexity of your environment. Straightforward upgrades from recent NAV versions (2018 or BC v14) with minimal customizations can complete in 3 to 4 months. Migrations from older NAV versions with extensive C/AL customizations, multiple ISV add-ons, and complex integrations typically take 6 to 8 months. Very complex environments with heavy customization and large data volumes may take up to 12 months. Aedista uses a three-phase methodology covering analysis, execution, and validation, with clearly defined milestones and risk mitigation strategies at each stage.
How is data migrated from NAV to Business Central?
Data migration from NAV to Business Central involves upgrading the NAV database through the required intermediate versions to reach the target Business Central version. Master data including customers, vendors, items, chart of accounts, and fixed assets is migrated along with open transactions such as purchase orders, sales orders, and outstanding invoices. Historical transaction data across all modules is preserved. Aedista performs multiple test migrations before the actual cutover, running detailed reconciliation reports at each step to verify that financial balances, inventory quantities, and open document counts match exactly between the source NAV system and the target Business Central environment.
What happens to my NAV customizations during the migration?
NAV customizations written in C/AL code are converted to AL extensions as part of the migration process. Aedista audits every customization in your NAV environment during the analysis phase, categorizing each one as: convertible to AL with equivalent functionality, replaceable by standard Business Central features or AppSource extensions, or requiring a fresh rebuild as a modern AL extension. ISV add-ons such as Pebblestone, Lanham, Insight Works, and others are evaluated for Business Central-compatible versions or suitable replacements. In our defense manufacturer case study, we successfully migrated a heavily customized NAV 2017 system with full Pebblestone and Lanham Shipping integration to Business Central 24 SaaS while preserving all critical business logic.
Can I run NAV and Business Central in parallel during the transition?
Yes, running NAV and Business Central in parallel during the transition period is a standard part of the Aedista migration methodology. During the validation phase, your team works in both systems simultaneously to verify that all business processes, reports, and workflows function correctly in Business Central before the final cutover. This parallel-run period typically lasts 2 to 4 weeks and allows your team to build confidence in the new system while maintaining business continuity on NAV. We also develop detailed cutover plans with defined rollback procedures, so if any critical issues are discovered during the parallel run, you can continue operating on NAV while the issues are resolved.
