Legacy ERP to Cloud Is the Most Common Enterprise Migration#
In 2026, the dominant ANZ enterprise migration is moving from legacy on-premise ERPs to cloud platforms. Whether motivated by end-of-life pressure, IT cost reduction, modernisation strategy, or M&A consolidation, the migration represents a multi-year program for most affected businesses.
This article covers the strategic decisions, deployment options, and realistic ANZ playbook.
Why Businesses Migrate#
Common drivers in 2026:
- End-of-life pressure. Older platforms (SAP ECC, JD Edwards World, AccuFlow, older Sage 300 versions) are deprecated or approaching end of support.
- IT cost reduction. Eliminating server infrastructure, database licensing, and ongoing IT operations typically saves NZ$50,000-300,000/year.
- Skill availability. Cloud platforms have larger skill pools than legacy systems; expertise becomes harder to recruit for legacy.
- User experience. Modern UX expectations vs 1990s-era ERPs.
- Compliance modernisation. Privacy Act 2020 (NZ), Australian Privacy Principles, sector-specific compliance driving modernisation.
- M&A integration. Acquired businesses often migrate to acquiring company's ERP.
- Regulatory requirements. Government, healthcare, financial services driving cloud adoption.
When Migration Isn't Justified#
Even for legacy ERPs, migration sometimes isn't the right answer:
- Customisation depth makes migration cost prohibitive (NZ$10M+ migrations)
- Business is being wound down or restructured
- Industry-specific compliance requires capabilities only legacy ERP has
- Total cost of staying (licences + IT + maintenance) is less than total migration cost over 5 years
Some businesses operate legacy ERPs indefinitely with minimal modernisation. The business case must support migration.
Strategic Decisions#
Lift-and-Shift vs Re-Implement#
Lift-and-shift: - Move existing ERP to cloud infrastructure (Azure, AWS) - Same ERP, new deployment - Faster, cheaper, lower risk - Doesn't address legacy architecture issues - Best for: businesses where legacy ERP is still operationally sound; primary driver is IT cost reduction
Re-implementation: - Move to new cloud-native ERP (NetSuite, MYOB Acumatica, Dynamics 365, S/4HANA Cloud) - Address legacy architecture and customisation debt - Longer, more expensive, higher risk - Best for: businesses where legacy ERP no longer fits operational needs; primary driver is modernisation
For most ANZ businesses outgrowing legacy ERPs, re-implementation is the right answer because customisations are typically the reason migration was needed.
Cloud Deployment Options#
Public Cloud (SaaS). - SAP S/4HANA Public Cloud (RISE) - NetSuite (cloud-only) - MYOB Acumatica - Microsoft Dynamics 365 (Public Cloud option)
Private Cloud. - SAP S/4HANA Private Cloud - Oracle Cloud Infrastructure - Microsoft Dynamics 365 Private Cloud option - Azure or AWS-hosted vendor-managed ERPs
Hybrid. - Some businesses run cloud + on-premise concurrently - Useful for businesses with sensitive data residency requirements - Often a transition phase rather than permanent state
Source Platform-Specific Migrations#
SAP ECC → S/4HANA Cloud#
Migration approaches: - Greenfield (new implementation, data migration) - Brownfield (system conversion, in-place upgrade) - Bluefield (hybrid, partial new and partial conversion)
Realistic ANZ scope: - Timeline: 18-30 months - Cost: NZ$2,000,000–5,000,000 (mid-market) - Key challenge: customisation modernisation (Clean Core) - Most ANZ ECC customers will migrate by 2030 (mainstream support ends 2030)
Oracle JD Edwards → Oracle Cloud or NetSuite#
Migration approaches: - JD Edwards World → Oracle Cloud (Fusion ERP) - JD Edwards World → NetSuite (different Oracle product) - JD Edwards EnterpriseOne → JDE 9.2 with cloud hosting (alternative)
Realistic ANZ scope: - Timeline: 15-24 months - Cost: NZ$1,500,000–3,000,000
Sage 300 → MYOB Acumatica or NetSuite#
Migration approaches: - Sage 300 (Accpac heritage) → MYOB Acumatica (most common ANZ path) - Sage 300 → NetSuite (for multi-entity expansion) - Sage 300 → Sage Business Cloud X3 (staying with Sage)
Realistic ANZ scope: - Timeline: 9-18 months - Cost: NZ$400,000–1,500,000
Custom Legacy ERP → Modern Cloud#
Migration approaches: - Replace with cloud ERP (NetSuite, Acumatica, etc.) - Build custom cloud replacement (rarely justified)
Realistic ANZ scope: - Timeline: 24-36+ months - Cost: NZ$2,000,000–8,000,000+ - Highest risk due to undocumented business logic in legacy custom code
The Migration Playbook#
Phase 1: Strategic Discovery (12-24 weeks)#
Activities: - Document current legacy ERP usage - Identify business processes vs system processes - Document customisations (often poorly understood) - Build business case with ROI modelling - Select target deployment option - Select target ERP and partner
Critical step: Legacy customisation discovery. Often the biggest unknown is how much custom code exists and what it does.
Phase 2: Design and Configuration (24-48 weeks)#
Activities: - Implement target ERP standard processes - Decide retain/rebuild/eliminate for each legacy customisation - Configure modules for required business functions - Build extensions where retain decisions were made - Configure integrations to other systems
Customisation strategy: - Adopt standard processes where business value justifies process change - Customise via modern extensibility frameworks (not legacy-style modifications) - Eliminate customisations that no longer serve a purpose
Phase 3: Data Migration and Testing (16-32 weeks)#
Activities: - Build data migration scripts (often complex for legacy) - Migrate test data with multiple iterations - Validate financial reconciliation - User acceptance testing - Performance testing - Disaster recovery testing
Legacy ERP challenges: - Custom data structures from years of evolution - Undocumented relationships between tables - Data quality issues accumulated over time - Need for data cleansing during migration
Phase 4: Parallel Run (12-24 weeks)#
Activities: - Legacy ERP remains production - Mirror critical transactions in target ERP - Reconcile financials between systems - Train users on target ERP - Identify and fix discrepancies
Long parallel run is common for legacy migrations because: - Financial close processes need validation across multiple cycles - Business users need extended training - Edge cases surface over months, not weeks
Phase 5: Cutover and Hypercare (12-24 weeks)#
Activities: - Phased cutover (often by entity, region, or function) - Legacy ERP becomes read-only - Hypercare with intense partner and internal team support - Gradual transition to ongoing support model
Phased cutover: Most large legacy migrations cut over in phases rather than big-bang. Risk reduction outweighs the additional complexity.
Integration Rebuild#
Legacy ERP integrations rarely port. Each requires rebuild:
| Integration type | Cloud ERP approach |
|---|---|
| Banking | Modern banking integrations (often more efficient than legacy) |
| Payroll | Modern payroll platforms with cloud ERP integration |
| Manufacturing execution (MES) | Modern MES platforms or ERP-native modules |
| EDI | Modern EDI platforms or ERP-native EDI |
| BI/Reporting | Modern analytics (Power BI, Tableau, SAP Analytics Cloud) |
| Custom integrations | Often rebuilt as API-based microservices |
Integration rebuild can be 20-40% of total migration cost.
Common Failure Patterns#
- Underestimating customisation depth. Legacy systems often have 10-20+ years of customisation; discovering and rebuilding is the biggest cost variance source.
- Insufficient parallel running. Cutover before validation creates production issues that cost more than the parallel weeks would have.
- Inadequate change management. Users with deep legacy ERP expertise need extensive training and time to adapt.
- Wrong target platform selection. Choosing target ERP before fully understanding requirements.
- Big-bang cutover for complex migrations. Phased cutover is almost always lower-risk.
- Underestimating internal staff time. Internal staff often spend 50% of their time on migration during peak phases.
Cost-Saving Strategies#
- Multi-partner RFP. 20-30% implementation cost reduction typical.
- Phased migration. Lower risk and allows learning between phases.
- Aggressive customisation elimination. Each retained customisation adds cost; eliminate where business value doesn't justify rebuild.
- Standard process adoption. Adopting target ERP's standard processes reduces customisation and ongoing maintenance.
- Don't migrate unused data. Historical data archival saves 30-50% of data migration cost.
What to Ask Migration Partners#
- Show me 3 ANZ migrations from my source platform with references.
- What's the partner's customisation evaluation methodology?
- Demo the data migration tooling and approach.
- What's the realistic timeline for my specific configuration?
- What's the post-migration support model?
See Also#
For broader context, see Why ERP Implementations Fail, Data Migration Disasters Case Studies, Migrating from Sage to NetSuite, SAP Implementation Complete Guide, and ERP System Architecture Fundamentals.