Microsoft dynamics nav migration checklist for NAV 2016 and NAV 2018 sites — pre-flight discovery, C/AL/AL inventory, partner add-on triage, multi-company sequencing, compliance archive design, parallel-run rigor, decommission readiness. The artefact that turns NAV-to-Fusion intent into actionable, sign-off-able phases.
A bullet-pointed wish list is not a checklist. A serviceable microsoft dynamics nav migration checklist has named owners, target dates, acceptance criteria and sign-off gates. It's the readiness gate before each phase and the audit trail after the programme.
Microsoft Dynamics NAV — Navision before 2002, Dynamics NAV 2005–2018, Business Central as the Microsoft cloud successor — runs across thousands of mid-market sites in DACH, the Nordics, UK and US SMB. The depth of customisation, partner add-on entanglement, multi-company complexity and country-specific compliance load accumulated over 10–20 years means a NAV-to-Fusion migration cannot be run from a 10-bullet checklist. The microsoft dynamics nav migration checklist that actually works is 60–120 items, structured by phase, with named owners and acceptance criteria per item.
The NAV 2016 extended-support cliff (April 2026) and NAV 2018 extended-support cliff (January 2028) make the checklist time-sensitive. From April 2026 there are no NAV 2016 security patches, no tax-table updates for HMRC MTD or GoBD or SAF-T, no Microsoft escalation path for production incidents. The microsoft dynamics nav migration checklist treats the EOL date as a backward-planning constraint — production cutover at least 3 months before EOL to provide parallel-run cushion and post-cutover stabilisation. For NAV 2016 that means discovery starts no later than September 2025; for NAV 2018, no later than September 2027.
The Syntra ETL platform builds a substantial portion of the checklist into the platform itself. The Object Designer crawler executes the C/AL/AL inventory items. The partner add-on signature scan executes the add-on inventory items. The compliance archive playbooks execute the GoBD/HMRC/SAF-T design items. The reconciliation engine executes the parallel-run reconciliation items. The microsoft dynamics nav migration checklist becomes shorter on the customer side because the platform absorbs the technical readiness work.
Each block addresses a NAV-specific risk area. None can be skipped without a corresponding overrun risk later in the programme.
12–18 items covering Object Designer enumeration, custom-object classification, owner identification, prior-upgrade history. Output drives crosswalk design phase as primary input.
8–14 items covering Anveo, ChargeLogic, Continia, Insight Works inventory, per-add-on retire/replace/keep decisions, vendor coordination, subscription cancellation planning.
8–12 items covering NAV per-company inventory, Fusion BU/ledger mapping, intercompany reconciliation at source, per-company cutover sequencing.
14–22 items covering per-jurisdiction retention (GoBD 10y, HMRC 6y, SAF-T 5–10y, SDI 10y, CFDI 5y, SPED 5y), audit-pack format, hash-signing, read-access logging.
12–18 items covering NAV delta capture, daily reconciliation cadence, month-end reconciliation pack, cutover run-sheet, rollback triggers, downstream-system coordination.
8–14 items covering archive verification, NAV read-only mode, Microsoft Enhancement Plan cancellation, SQL Server retirement, partner add-on subscription cancellation, hardware decommission.
Working backward from the NAV 2016 (April 2026) or NAV 2018 (January 2028) extended-support cliff. The checklist makes the EOL pressure concrete and the discovery start date specific.
Object Designer crawl scheduled, NAV version confirmed, partner add-on signature scan scheduled, multi-company inventory drafted, compliance archive scope documented, history depth decided. For NAV 2016 April 2026 EOL: discovery starts September 2025 at latest.
Crosswalks signed off, dimension-to-COA mapping signed off, posting-group-to-SLA signed off, partner add-on disposition signed off, compliance archive design signed off by internal audit. Target Fusion shape confirmed.
Extractors configured, transforms configured, FBDI emission verified against Fusion 26x schemas, dress-rehearsal load completed end-to-end against production-shape data, reconciliation engine configured, sign-off pack template confirmed.
Production parallel-run window starts. 1–2 month-end cycles minimum. Daily NAV vs Fusion reconciliation. Variance log opened. All variances root-caused and fixed before cutover sign-off.
Cutover weekend executed with named owners, rollback triggers monitored, NAV switched to read-only, hyper-care command centre opens. Statutory submission cutover (HMRC MTD, GoBD GDPdU, SAF-T, SDI) coordinated.
Hyper-care stabilisation complete. Archive verification signed off by audit. NAV licence and SQL Server retirement coordinated. Partner add-on subscription cancellation per vendor. Hardware decommission scheduled. EOL date arrives with no live NAV dependency.
Skipped items correlate strongly with month-4-to-month-8 overruns. The items below are the ones consistently absent from checklists that later derail.
Which custom objects survived which prior NAV version upgrades reveals brittleness. Objects touched in every prior upgrade are typically the heaviest crosswalk effort in Fusion migration.
Anveo, ChargeLogic, Continia, Insight Works each have renewal dates and notice-period requirements. Missed cancellation = another year's subscription paid post-NAV-decommission.
HMRC MTD VAT return, GoBD GDPdU export, EU SAF-T per country, Italian SdI rehearsed end-to-end before first live submission. 'First time live' on a statutory deadline is preventable.
Per-bank file format (BACS, SEPA, CHAPS, ACH, country-specific) cutover from NAV to Fusion coordinated with each bank. Often skipped, causes Day-1 payment processing failures.
Who uses which Jet Report, with what frequency, replacing what business process. Missing inventory means post-cutover reporting gaps surface as user complaints, not planned migrations.
Compliance-archive hash-signing keys need long-term custody (10+ year retention for GoBD). Skipped = audit-evidence pack is unverifiable when needed.
A microsoft dynamics nav migration checklist is the pre-flight artefact that converts NAV-to-Fusion migration intent into actionable, sign-off-able tasks. A serviceable checklist is 60+ items grouped by phase — discovery, design, build, validate, cutover, decommission — each with named owner, target completion date, and acceptance criterion. The microsoft dynamics nav migration checklist is not a project plan; it is the readiness gate before each phase, and the audit trail after the programme. A 10-item bullet list is not a checklist — it's wishful thinking. A 300-item exhaustive list is overkill — it becomes ceremonial. 60–120 items, structured by NAV-specific risk areas (C/AL/AL inventory, partner add-ons, multi-company, GoBD/HMRC/SAF-T), is the sweet spot for mid-market NAV-to-Fusion programmes.
NAV 2016 extended support ends April 2026; NAV 2018 January 2028. The microsoft dynamics nav migration checklist treats the EOL date as a fixed-point backward-planning constraint — production cutover must land at least 3 months before EOL to provide parallel-run cushion and stabilisation. From EOL date the checklist works backward: 3 months stabilisation buffer + 4–6 weeks parallel run + 4–6 weeks final cutover prep + 8–12 weeks build/transform/load + 6–10 weeks crosswalk design + 2–4 weeks assessment = 27–43 week total. So a NAV 2016 site targeting April 2026 EOL should start discovery no later than September 2025. The microsoft dynamics nav migration checklist makes the timeline visible and the EOL pressure concrete rather than abstract.
The C/AL/AL inventory block of the microsoft dynamics nav migration checklist runs 12–18 items typically. Sample items: Object Designer access provisioned with read-only credentials. Custom-object enumeration complete (custom tables 50000-99999, custom fields on standard tables, modified standard objects, custom codeunits, custom pages, custom reports RDLC + Word layout, custom XMLports, custom queries). Each custom object classified by business purpose (retire / replace / preserve / rebuild). Customisation owner identified per object (original developer name, current owner if different, last modified date). Customer Object Designer changes signed off by IT leadership. Inventory artefact stored in shared evidence pack. C/AL → AL upgrade history documented (which objects were touched in any prior NAV version upgrade). The output goes into the crosswalk design phase as input.
The partner add-on block runs 8–14 items typically. Sample items: complete add-on inventory (Anveo, ChargeLogic, Continia OPplus, Insight Works, regional specialists). Per-add-on licence record (vendor, version, renewal date, primary contact). Per-add-on data-footprint analysis (which custom tables, which row volume, which business processes depend on it). Per-add-on retire/replace/keep decision documented and signed off. For replace decisions: Fusion equivalent identified, integration partner identified, transition plan documented. For retire decisions: data extraction and archive plan documented. For keep decisions (very rare in NAV-to-Fusion): coexistence integration design documented. Vendor coordination contact made for each add-on. Licence-stack retirement coordination plan documented.
The multi-company block runs 8–12 items. Sample items: full NAV company inventory (Company1, Company2, Company3 — each company's name, country, currency, fiscal calendar, statutory framework). Per-company Fusion BU + ledger mapping documented and signed off. Intercompany G/L Entry pairs reconciled at NAV source (intercompany imbalance fixed before extraction). Per-company extraction sequence planned (parallel against SQL replica, no production server load). Per-company cutover sequence planned (which company cuts first, which last, dependencies). Intercompany reconciliation engine configured for post-load Fusion validation. Per-company sign-off authority identified (typically country finance lead). Per-company hyper-care arrangement documented.
The compliance archive block runs 14–22 items depending on jurisdiction count. Sample items per jurisdiction: retention window confirmed against current regulation (GoBD 10-year, HMRC 6-year, EU SAF-T 5–10-year per country, Italian SDI 10-year, Mexico CFDI 5-year, Brazilian SPED 5-year). Audit-pack format documented per regulator. Read-access logging requirement documented per regulator. Hash-signing scheme designed (which fields go into the hash, signing-key custody). Archive storage location decided (Fusion-side vs NAV-side long-term archive). Read-access procedure documented for tax/audit team. Test-run of audit-pack extraction completed with sign-off from internal audit. The microsoft dynamics nav migration checklist treats compliance archive as a first-class deliverable, not as a phase-2 afterthought.
The parallel-run / cutover block runs 12–18 items. Sample items: parallel-run window scheduled (1–2 month-end cycles minimum). NAV delta capture configured (SQL Server change tracking or Modified DateTime field). Daily NAV vs Fusion reconciliation cadence scheduled. Month-end reconciliation pack template prepared (trial balance, AR aging, AP aging, inventory valuation — all NAV-vs-Fusion to the cent). Variance investigation log opened (every reconciliation variance logged, root-caused, fixed before cutover sign-off). Cutover weekend run-sheet prepared with named owners per task and rollback-trigger criteria. Communication plan documented (user notification, downstream-system notification, banking partner notification). NAV read-only switch tested. Banking-file, EDI, payroll, tax-submission cutover all coordinated by named owner. Go/no-go review meeting scheduled with sign-off authority.
The decommission block runs 8–14 items. Sample items: archive verification complete (all required history accessible in long-term archive, signed off by audit). NAV read-only mode active and tested. Microsoft Enhancement Plan renewal cancellation documented (next renewal date, cancellation lead-time complied with). SQL Server licence retirement coordinated with infrastructure team. Windows Server CAL retirement coordinated. Partner add-on subscription cancellation coordinated per vendor (Anveo, ChargeLogic, Continia, Insight Works). NAV-specialist headcount transition plan (retraining for Fusion or contract end). Hardware decommission scheduled (database server, application server, file server). Backup retention policy documented post-decommission (final backups retained per audit policy). Decommission completion certificate signed by IT, finance, audit.
Book a 30-minute discovery call. We'll walk through your NAV version, EOL date, customisation depth, partner add-on inventory, multi-company estate, compliance scope and decommission planning — and give you a backward-planned, EOL-anchored microsoft dynamics nav migration checklist before the call ends.