NAV-to-Business Central Upgrade: 2-Week Assessment by AppSource ISV

Most NAV-to-Dynamics 365 Business Central upgrades fail in places nobody warned you about. The cutover weekend runs twelve hours longer than planned because data migration was never tested at production scale. Three custom modifications you forgot about block the Cloud Migration Tool. An ISV add-on you assumed would auto-upgrade requires a complete rewrite. The Latvian, Estonian, or Swedish localization layer needs decisions you didn't realize you were making.

Over 90+ NAV and Dynamics 365 Business Central implementations — including 46+ Swedish migrations from NAV 2009 through NAV 2018, database sizes from 5 GB to 800 GB — JEMEL has run into these failure modes before. This 2-week paid assessment surfaces them in writing, with a costed plan, a risk register, and a path through, so the upgrade project is scoped honestly before it starts.

JEMEL is a Microsoft Partner and publisher of 12 extensions on Microsoft AppSource — Bank Gateway, Baltic EDI, Asset Pro, Latvian and Estonian Localization, Shopify Connect, Notify User, and others. The person you talk to writes the AL code and runs the cutover. No account management layer, no handoff.

What the assessment surfaces

• Version-bridge path — exact upgrade route from your NAV version to Dynamics 365 Business Central, Cloud Migration Tool eligibility, intermediate version steps where required.
• Customization fit-gap — every modification classified as keep-as-extension, replace-with-standard, replace-with-AppSource-app, or retire. Typical NAV codebases lose 30-40% of customizations to standard Dynamics 365 Business Central features that didn't exist when the customization was built.
• ISV add-on assessment — Continia, ExFlow, Swebase, Tasklet, Lasernet, and others. For each: AppSource alternative, upgrade path, or rebuild scope.
• Large-database cutover modeling — for databases over 50 GB, realistic cutover window estimation including the custom SQL scripts that the standard upgrade toolkit doesn't generate.
• Localization strategy — Baltic (Latvian, Estonian, Lithuanian) and Nordic (Swedish, Danish) statutory reporting, bank formats, e-invoicing, payroll handling.
• Integration architecture — current interfaces mapped to Dynamics 365 Business Central-native APIs, AppSource connectors, Power Platform flows, or custom Azure middleware.
• Hardware refresh — scanner, POS, label printer compatibility. Legacy Windows CE devices typically need replacement.

What you receive after two weeks

• A 20-30 page written assessment report covering all areas above with specific recommendations
• A cost estimate broken down by workstream — development, data migration, localization, integrations, testing, cutover, hypercare
• A project timeline with milestone-level phasing and identified critical path
• A risk register with named risks, mitigation actions, and contingency budget
• An AppSource fit-gap map showing which extensions cover which functional areas, including JEMEL's own where they apply

How it works

Week 1: Discovery sessions with your team (on-site or remote). Technical analysis of the NAV codebase, schema, customizations, and integrations. Database profiling and ISV add-on inventory.

Week 2: Synthesis and document production. Cost modeling, risk identification, deliverable writing. Final delivery with a presentation walkthrough.

Fixed-fee paid engagement. The assessment fee is credited toward the implementation cost if you proceed with JEMEL for the full project. Microsoft AIM Program incentives apply where eligible — we help with the AIM Assessment Report submission.

About JEMEL

JEMEL SIA is a Microsoft Partner based in Riga, Latvia. 20 years in the Microsoft Dynamics ecosystem. 90+ Dynamics 365 Business Central and Dynamics NAV implementations completed. 12 published extensions on Microsoft AppSource. We serve Baltic, Nordic, and EU customers in English, Latvian, and Russian.

jemel.lv/en/services/business-central-upgrade