Move off MYOB Exo without losing your history, your customisations, or a week of trading

MYOB has publicly repositioned Exo as a legacy product and is directing development investment toward MYOB Acumatica (formerly MYOB Advanced). Exo still works, but it receives no new feature development, the talent pool of people who know Exo SQL is shrinking, and cloud integrations that modern businesses expect are not available. Most Australian Exo customers are evaluating their migration window now rather than waiting until support is formally discontinued.

It depends on your size, vertical, and existing Microsoft or cloud footprint. Business Central suits mid-market Australian businesses already on Microsoft 365 or needing strong manufacturing and field-ops modules. NetSuite suits businesses with multi-subsidiary, multi-currency or complex revenue recognition needs. Xero is the right simplification move for smaller Exo customers whose complexity has reduced. MYOB Acumatica makes sense when the team knows MYOB and the business needs a genuine mid-market cloud ERP without a vendor change. The scoping call covers all four honestly — we are not a reseller of any of them.

In principle, all of it — GL transactions, AR/AP detail, customer and supplier records, inventory, Job Costing WIP, payroll history, custom fields. In practice we ask which years need to be live and queryable in the new system (typically the last 2–7 years) and archive older data as exports. The ATO requires 5 years of records; we always migrate enough to satisfy that requirement and the next audit.

Not automatically — but they are rebuilt in the target platform as part of the migration scope. Clarity reports become Power BI dashboards or Business Central report layouts. Business Analytics views are rebuilt as NetSuite Saved Searches or Xero analytic templates. Job Costing logic is reconstructed in the target platform's project module. Every customisation is catalogued in the Exo audit so nothing is missed.

Yes, and this is one of the most carefully managed parts of any Exo migration. We preserve year-to-date payroll figures, carry the STP reporting trail across cleanly, and switch the STP submission to the new system on a clean pay-period boundary. No missed pay runs, no broken ATO reporting trail, no year-end surprises.

Mining and field-services businesses are among the most common MYOB Exo customers, and they typically have the most complex migrations — Job Costing across multiple projects, site-based inventory, subcontractor management, field-ops mobile workflows. Business Central and NetSuite both have strong field-ops and project modules; the scoping call determines which fits your specific workflow. Keywords like “MYOB Exo to Business Central mining” and “MYOB Exo to NetSuite field operations” land here because we have done exactly this kind of migration.

Everything talking to the Exo SQL Server database — EDI feeds, payroll bureaus, custom COM or API calls, field-service tools, BI connectors — is inventoried in the Exo audit and scoped for re-plumbing to the target platform. SQL reporting queries are rewritten for the new data model. We do not leave dark integrations undiscovered until after go-live.

Yes. Migration scripts, reconciliation reports, data mapping documents, and integration code all live in your GitHub repository from day one — not ours. Exo stays installed read-only for one financial year as an audit safety net. After that you keep exported archives indefinitely. There is no ongoing licence or fee to us after the project closes.