Structured 2–3 week microsoft dynamics nav migration assessment. NAV version, C/AL vs AL customisation depth, partner add-ons (Anveo, ChargeLogic, Continia, Insight Works), data volumes, multi-company shape, statutory obligations, NAV 2016 April 2026 cliff exposure. Sized timeline + budget.
Consultant-led migrations spend the first four months in workshops trying to figure out what is in the NAV estate. A real assessment does it in three weeks with machinery, not interviews.
NAV deployments are not greenfield. They have been running for 10, 15, sometimes 20 years — from Navision Attain through Microsoft Navision through Dynamics NAV 2005, 2009, 2013, 2015, 2016, 2017 and 2018. Over that window, in-house developers and partner consultants have written C/AL modifications, added custom tables in the 50000-99999 range, installed partner add-ons (Anveo, ChargeLogic, Continia, Insight Works, LS Retail, regional specialists), built RDLC reports and Word layout reports, deployed Jet Reports Excel templates on every finance laptop. Nobody at the customer has a complete inventory in their head. Workshops don't produce one either.
A real microsoft dynamics nav migration assessment runs machinery. The Object Designer crawler enumerates every NAV object. The SQL Server profiler estimates every table's row volume. The partner add-on signature scan recognises every installed third-party module. The statutory obligation register cross-references the operating jurisdictions against NAV's localisation features. Each output is empirical, time-stamped and version-controlled. The customer's IT and finance leads see what is actually there, not what the lunch-room consensus says is there.
Whether you are running NAV 2016 on SQL Server 2014 in a German factory facing the April 2026 cliff, or NAV 2018 across UK, Ireland and France with HMRC MTD and EU SAF-T obligations, or a Navision-era database still doing payroll for a Nordic subsidiary — the same assessment engine runs, the same outputs ship, the same sized timeline and budget land on the finance committee desk.
The variables that drive a NAV → Fusion migration's timeline, budget and risk — each one inventoried as a discrete output in the assessment.
NAV 5.0 / 2009 / 2013 / 2015 / 2016 / 2017 / 2018 detected from SQL Server schema and Object Designer metadata. NAV 2016 extended-support cliff April 2026, NAV 2018 January 2028.
Object Designer crawler enumerates every modified standard object and every custom object in 50000-99999. C/AL (pre-2018) and AL (2018+) both classified.
Signature scan identifies Anveo, ChargeLogic, Continia, Insight Works, LS Retail, Tasklet Factory, Mekorma and regional specialists. Per-vendor playbook decisions.
SQL Server profiler estimates row volumes for top 20 tables. G/L Entry 17 and Item Ledger Entry 32 are typically the long pole.
Per-company database inventory. NAV's per-company segmentation makes Company1, Company2, Company3 visible. Consolidation shape recommended.
GoBD (DE), HMRC MTD (UK), SAF-T per-country (NO, PL, PT, FR, LT, RO), Intrastat, SdI (IT), CFDI (MX), SPED (BR) — cross-referenced to NAV localisation features.
A repeatable 2–3 week assessment, read-only access, no NAV admin downtime, signed output ready for finance committee.
Scope agreed: which companies, which NAV versions, which jurisdictions, which subledgers in scope. Read-only access provisioned to SQL Server backend or recent backup restored to sandbox. NAV application metadata extracted.
Crawler enumerates every NAV object — tables, fields, keys, pages, codeunits, reports, XMLports, queries. Standard vs modified-standard vs custom classification applied. C/AL vs AL distinction captured. Output: customisation register v0.1.
SQL Server profiler estimates row counts and storage for top 20 tables across every company in scope. G/L Entry 17, Item Ledger Entry 32, Sales Header/Line, Purchase Header/Line, masters — empirical row counts captured.
Add-on signature scan against NAV application metadata. Per-vendor playbook decisions drafted. Statutory obligation register cross-referenced against NAV localisation features and operating jurisdictions.
Timeline and budget calibrated from the assessment outputs. Risk register populated. Recommended sequencing of work drafted. Draft assessment report v0.1 circulated to IT and Finance leads.
IT and Finance leads review draft, feedback incorporated, final microsoft dynamics nav migration assessment report v1.0 signed off. Ready for finance committee. Migration engagement scope and pricing locked.
The six pre-migration failure modes a real assessment prevents — each one seen on real consultant-led projects that skipped the discovery discipline.
Without a support-cliff exposure check, customers find out in February 2026 that their NAV 2016 extended support ends April 2026 and they have no migration plan. Forced sprint, no parallel-run cushion.
Without Object Designer crawl, the 47 custom tables in the 50000-99999 range get discovered piecemeal during migration. Each one adds weeks. Budget overruns 40-60%.
Without add-on signature scan, the Continia OPplus dependency or ChargeLogic vault gets noticed in week 8 of a 14-week migration. Scope renegotiation under time pressure.
Without empirical SQL profiling, the G/L Entry table 17 is assumed to be '10 million rows' and turns out to be 84 million. Extract windows blow out. Timeline slips.
Without per-company database inventory, the consolidating Fusion ledger design is wrong, intercompany pairs don't reconcile, multi-company go-live slips a month-end.
Without statutory obligation register, the SAF-T-PT submission for Portugal or the SdI obligation for Italy gets noticed at the first cutover-period submission deadline. Tax pressure under audit.
A microsoft dynamics nav migration assessment is the structured pre-migration discovery that tells you, before any contract gets signed, exactly what is sitting in your NAV estate and what it will cost in time, money and risk to move it to Oracle Fusion. It inventories the NAV version (5.0 / 2009 / 2013 / 2015 / 2016 / 2017 / 2018), the customisation depth (C/AL vs AL, custom tables in 50000-99999, custom fields on standard tables, custom codeunits and reports), the partner add-ons installed (Anveo, ChargeLogic, Continia, Insight Works and regional specialists), the data volumes per table, the multi-company estate shape, the statutory obligations (GoBD, HMRC MTD, SAF-T, Intrastat, SdI, CFDI, SPED) and the support-cliff exposure (NAV 2016 extended-support cliff April 2026).
A focused assessment runs 2–3 weeks elapsed time. Week 1 is connectivity and source-side inventory: Object Designer crawler runs against the NAV application to enumerate every table, field, key, page, codeunit, report and XMLport; SQL Server profiler estimates row volumes per table; partner add-on signature scan identifies installed third-party modules. Week 2 is target-side analysis: NAV version vs Fusion 26x compatibility check, customisation classification (DFF candidate vs custom table vs retire), partner add-on retire/replace decisions, statutory obligation cross-reference. Week 3 is the sized output: timeline, budget, risk register, signed assessment report with finance and IT sign-off.
Microsoft's NAV 2016 extended support ends April 2026. Past that date, no security patches, no tax-table updates (UK MTD, German GoBD, EU SAF-T per-country), no Microsoft escalation path for production incidents, and increasing audit and insurance pressure to remediate. A microsoft dynamics nav migration assessment commissioned 18 months ahead of the cliff hits a controlled go-live with full parallel-run cushion. One commissioned 6 months ahead has a tight cutover with reduced parallel-run window. One commissioned 3 months ahead is racing the cliff with no margin for slippage. NAV 2018 extended support runs to January 2028, which gives more headroom but follows the same logic — assessment first, then a planned migration window, not a forced sprint.
Syntra ETL's microsoft dynamics nav migration assessment runs the Object Designer crawler against the source NAV application and enumerates every object: tables (standard, modified standard, custom in 50000-99999), fields (standard, modified, custom), keys, pages (modified standard, custom), codeunits (modified standard, custom), reports (RDLC, Word layout, custom), XMLports and queries. Each object is classified by signature against the standard NAV release the customer is on, so modifications and custom objects are unambiguously separated from baseline. C/AL (classic, pre-NAV 2018) and AL (modern, NAV 2018+) are both handled. The output is a complete customisation register that drives migration scope and pricing — not a guess based on customer interviews.
Yes. Partner add-ons leave fingerprints in the NAV application — custom tables in specific number ranges allocated to each vendor, named codeunits and pages, distinctive table layouts. The assessment includes a partner add-on signature scan that recognises the major players (Anveo for eCommerce/EDI/mobile, ChargeLogic for credit-card processing, Continia for OPplus/document-capture/expense, Insight Works for mobile WMS/manufacturing/shipping, plus regional specialists like LS Retail, Tasklet Factory, Mekorma). Each detected add-on triggers a vendor-specific playbook entry in the assessment output: retire / replace with Fusion-native / keep alongside Fusion / data-only migration. The customer gets a clear-eyed view of which add-ons travel and which don't.
A signed PDF report with: NAV version + support-cliff exposure summary; per-company database inventory with row volumes for the top 20 tables (17, 32, 36/37, 38/39, 18, 23, 27, 5050, 270 + the largest custom tables); C/AL/AL customisation register classified by migration disposition; partner add-on register with per-vendor playbook decisions; statutory obligation register (GoBD, HMRC MTD, SAF-T per-country, Intrastat, SdI, CFDI, SPED) with retention requirements; report inventory (RDLC, Word layout, Jet Reports) classified by business value; sized timeline (Weeks 1–22 typical full-scope); sized budget; risk register; recommended next steps; sign-off page for IT and Finance leads.
No. The assessment runs against read-only access to either the production NAV SQL Server backend, a recent backup restored to a sandbox SQL Server, or a SQL Server replica. Most customers prefer the backup option — it avoids any read load on production NAV, runs against a known-stable snapshot, and gives the assessment team unconstrained query time. The Object Designer crawler runs against the NAV application metadata which is also extractable from a backup. No NAV admin downtime is required, no Object Designer modifications are made, and NAV users continue working without slowdown for the entire assessment window.
Pricing emerges from the assessment output: NAV version (older versions have less mature web-services and OData coverage, requiring more SQL-direct extraction), customisation depth (custom tables and modified standard objects drive crosswalk work), partner add-on count (each retired/replaced add-on adds days), data volumes (G/L Entry 17 and Item Ledger Entry 32 in high-volume sites are the long pole), multi-company count (each additional NAV company is incremental but not zero), statutory obligation count (each country jurisdiction adds compliance archive work). A typical full-scope microsoft dynamics nav migration assessment converts to a 14–22 week timeline and a fixed-fee budget that customers can take to finance committee with confidence — versus a consultant-led time-and-materials engagement that drifts indefinitely.
Book a 30-minute discovery call. We'll scope the assessment, agree access, and start the 2–3 week clock — so your sized timeline and budget land on the finance committee desk before the next steering meeting.