Every firm planning a migration on the SAP side needs three dates settled. The timeline has shifted over the years, and that shift causes mistaken planning.
01. Three Dates
Mainstream maintenance for Business Suite 7 core applications ends at the close of 2027. Optional extended maintenance then runs to the end of 2030. For S/4HANA, a maintenance commitment has been given through the end of 2040.
02. Extended Maintenance Isn't Free
Continuing past 2027 carries an extra fee and narrower scope than mainstream maintenance. It should be seen not as a solution but as time bought to plan the migration.
03. Why Start Early
An S/4HANA migration is not a technical upgrade but a rethink of processes. Even at a mid-sized firm it's a programme exceeding a year including preparation. A plan targeting 2027 should already have started.
04. The Migration Approach
There are three routes: converting the existing system, a greenfield implementation, or a selective transition. Where the customisation burden is heavy, greenfield often produces the cleaner result.
05. The Turkish Dimension
Localisation, e-document integration and local reporting requirements belong in scope from the start. Added later, this item is the one that most often breaks the timeline.
06. Assessing Alternatives
Where migration cost comes out high at mid-sized firms, evaluating an alternative ERP also enters the discussion. The decision should follow current process complexity and any need for overseas operations.