Epicor migration — to Business Central, NetSuite, MYOB or Xero

A right-sized Epicor → Business Central or Xero migration (single entity, vanilla modules) typically runs 12–20 weeks. A standard Epicor → 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 Epicor 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.

Audited before migration begins. We document every customisation (often surprising the current team) and sort into three buckets — re-implement in the target system as a native feature or extension, replace with something the target already does, or drop because the underlying business need has changed. Nothing disappears without a conscious decision.

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). The Australian Tax Office requires 5 years of records. Multi-entity Epicor installations have intercompany history that we preserve carefully — those are often the most time-consuming part of the project.

Yes. Epicor field-service and field-operations modules (work orders, asset management, scheduling, equipment maintenance) are mapped to Business Central Field Service or NetSuite Field Service Management. Mining-sector workflows including shift-costing, 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.

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

Yes. “Epicor to Business Central field operations” is a common migration pattern we deliver. Business Central 2024 includes a mature Field Service module (formerly Dynamics 365 Field Service integrated with BC) that covers work orders, asset management, scheduling, mobile field-technician apps and service contracts. Epicor field-service configuration, job history and asset register all migrate.

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 Epicor 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.