Greentree ERP migration — to Business Central, NetSuite, MYOB or Xero

A right-sized Greentree → Business Central or Xero migration (single entity, standard modules) typically runs 12–20 weeks. A Greentree → Business Central or NetSuite migration with field-ops, mining or manufacturing modules and several integrations runs 5–10 months. Multi-entity migrations with heavy customisations can run 9–18 months. Cutover always lands on a financial-year or quarter boundary so reporting stays clean.

Depends on size, sector and ecosystem. Business Central is right when you want to stay in the Microsoft ecosystem and use field-service, manufacturing or inventory modules natively. NetSuite is the consolidation play when the parent group is already on NetSuite or you want full ERP independence. MYOB or Xero suit businesses where Greentree was over-scoped and a modern accounting platform plus a connected app covers actual usage. The scoping call covers all options honestly — we do not get paid more to recommend any one.

MYOB acquired Greentree International in 2016 and has since rebranded the product as MYOB Greentree. The product has seen limited investment compared to MYOB's cloud platforms, and the direction of travel for MYOB is clearly toward MYOB Acumatica as the ERP-grade offering. For AU/NZ businesses on Greentree, the question is not if they will need to migrate, but when — and doing it on your terms is better than being forced by a deadline.

In principle, all of it. We extract the general ledger, chart of accounts, AR/AP transactions and open items, customer and supplier master records, inventory items, bills of materials, sales orders, purchase orders, job costing and project history, fixed assets, and field-ops job records. In practice we agree which years need to be queryable live in the new system (typically 2–7 years) and archive older history as exports. The Australian Tax Office requires 5 years of records.

Yes. Greentree field-service and field-operations modules (work orders, asset management, scheduling, equipment maintenance, shift-costing) are mapped to Business Central Field Service or NetSuite Field Service Management. Mining-sector workflows including equipment register and production reporting are re-implemented in the target system's native features or as configured extensions. Job history and asset register are migrated, not dropped.

Distribution and wholesale workloads in Greentree — multi-warehouse inventory, landed cost, purchase order receipting, sales order fulfilment — map cleanly to Business Central or NetSuite. Both platforms have strong native distribution functionality. We validate item masters, warehouse structure, pricing rules and open order history during the parallel-run phase before cutover.

Yes — migration scripts, reconciliation reports, target-system configurations, custom extensions, deployment scripts, all yours in your GitHub or Azure DevOps from day one. Greentree 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.

Fixed-price means a firm number you approve before any data is touched — not a time-and-materials estimate that blows out. It is based on a 15-minute scoping call and a short discovery session where we confirm Greentree version, module list, customisation depth and data volume. Scope is documented and signed off. Change control applies only if the scope genuinely changes, not because the project took longer than our estimate.