Overview
This post explains why NAV to Business Central migrations often go wrong when led by a generalist partner. It covers the technical differences between the two platforms and what specialist knowledge actually looks like. You’ll also find Microsoft’s support timeline for NAV and the questions worth asking before you sign anything.
Most Microsoft Dynamics NAV migrations run into trouble for the same reason. The partner leading the project doesn’t know NAV well enough, doesn’t know Business Central well enough, or both.
That gap is where projects stall, budgets overrun, and businesses end up with a system that works on paper but causes daily frustration in practice. At Tecvia, we work exclusively in the Microsoft Dynamics space, handling NAV to BC migrations across manufacturing, distribution, professional services, and retail.
This article explains what a successful migration actually requires. Your choice of partner determines the outcome before a single line of code is written.
NAV And Business Central Are Not The Same Product
This is the most important thing to understand before you start planning.
NAV and Business Central share a commercial lineage, but they’re built on entirely different technical foundations. Moving from one to the other isn’t a version upgrade. It’s a re-architecture.
The NAV environment you’re leaving runs C/AL code inside the Classic Client or RoleTailored Client, with customisations often baked into the base application without documentation. Years of workarounds sit layered on top of each other, typically managed on-premises by an internal IT team.
The Business Central environment you’re moving into works differently. It uses AL Language with an extension-based architecture, so customisations sit outside the base application entirely. Cloud-first design means Microsoft manages updates and security patches, while API-driven connectivity links you to third-party tools and Microsoft 365. Anyone who tells you this is a straightforward upgrade hasn’t done it properly.
What A Generalist Partner Gets Wrong
A generalist Dynamics partner may have solid Business Central knowledge. What they typically lack is deep familiarity with NAV, and that gap creates real problems in practice.
Your customisations are the issue. In NAV, modifications live inside the base application code, so your partner needs to read C/AL code written years ago, often with no documentation. They need to identify which modifications are genuinely needed and which are outdated workarounds, then translate that logic into AL extensions that work within BC’s architecture.
Testing against your actual business processes matters too, not just a demo environment. A partner who skips the analysis stage will carry forward the problems you already have, plus create new ones.
We’ve seen this happen. A manufacturing business came to Tecvia after an initial migration left their production reporting broken, because the previous partner had missed a set of custom NAV fields entirely. Six months of painful manual reconciliation followed before the data was corrected.
What Deep NAV And BC Knowledge Looks Like In Practice
Here’s the difference between a specialist and a generalist at each stage of a migration project.
On the NAV side, a specialist conducts a full object and customisation audit before writing a single line of AL code. They identify deprecated features that need re-engineering rather than simply porting across, and they know which NAV modules behave unexpectedly during data migration. Because each NAV version has its own quirks, understanding your specific version matters.
On the Business Central side, a specialist designs extensions that follow Microsoft’s recommended patterns, so future release wave updates don’t break your system. They evaluate whether a cloud SaaS deployment or on-premises installation suits your infrastructure, then connect BC to your existing tools via APIs rather than clunky direct database integrations. This same attention to detail applies to financial management configuration and Power BI reporting setup.
Both skill sets are required. One without the other isn’t enough.
AI Tools And Your NAV To BC Migration
Microsoft has introduced Copilot AI across Business Central, and it changes what the system can do once you’re live. This is worth factoring into your migration planning now, because our guide to what Business Central’s AI actually does covers the detail.
AI in Business Central currently covers natural language queries, so users can ask questions in plain English without training on menu structures. Automated bank reconciliation matches statement lines to posted ledger entries, while sales line suggestions recommend items based on what a customer has ordered before, similar to the logic behind the Sales Order Agent. Cash flow forecasting uses your historical data to project cash positions, a significant step up from what was available in NAV.
None of these capabilities exist in NAV. They’re part of what you gain by moving to Business Central, but only if your migration is set up correctly. At Tecvia, we build Copilot readiness into every migration project, drawing on the same principles covered in our guide to features many businesses already pay for.
Questions To Ask Any Partner Before You Sign Anything
Don’t rely on a partner’s marketing materials. Ask these questions directly and listen carefully to how specific the answers are.
Ask how many NAV to BC migrations they’ve completed in the past two years, and from which NAV versions. Ask how they approach the customisation audit, and whether they can show a case study from a business of similar size and complexity to yours.
Ask who specifically will work on your project, what their Dynamics background is, and how they handle customisations that can’t be directly ported to AL. Ask about post-go-live support, pricing, and their approach to Copilot readiness. Vague answers about extensive experience tell you nothing. Specific projects, specific versions, and named individuals tell you a great deal.
The Real Cost Of Getting This Wrong
A failed or poorly executed migration is expensive in ways that go beyond the original project invoice.
Downtime during go-live disrupts operations and damages customer confidence. Months of manual reconciliation follow when data doesn’t migrate cleanly, and rebuilding customisations that were missed or incorrectly ported adds further delay. Staff frustration builds when the new system doesn’t match how people actually work, similar to the stock visibility issues that come from poor configuration elsewhere in the system.
A second migration project to fix the first one is more common than it should be. So is delayed access to Copilot AI tools, because the system configuration wasn’t set up correctly from the start. None of this is hypothetical. It happens when businesses treat this as a routine software upgrade rather than the considered re-architecture project it actually is.
Microsoft’s End Of Support Timeline For NAV
If you’re still running NAV, there’s a timeline you need to be aware of.
NAV 2013 and earlier reached the end of extended support in 2023. NAV 2015’s extended support ended in January 2025, while NAV 2016’s ends in April 2026. NAV 2017’s extended support ends in April 2027, and NAV 2018’s ends in January 2028.
Running on an unsupported NAV version means accepting security risk with no path to a vendor fix. For many businesses, migration to Business Central is a compliance and security requirement rather than a product preference.
Note that Microsoft support dates can change. Confirm current dates at microsoft.com/en-us/licensing/product-licensing/products, or speak to Tecvia directly.
Why Tecvia
Tecvia works exclusively in the Microsoft Dynamics space, with hands-on experience across multiple NAV versions and industries. We don’t outsource our core project work, so the people who scope your migration are the people who deliver it.
Every project starts with a structured assessment of your current NAV environment. We document what you have, categorise your customisations by complexity, and produce a migration plan you can examine before any development work begins.
We work with your internal team throughout the implementation, because our goal is to leave you with a system your people understand and can manage. We don’t want you dependent on us for routine tasks.
Talk To A Migration Specialist
A NAV to Business Central migration is not the place to gamble on a generalist partner. Tecvia gives you an honest assessment of what your environment requires, including a realistic timeline, budget range, and view of risk.
Get in touch for a free consultation, or ask us for a demo of what your migrated environment could look like. Our support team stays involved well beyond go-live. Contact Tecvia to start your customisation audit.
FAQs
For anything not covered here, get in touch directly. We’re happy to answer questions specific to your business and your ERP requirements.
It depends on the complexity of your current environment. A NAV 2018 system with limited customisations can migrate in three to four months. A heavily modified NAV 2013 environment with complex integrations may take six to twelve months. The customisation audit at the start of any project produces a reliable estimate before work begins.
No. Business Central is available as a cloud SaaS product and as an on-premises installation. Your choice depends on your infrastructure, data residency requirements, and internal IT capability. Tecvia will assess both options with you and recommend based on your situation, not on what is easiest for us to deliver.
Each customisation is reviewed during the audit phase. Some will be rebuilt as AL extensions. Others may be replaced by standard BC functionality that did not exist in your version of NAV. A small number may be retired if they no longer serve a business purpose. You will know exactly what is happening to each one before migration starts.
Yes, and for many businesses this is the right approach. Running both systems in parallel reduces go-live risk and gives your team time to build confidence in BC before you fully cut over. The practicalities depend on your data volumes and integration points, which Tecvia reviews as part of project planning.
Training is built into every Tecvia migration project. We work with your key users throughout the project so they understand Business Central before go-live, not after. We also document your specific configuration so your team has a reference they can actually use day to day.
Training is built into every Tecvia migration project. We work with your key users throughout the project so they understand Business Central before go-live, not after. We also document your specific configuration so your team has a reference they can actually use day to day.
Tecvia provides post-go-live support as standard. Our team remains available during the critical first weeks after cutover. For ongoing support beyond that period, we offer managed support agreements tailored to your needs.
Yes. We regularly take on migration projects where a previous partner relationship has broken down or where the business wants a specialist team for the migration specifically. We request access to your NAV environment and existing documentation, assess what has been done, and produce a clear plan from that point forward.
