Purpose-built ETL platform for microsoft dynamics nav to oracle fusion migration — Financials, Sales, Purchasing, Inventory and Manufacturing. SQL Server, NAV Web Services and OData extractors, C/AL and AL inventory, GoBD/HMRC/SAF-T retention playbooks. 40–60% faster than consultant-led programmes.
Most NAV to Fusion projects don't slip in the SQL extract. They slip in C/AL inventory, partner add-on reverse-engineering, RDLC/Jet report rebuild and DACH/UK compliance archive design.
Microsoft Dynamics NAV — Navision before the 2002 Microsoft acquisition, Microsoft Navision in the early Microsoft years, and Dynamics NAV from 2005 onward — has been the dominant mid-market ERP across DACH, the Nordics, UK and US SMB for two decades. Customers carry a deep tail of customisation: hundreds of C/AL modifications layered into standard objects, custom tables in the 50000-99999 partner range, partner-built add-ons from Anveo, ChargeLogic, Continia, Insight Works and a long list of regional specialists. Consultant-led migrations spend the first four months just cataloguing what exists.
Syntra ETL inverts the sequence. The Object Designer crawler enumerates every NAV object — tables, fields, keys, pages, codeunits, reports, XMLports — in days, not months. The SQL Server extractor pulls table 17 (G/L Entry), table 32 (Item Ledger Entry), table 18 (Customer), table 23 (Vendor), table 27 (Item) plus every custom table in parallel against a read replica. The microsoft dynamics nav to oracle fusion migration conversation that traditionally consumes a quarter happens in week two with the complete customisation inventory on the table.
Whether you are migrating a single-tenant NAV 2016 sitting on SQL Server 2014 in a German factory, a multi-region NAV 2018 estate across UK, Ireland and France with HMRC MTD and EU SAF-T obligations, or a Navision Attain database from 2003 still running payroll for a Nordic subsidiary — the same engine handles the work, with the same reconciliation rigor and the same audit trail evidence pack.
And how the Syntra ETL platform addresses each one — before they consume your timeline.
NAV sites accumulate C/AL modifications over 10–20 years — modified standard objects, custom tables, custom codeunits. Object Designer crawler enumerates everything; classification engine routes each to Fusion DFF/EFF, OTBI, REST integration or retirement.
Reports run on RDLC, Word layouts or the ubiquitous Jet Reports Excel add-on. Inventory, classification by business value, Fusion OTBI/BI Publisher/Smart View rebuild plan. 40–60% retired during cleanup.
German GoBD requires 10-year retention of digital records with audit-grade immutability. Syntra ETL preserves the full posting chain on the archive side with GoBD-compliant hash signatures and timestamped read-access logs.
Anveo, ChargeLogic, Continia, Insight Works, regional specialists — each adds its own custom tables and codeunits. Vendor-specific playbooks recognise add-on signatures and handle data extraction without vendor cooperation.
NAV 2016 extended support ends April 2026; NAV 2018 ends January 2028. Past the cliff: no patches, no tax updates, no escalation. Syntra ETL planning playbook ensures the cutover lands 3+ months before the cliff with parallel-run cushion.
Norway, Poland, Portugal, France, Lithuania, Romania all mandate SAF-T digital tax submissions. NAV's localisation files (NO/PL/PT/FR) carry submission history that has to migrate. Per-country SAF-T preservation built in.
A repeatable, governed workflow built for NAV's particular complexity. Typical full-scope timeline: 14–22 weeks.
Object Designer crawler enumerates every NAV table, field, page, codeunit, report and XMLport. SQL Server profiler estimates row volumes per table. Partner add-on signature scan identifies Anveo/ChargeLogic/Continia/etc. Output: complete customisation inventory, data volume estimate, sized assessment with risk register.
Customer/Vendor/Item master crosswalks, dimension-to-Fusion-COA mapping, custom-field to DFF routing, C/AL codeunit replacement plan, partner add-on retire/replace decisions. GoBD/HMRC/SAF-T compliance archive design signed off by tax and audit leads.
NAV SQL Server, Web Services and OData extractors pull all configured tables and entities. Output staged as Parquet plus original RDLC/Jet artifacts, partitioned by company (NAV multi-tenancy) and fiscal year with hash-signed manifests.
Crosswalks applied, custom fields collapsed to DFFs, dimensions remapped to COA, FBDI payloads generated for Fusion Financials/SCM, validated against current Fusion 26x release schemas. Errors surfaced locally with row-level diagnostics.
FBDI ZIPs submitted to Fusion ESS, monitored to completion, reconciled at row, sum and hash level. In parallel, critical OTBI and BI Publisher reports rebuilt and validated against RDLC/Jet equivalents. Compliance archive (GoBD/HMRC/SAF-T) populated and signed.
1–2 month-end cycles in parallel (NAV + Fusion), deltas captured and replayed, reconciled to the cent, sign-off pack issued. NAV moves to read-only archive mode; new transactions flow to Fusion only. Decommission scheduled when retention window allows.
No more bespoke SQL queries against table 17 or hand-built SOAP clients. Just configure scope, run, reconcile.
Read-replica SQL Server extraction with parallel partition scans on the high-volume tables (G/L Entry 17, Item Ledger Entry 32, Sales/Purchase Lines). Throttled to respect NAV server load; off-peak scheduling for the biggest pulls.
SOAP-based extraction for NAV 2009 R2 and later, scoped service-account credentials, every published Page and Codeunit web service callable with proper pagination and error handling.
OData v3/v4 feeds for NAV 2013 and later, ideal for incremental delta pulls keyed on Modified Date/Time. Supports the modified-since watermark pattern for steady-state delta loading.
Enumerates every table, field, key, page, codeunit, report, XMLport and query in the NAV application. Output classified by business purpose for migration crosswalk.
NAV's per-company database segmentation handled natively — Company1, Company2, Company3 all extracted in parallel with company-id preserved in every output partition.
Country-specific localisation tables (DE, UK, NO, PL, PT, FR, IT) extracted with format preservation for downstream GoBD, HMRC MTD, SAF-T submission history.
A typical microsoft dynamics nav to oracle fusion migration covering Financials, Sales, Purchasing and Inventory — with 7–10 years of history and customer/vendor/item masters carrying years of C/AL customization — runs 14–22 weeks with Syntra ETL versus 12–18 months on a consultant-led programme. Single-module work (NAV General Ledger → Fusion GL only) completes in 8–11 weeks. The acceleration comes from pre-built NAV extractors that already speak the SQL Server backend, NAV Web Services (SOAP) and OData feeds, plus governed crosswalks for the classic NAV table set (Customer 18, Vendor 23, Item 27, G/L Entry 17, Sales/Purchase Header/Line). Customers in DACH, Nordics and UK carrying GoBD or HMRC retention obligations routinely add 2–3 weeks for the cross-region compliance archive.
Microsoft is pushing Dynamics 365 Business Central as the cloud successor to NAV, but for organisations already running Oracle databases, EBS, or Fusion in adjacent business units the BC path means relearning a Microsoft cloud stack that doesn't match the rest of the estate. A microsoft dynamics nav to oracle fusion migration consolidates onto a single Oracle ecosystem, eliminates Microsoft SQL Server licensing for the ERP footprint, retires the C/AL/AL customisation backlog and crosses the NAV support cliff cleanly — NAV 2016 mainstream support ended April 2021 and extended support ends April 2026, NAV 2018 extended ends January 2028. Fusion delivers quarterly innovation, native multi-pillar (Finance, SCM, HCM, EPM) integration and a modern Redwood UX without partner-built add-on dependency.
All actively-deployed versions: NAV 5.0 (classic client), NAV 2009 (RoleTailored client), NAV 2013, 2015, 2016, 2017 and NAV 2018 — plus the original Navision databases still in production at long-tenured customers. Extraction works against the SQL Server backend for any version that exposes its database (every NAV release since 2005), via NAV Web Services (SOAP) for versions 2009 R2 and later, and via OData for NAV 2013 and later. Customisations written in C/AL (classic) or AL (modern NAV 2018) are inventoried automatically. We also handle Navision Attain and Navision Financials databases pre-acquisition by Microsoft in 2002 — useful when the migration has to absorb genuinely legacy data alongside more recent NAV.
C/AL is the original NAV programming language; AL is its modern successor introduced for NAV 2018 and Business Central. Both produce customisations — custom tables, custom fields, custom pages, custom codeunits, custom reports — that don't translate 1:1 to Fusion. Syntra ETL's Object Designer crawler enumerates every object in the NAV application: custom tables, fields, keys, pages, codeunits, reports, XMLports and queries. Each is classified by business purpose, scored for migration materiality and mapped to its Fusion equivalent: custom fields collapse to Fusion DFFs/EFFs, custom tables route to Fusion extension objects or to the long-term NAV archive, custom reports rebuild as OTBI/BI Publisher, custom codeunits map to Fusion REST integrations or process automation. Partner add-ons (Anveo, ChargeLogic, Continia, Insight Works) are recognised by signature and handled with vendor-specific playbooks.
Yes. NAV deployments tend to grow custom tables (typically in the 50000-99999 range reserved for customers and partners) over years of in-house development. Syntra ETL's NAV converter walks every custom table, samples row volume and update frequency, and proposes a target: required custom tables migrate as Fusion descriptive flexfield extensions on the parent object (Customer, Vendor, Item), high-volume analytical custom tables route to a Fusion-adjacent data warehouse and OTBI lookback, and obsolete custom tables (zero updates in 36 months) get retired. Custom fields on standard NAV tables (Customer 18, Vendor 23, Item 27) similarly collapse onto Fusion DFFs with full retention of historical values. Every decision is logged in the migration evidence pack.
NAV reporting evolved across versions: classic NAV used Report Designer with section-based layouts, then RDLC (SQL Server Reporting Services-style) reports from NAV 2009, then Word layout reports for letter-style output, plus the ubiquitous Jet Reports Excel add-on installed at the majority of NAV sites. None of these carry over to Fusion natively. Syntra ETL's reporting assessment inventories every active RDLC, Word layout and Jet Report file, classifies by business value (sales-by-customer, item-turnover, AR aging, GoBD GDPdU export, statutory tax reports) and proposes Fusion replacements: OTBI dashboards for analytical reports, BI Publisher for pixel-perfect statutory output (HMRC, GoBD, SAF-T), Smart View for Excel-tethered analysis replacing Jet. 40–60% of legacy reports are duplicates or low-value and get retired.
No. The Syntra ETL extractor connects to NAV through three read-only channels — SQL Server replica or read-replica account, NAV Web Services with scoped service-account credentials, and OData with read scope — and never writes back to NAV. SQL Server extraction is throttled to respect NAV server load, and the largest historical extracts (10 years of G/L Entry table 17, Item Ledger Entry table 32) are scheduled for off-peak windows or run against a SQL Server replica. No NAV admin downtime is required, no Object Designer modifications are made, and NAV users continue working without slowdown. Cutover itself is a defined moment, typically a weekend close-out — NAV switched to read-only, new transactions filed in Fusion — with parallel running for 1–2 month-end cycles before NAV decommission.
Microsoft's NAV support timeline creates real cliffs. NAV 2016 mainstream support ended April 2021 and extended support ends April 2026 — that's the security-patch and tax-update cutoff for any NAV 2016 site. NAV 2018 extended support runs to January 2028. Older versions (5.0, 2009, 2013, 2015) are already entirely out of support. Past extended support there are no security patches, no tax-table updates for jurisdictions like UK MTD, German GoBD or EU SAF-T, no Microsoft escalation path for production incidents, and increasing audit and insurance pressure to remediate. A microsoft dynamics nav to oracle fusion migration planned 12–18 months ahead of the cliff hits a controlled go-live; one planned 3 months ahead hits a forced cutover with no parallel-run cushion.
Book a 30-minute discovery call. We'll walk through your NAV version, customisation depth, partner add-ons, multi-company estate and compliance obligations — and give you a concrete timeline and budget before the call ends.