Moving a fashion ERP to the cloud: lessons from 2024 to 2026 migrations
Maintenance deadlines for older ERP platforms are pushing fashion companies to move. What drives the timing, which approaches are used and where projects run into trouble.
KEY TAKEAWAYS Summary by the editors
- SAP's mainstream maintenance for Business Suite 7, including ECC, runs until the end of 2027, with optional extended maintenance to 2030 at a premium.
- Microsoft ended extended support for Dynamics AX 2012 R3 on 11 January 2023, so remaining AX users are already running unsupported software.
- A PwC case study published in October 2025 describes a clothing brand with around 1 billion euros in revenue moving from ECC to S/4HANA using a selective greenfield approach.
- The hardest parts of a fashion ERP migration are usually the size and colour data model, wholesale and retail integrations, and cut-over timing around the season calendar.
- A migration is the cheapest moment to clean master data and retire custom code; projects that lift and shift both tend to carry old problems into the new system.
Fashion companies are moving their ERP to the cloud mainly because maintenance deadlines for older platforms are approaching, and because modern planning, AI and integration features are increasingly released only for cloud editions. The projects that go well treat the migration as a chance to simplify processes and clean data; the ones that struggle try to reproduce every legacy customisation. The lessons below draw on vendor timelines and published case studies from 2024 to 2026.
Why are fashion companies migrating their ERP now?
The most concrete driver is vendor support. SAP has committed to maintaining S/4HANA until the end of 2040, while mainstream maintenance for SAP Business Suite 7 core applications, which includes ECC, ends at the end of 2027, with optional extended maintenance from 2028 to 2030 at a premium. Many fashion companies run SAP's Apparel and Footwear Solution (AFS) on that platform; Rizing, an SAP partner, writes that support for SAP AFS ends in 2027. On the Microsoft side, both mainstream and extended support for Dynamics AX 2012 R3 have ended, the latter on 11 January 2023, and Microsoft recommends migration to Dynamics 365.
Deadlines alone rarely justify the cost. The business reasons usually given are a single platform for wholesale, retail and e-commerce, better inventory visibility, and access to newer planning and AI functions.
What does a fashion ERP migration look like in practice?
A PwC case study published in October 2025 describes a clothing brand, not named, that moved from SAP ECC to S/4HANA after 19 years on the old system. The scope covered 11 countries and around 1 billion euros in revenue, more than 200 stores, over 300 wholesale partners, several online marketplaces and three warehouses. The company chose a selective greenfield approach, combining standard S/4HANA functions with retained custom processes. According to PwC, the project streamlined more than 700 business processes, introduced algorithm-based store replenishment and RFID-based stock-taking in stores, and unified retail, wholesale and e-commerce on the same applications and processes.
Two features of this example are typical. The scope included many external partners, which makes integrations a central workstream, and the migration was used to add new capabilities rather than only to replace the old system.
Which migration approach fits a fashion company?
| Approach | What it means | Suits | Main risk |
|---|---|---|---|
| Brownfield (system conversion) | Convert existing system and data, keep processes | Stable processes, tight timeline | Carries old customisations and data issues forward |
| Greenfield | New implementation on standard processes, migrate selected data | Companies willing to redesign processes | Longer change effort, more business involvement |
| Selective (hybrid) | Mix of new standard and retained custom processes | Large groups with some unique processes | Complex scoping and testing |
| Platform switch | Move to a different vendor's cloud ERP | Smaller firms on unsupported systems | Full re-implementation and integration rebuild |
Cloud editions, particularly public cloud, limit how much core code can be modified. For fashion companies with heavy customisations in allocation, size runs or pre-order handling, that constraint forces decisions: adopt the standard, move the logic to a separate application, or choose a private cloud edition with more freedom and more maintenance.
The choice also shapes the integration work. A conversion keeps most interfaces in place but may require re-testing every EDI mapping and API connection; a greenfield or platform switch usually means rebuilding them. In both cases, a separate integration layer between ERP and partners reduces the risk, because retailer-facing formats can stay stable while the system behind them changes.
Where do fashion ERP migrations run into trouble?
- The product data model. Style, colour and size structures, size scales and seasonal attributes must map cleanly to the new system. Errors here affect every order line.
- Integrations. EDI links to department stores, marketplace APIs, warehouse and 3PL systems, PIM, B2B ordering and point of sale all need to be rebuilt or re-tested.
- Cut-over timing. Fashion has few quiet periods; going live during pre-order intake, a delivery peak or year-end closing raises risk.
- Open orders. Pre-orders for future seasons, back orders and open invoices must be migrated without losing delivery dates or terms.
- Custom code. Years of modifications are often undocumented; deciding which to retire takes longer than expected.
How should the business case and ROI be measured?
A credible case compares the cost of migration with the cost of staying: extended maintenance premiums, security and compliance risk on unsupported software, and the effort of maintaining integrations to an ageing platform. Benefits should be expressed in measures the business already tracks, such as order processing time, stock accuracy, deductions from retailers, inventory levels and the time needed to onboard a new wholesale account or marketplace. Vendor benefit claims are a starting point, not evidence; insist on baselines from your own data.
What should fashion leaders decide first?
- Confirm the support end dates for your current system and any industry add-ons.
- Choose the approach (conversion, greenfield, selective or platform switch) based on how much process change the business can absorb.
- Inventory every integration and assign an owner for each partner connection.
- Fix the go-live window around the season calendar, and protect it.
- Start master data clean-up before the system integrator arrives.
Finally, plan for the period after go-live. Retailers, marketplaces and logistics partners will notice any change in document quality or timing before internal users do. Agree a monitoring plan for the first weeks with key accounts, keep a contingency for manual order handling, and schedule a review of deductions and rejected files about a month after cut-over to catch problems that testing missed.
Frequently asked questions
When does SAP ECC support end?
SAP's mainstream maintenance for Business Suite 7 core applications, including ECC, runs until the end of 2027. Customers can buy optional extended maintenance from 2028 to 2030 at a premium.
What happens to SAP AFS users?
SAP AFS runs on the ECC platform, and SAP partner Rizing writes that its support ends in 2027. AFS users are typically evaluating S/4HANA Fashion or other ERP platforms.
Is Dynamics AX 2012 still supported?
No. Microsoft's mainstream support for Dynamics AX 2012 R3 ended on 13 October 2021 and extended support on 11 January 2023. Microsoft recommends migration to Dynamics 365.
How long does a fashion ERP migration take?
It varies with scope, approach and data quality, from a contained project for a smaller company on standard processes to a multi-year programme for multi-country groups. Integrations and cut-over planning around the season calendar often drive the timeline.
One edition every weekday morning. Read in five minutes. Free for industry professionals.
