Dynamics AX migration — to D365 F&O, Business Central, NetSuite or Xero

Fixed-price after a 15-minute scoping call and a short discovery session. A right-sized AX → Dynamics 365 BC migration (small mid-market, vanilla modules) takes 12–20 weeks. A standard AX → Dynamics 365 F&O migration with vertical industry modules (manufacturing, mining, field-ops) and several custom integrations takes 6–14 months. Enterprise-scale multi-entity migrations sit higher. You know the price before any data is touched.

Small right-size (AX → BC, vanilla modules, single entity): 12–20 weeks. Standard AX → D365 F&O with industry modules and multi-entity: 6–10 months. Enterprise AX 2012 R3 → D365 F&O / NetSuite with heavy customisations, ISVs and 8+ legal entities: 9–18 months. Cutover always lands on a financial-year or quarter boundary so reporting stays clean.

Depends on size, sector and ecosystem. D365 F&O is the natural Microsoft path — best when you're heavy on Microsoft (Power BI, Azure, Entra ID) and use AX's heavier modules in production. Dynamics 365 Business Central is right when AX was over-scoped and you're actually using 60–80% finance + light inventory. NetSuite is the consolidation play when the parent group is on NetSuite or you want out of the Microsoft ecosystem. The scoping call covers all three honestly — we don't get paid more to recommend any one.

Audited carefully. We document every customisation (often surprising the current team) and split into three buckets — (1) re-implement as a proper D365 extension or NetSuite SuiteScript, (2) replace with native functionality the new system covers, (3) drop because the underlying business need has changed. ISV add-ons (Junction Solutions, To-Increase, etc.) are mapped to D365 equivalents where they exist; otherwise replaced or custom-built.

In principle, all of it. In practice we ask which years actually need to be queryable in the new system (typically last 2–7 years live, older years archived as exports). Australian Tax Office requires 5 years of records. Multi-entity AX installations have intercompany history that we preserve carefully — those are often the trickiest part of the project.

Yes. AX 2012 R3 + the AX for Mining ISV, AX Manufacturing module, AX Project Management & Accounting, AX Warehouse Management, AX Production Control. These map cleanly to D365 F&O's native modules (industry pre-configured for mining, manufacturing) and partially to NetSuite Advanced Manufacturing. Field-operations modules (where keywords like "dynamics ax field operations migration" land) are common — D365 F&O Field Service is the typical successor.

Yes. AX 2009 is older, no longer supported, and the migration tools Microsoft provides are oriented toward AX 2012 R3 → D365. AX 2009 migrations need more custom extraction work; we have the patterns. AX 2012 R3 has Microsoft-supplied data migration tools (Lifecycle Services data packages) that we leverage where they apply, augmenting with custom extraction for anything they don't cover.

Yes — migration scripts, reconciliation reports, target-system configurations, custom extensions, deployment scripts, all yours in your GitHub or Azure DevOps from day one. AX 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 (D365 F&O is your Microsoft tenant; NetSuite is your NetSuite account).