Microsoft is sunsetting Dynamics NAV. Every NAV customer needs to migrate to Business Central — but the path isn't trivial. Here's the 7-step checklist we use on every NAV-to-BC migration in the Gulf.
Why every NAV customer needs to migrate
Microsoft Dynamics NAV reached end-of-mainstream-support in 2028 for most version branches. Beyond that, no new security updates, no new feature releases, no Microsoft technical support. NAV 2018 customers are already on borrowed time; NAV 2013 and earlier are unsupported today.
Business Central is the direct evolution path — same data model, similar UX, but cloud-first with native Copilot, AppSource extensions, and modern integration. Every NAV customer should be on a migration plan by mid-2026.
Step 1 — Licence and tenant review
Confirm your current NAV licence (per concurrent user, per session, custom granules). Microsoft will offer you a Business Central transition price that's tied to your existing NAV investment — don't sign anything before requesting this transition quote.
Decide tenant strategy: single Microsoft 365 tenant, or do you have multiple? BC ties to one M365 tenant per environment. Plan for consolidated identity (Entra ID) at this stage.
Step 2 — Choose deployment: cloud, hybrid, or on-prem
For 90% of NAV customers, cloud SaaS BC is the right answer. The exceptions:
- Strict data-residency rules with no Azure-region match
- Existing massive on-prem infrastructure with 4+ years of useful life
- Heavily customised NAV with offline-critical scenarios
Default to cloud SaaS unless a real blocker exists. Cloud avoids hardware refresh, upgrade outages, and patch operations.
Step 3 — Customisation analysis (C/AL → AL)
NAV customisations are in C/AL. BC extensions are in AL. The translation is straightforward conceptually but every NAV customer has hundreds to thousands of lines of C/AL to audit.
Run the Code Customization Analyzer (Microsoft tool) against your NAV database. It outputs every customised object, every modification, and whether each has a 1:1 BC standard alternative. Typically 60–80% of NAV C/AL is no longer needed in BC because BC's standard features replaced it.
Step 4 — Build data migration toolkit
Master data, open transactions, historical balances. We use a 4-pass migration:
- Pass 1: Setup (chart of accounts, dimensions, posting groups, number series)
- Pass 2: Master (customers, vendors, items, fixed assets)
- Pass 3: Open transactions (open AR, AP, sales orders, purchase orders, inventory balances)
- Pass 4: Historical (closed transactions for the past 2–5 years, depending on audit requirements)
Pass 4 is optional — many customers keep NAV as read-only archive instead of migrating 10 years of history.
Step 5 — UAT in a sandbox tenant
Microsoft provides a sandbox BC tenant for every production tenant. Run your top 20 business processes end-to-end in the sandbox with real data and real users. Document gaps in writing; either resolve via AL extension or accept the standard-BC behaviour.
Step 6 — Cutover and go-live
Cutover weekend: freeze NAV (read-only), run final delta migration, switch user access. Typical cutover window is 36–48 hours; planning starts 6 weeks before. Communicate the freeze window to every dependent system (eCommerce, bank, freight) two weeks in advance.
Step 7 — Post-go-live hyper-care
First 2–4 weeks: daily standup, 4-hour issue triage SLA, on-call developer for emergencies. Issue volume drops 60–70% per week typically. Hand over to NovaCare AMC by week 4–6.
Frequently asked questions
How long does a NAV to BC migration take?
8–16 weeks for a typical single-entity rollout, 4–6 months for multi-entity with heavy customisations. Run discovery first to scope your number.
Do we lose features moving from NAV to BC?
Almost never. BC inherits everything NAV had and adds cloud-native capabilities. The pain is in C/AL-to-AL rewrites of customisations, not feature loss.
Can we keep our NAV customisations?
Functionally yes — the equivalent AL extension delivers the same behaviour. The code itself has to be re-written. Microsoft's Code Customization Analyzer maps every NAV object to its BC counterpart.
What's the cost?
Typically AED 280k–650k for a 25–100 user UAE NAV customer migrating to BC. The savings appear within 12 months via reduced upgrade overhead and modern AppSource extensions.
Does BC handle our historical NAV data?
Yes. You can either fully migrate historical transactions or keep NAV as read-only archive. Most customers do the latter for years 4+ of history.
Can we go live by Q4 if we start now?
Yes if you start by Q2 with a 12–18 week budget. We've delivered Q4 NAV-to-BC migrations in the Gulf consistently.
Where to go next
Read the full overview of Business Central in the Gulf. For a deeper dive into related capability, see NovaCare post-go-live support. When you're ready to talk specifics, book a 30-minute call with a Novasoft consultant.