Dynamics NAV migration — to Business Central, D365, NetSuite or Xero

Fixed-price after a 15-minute scoping call and a short discovery session. A focused NAV to Business Central migration (single entity, vanilla modules, light customisations) runs in the mid-tens-of-thousands over 10–16 weeks. A multi-entity NAV to BC or NetSuite migration with C/AL customisations and ISV add-ons is a larger engagement. Enterprise NAV with heavy customisations, 5+ legal entities and complex industry modules sits higher again. You receive a fixed price before any data is touched — no per-hour billing that climbs as the project drags.

A right-sized single-entity NAV to Business Central with vanilla modules runs 10–16 weeks. A standard multi-entity NAV to BC with C/AL customisations and 2–3 ISV add-ons runs 16–28 weeks. An enterprise NAV with industry vertical modules (manufacturing, mining, construction) and many integrations runs 6–12 months. Cutover always lands on a financial-year or quarter boundary so reporting stays clean.

For most NAV customers, yes. Business Central is the official Microsoft successor — structurally the same product, cloud-native, and the platform Microsoft is actively investing in. D365 Finance & Operations is right only when you genuinely need the heavier tier (advanced manufacturing at scale, complex multi-subsidiary). NetSuite suits consolidation plays or businesses leaving the Microsoft ecosystem. Xero/MYOB suit businesses where NAV was over-scoped. The scoping call covers all options honestly.

Audited carefully. We document every customisation — often uncovering ones the current team has forgotten — and split into three buckets: (1) re-implement as a proper BC extension or D365 extension, (2) replace with native target-system functionality, (3) retire because the underlying business need has changed. Nothing is silently dropped. ISV add-ons are mapped to target-system equivalents or replaced consciously.

Chart of accounts, general ledger transactions, AR/AP open items and history, customer and supplier records, inventory and item records, sales orders, purchase orders, invoices, warehouse data, fixed assets and payroll history. In practice we ask which years need to be queryable live vs archived — the Australian Tax Office requires 5 years of records, so we always migrate enough to satisfy that and the next audit.

Yes. NAV manufacturing modules map to Business Central Manufacturing or D365 F&O Advanced Manufacturing for heavier needs. Mining and field-operations modules (common in WA and QLD resource sector NAV installations) carry to D365 F&O or D365 Field Service. Construction project-costing re-implemented in BC Jobs module plus extensions. Distribution and wholesale warehouse modules handled — WMS carried to the target system or replaced with a specialist connected app.

Yes and no. Older Navision versions (NAV 2009, NAV 2013, NAV 2015) need more custom extraction work because the Microsoft migration tooling is oriented toward NAV 2017+ and AL extensions. We have the extraction patterns for older NAV versions. The core migration approach is the same — audit, extract, reconcile, build in target, parallel-run, cutover — but the extraction layer takes more effort on older versions.

Yes — migration scripts, reconciliation reports, target-system configurations, custom extensions and deployment scripts are all yours in your GitHub or Azure DevOps from day one. NAV stays installed read-only for one financial year as audit safety — the auditor can still pull source data when needed. After that, exported archives are kept indefinitely. Target system hosting is yours (Business Central is your Microsoft tenant; NetSuite is your NetSuite account).