Dynamics NAV to Business Central — upgrade and migration
Twenty years in the Microsoft Dynamics ecosystem. 90+ implementations completed. Twelve published extensions on Microsoft AppSource covering Baltic and Nordic markets. Founder-led delivery from assessment through cutover.
Why upgrade now
Dynamics NAV is in long-term decline. Microsoft has ended mainstream support for NAV 2018 and earlier, and the platform receives no new functionality. Innovation — Copilot, modern AL extensions, Power Platform integration, AppSource ecosystem — has moved entirely to Business Central.
The question is not whether to upgrade but how. Staying on NAV gets more expensive each year: no security patches, no compliance updates, growing distance from the partner skill pool, increasing exposure to localization gaps when statutory requirements change.
Business Central solves these problems, but the upgrade is a real project. It is also an opportunity. Most NAV deployments eliminate 30–40% of their custom code by adopting standard BC features that did not exist when the original customization was built. Done well, an upgrade leaves the business with a smaller, cleaner, more maintainable system than it had before.
Assessment first
Before any code is touched, the right questions need to be answered. JEMEL's upgrade engagements start with a paid assessment that produces concrete deliverables — not a sales pitch dressed as a discovery call. The assessment fee is credited toward the full project if you proceed.
Target platform
Business Central Online (SaaS) or on-premises. We support both and shape the architecture so a later move between them stays open. We assess Cloud Migration Tool eligibility for your NAV version — NAV 2015 onwards is eligible via the BC v14 bridge; NAV 5.0 and earlier follow a staged upgrade path.
Customization scope
Every NAV modification is classified — keep as AL extension, replace with standard BC functionality, replace with AppSource app, or retire. Typical NAV deployments eliminate 30–40% of custom code by adopting standard BC features that did not exist when the customization was originally built.
AppSource fit-gap
We map your current add-ons against AppSource alternatives, including our own published extensions where they fit. You get clarity on licensing, ongoing cost, and ownership for each functional area.
Localization strategy
Baltic (Latvian, Estonian, Lithuanian) and Nordic (Swedish, Danish) localization options — statutory reporting, bank formats, e-invoicing (Finbite, Latvian EDI), and payroll handling. Keep in Business Central or run externally.
Data scope
Full history migration versus open balances with archived legacy access. We model the trade-offs between project cost, go-live complexity, and ongoing access to historical records.
Integration architecture
Current interfaces (EDI, e-commerce, bank, CRM, peripherals) mapped to BC-native APIs, AppSource connectors, Power Platform flows, or custom Azure middleware — whichever fits the integration profile and total cost of ownership.
Hardware and peripherals
Scanner, POS, label printer, and other peripheral hardware reviewed for BC compatibility. Legacy Windows CE devices typically need replacement with Android rugged scanners.
Assessment deliverables
From the assessment engagement you receive a complete decision package, not a sales document.
- A written assessment report covering the seven areas above with our recommendations
- A cost estimate broken down by workstream — development, data migration, localization, integrations, testing, cutover, post-go-live support
- A project timeline with milestone-level phasing and identified critical path
- A risk register with mitigation actions and contingency budget
- An AppSource fit-gap map showing which extensions cover which functional areas
Full migration delivery
Beyond assessment, JEMEL delivers the full upgrade end to end.
Build and test
Sandbox environment setup, AL extension development for custom requirements, AppSource extension configuration, data migration scripts, integration build, iterative UAT cycles with the customer team.
Cutover
Production cutover delivered over a planned weekend, typically 24–32 hours including data freeze, final delta migration, integration switchover, and validation. The cutover plan is rehearsed in advance using sandbox — no improvisation on go-live weekend.
Hypercare
For the first two months after go-live, JEMEL provides priority response and proactive monitoring. Most stability issues surface within this window and are resolved before transitioning to standard support.
Why JEMEL
JEMEL has been in the Microsoft Dynamics ecosystem since 2006. We have completed more than 90 NAV and Business Central implementations across the Baltic states (Latvia, Lithuania, Estonia) and the Nordic markets (Sweden, Denmark). We are a Microsoft Solutions Partner for Business Applications.
We publish 12 extensions on Microsoft AppSource — Bank Gateway, Baltic EDI, Latvian and Estonian Localization, Asset Pro, Shopify Connect, Notify User, Currency Rates, Job Queue Admin, and others. Building extensions is not a side activity for us. It is how we know the platform from the inside.
Our delivery model is founder-led. We deliberately keep the team small and work with a limited number of clients where the fit is right. Several of our customer relationships now exceed 10 years. The person you talk to on the assessment call is the person who will write the AL code and run the cutover weekend — no account management layer, no handoff.
Working languages: English, Latvian, Russian.
Our published AppSource extensions
Frequently asked questions
Which NAV versions can be upgraded?
All versions from NAV 4.0 onwards. The path depends on the starting version. NAV 2015 onwards can use the Microsoft Cloud Migration Tool via a BC v14 bridge step. Older versions (NAV 5.0 and earlier) follow a staged upgrade through intermediate NAV versions before reaching BC. The assessment determines the exact path.
Cloud or on-premises?
Both are supported. Business Central Online (SaaS) is the modern default and unlocks Copilot, Power Platform, and the AppSource ecosystem. On-premises remains viable for specific regulatory or integration requirements. The assessment shapes the target so a later move between them stays open.
How long does an upgrade take?
The honest answer is "it depends on your customizations." A standard NAV deployment with limited modifications can complete in 3–4 months. A heavily customized deployment with extensive integrations can run 6–12 months or more. The assessment produces a real timeline based on your specific situation, not a generic estimate.
What happens to our customizations?
Every NAV modification is classified into one of four outcomes — keep as AL extension, replace with standard BC functionality, replace with AppSource app, or retire. Typical NAV deployments eliminate 30–40% of custom code by adopting standard BC features that did not exist when the customization was originally built. The assessment produces this classification for your specific codebase.
What about our integrations?
Each integration is reviewed against BC-native APIs, AppSource connectors, Power Platform flows, and custom Azure middleware as options. The right answer depends on the integration profile, total cost of ownership, and how the integration is expected to evolve. EDI, e-invoicing, banking, e-commerce, CRM, and peripheral integrations are all covered.
What does an assessment cost?
Assessment scope and cost depend on the complexity of the existing NAV deployment. Contact us for an initial scoping conversation. The assessment fee is credited toward the full project if you proceed with JEMEL for the implementation.
Ready to scope your upgrade?
Start with an assessment. You receive a complete decision package — report, cost estimate, timeline, risk register, AppSource fit-gap map — and the fee is credited toward the project if you proceed.