Lesson 1 of 5
New implementation
9 min
SAP describes three main ways to move to SAP S/4HANA: new implementation, system conversion and selective data transition. They differ in what you keep from the old system (configuration, custom code, history) and what you redesign. This course takes each in turn, then compares them and their testing demands. Start with the cleanest break: the new implementation, often called greenfield.
| New implementation | System conversion | Selective data transition | |
|---|---|---|---|
| Basic idea | Build a new system; migrate data into it | Convert the existing ERP system in place | Build a new or shell system; move selected configuration and data |
| Processes | Redesigned, often from SAP Best Practices | Kept, adjusted where SAP S/4HANA requires | Chosen: some reused, some redesigned |
| Custom code | Rebuilt only where still needed | Kept and adapted | Selected and adapted |
| History | Usually open items and balances only | All history kept | Chosen: for example all history or a time slice |
| Target editions | Public Edition, Private Edition, on-premise | Private Edition, on-premise | Private Edition, on-premise |
How a new implementation works
In a new implementation, the program installs a fresh SAP S/4HANA system (or receives one from SAP in the cloud editions) and designs processes for it, typically with the SAP Activate methodology and SAP Best Practices content as the starting point. Fit-to-standard workshops compare the standard processes with the business's needs, and only real gaps become extensions. Data is then migrated: master data and open items, such as open orders, open receivables and payables, stock and balances, are loaded, usually with the SAP S/4HANA Migration Cockpit. SAP also positions SAP Data Services, with best practice migration content, for more complex extraction and transformation.
- Install or provisionA new SAP S/4HANA system in the chosen edition
- Fit-to-standardStandard processes and Best Practices reviewed with the business
- Configure and extendSettings and only the extensions really needed
- Migrate dataMaster data, open items and balances, rehearsed in mock loads
- Test and acceptEvery process tested end to end; users trained
- Cut overFinal load, validation, go-live; old system read-only or archived
When it fits
- The source is a non-SAP legacy system, so there is nothing to convert.
- The SAP source is old, heavily modified, or does not meet the technical requirements for conversion.
- The business wants to redesign processes and drop years of workarounds.
- The target is SAP S/4HANA Cloud Public Edition, which is reached only by new implementation.
- The organization is ready to accept that history stays in the old system or an archive.
Effort and risk profile
A new implementation front-loads design effort and puts a heavy load on the business: every process must be re-decided, re-tested and re-learned. Data migration is a large workstream in its own right, with mock loads, reconciliation and owner sign-off. In return, the program can simplify radically and starts with a clean core. The biggest risks are scope creep in design, underestimated data migration and change fatigue among users.
What would you do?
A distribution company runs a non-SAP legacy ERP and wants to move to SAP S/4HANA Cloud Public Edition within 18 months. Which path applies?
- Three paths: new implementation, system conversion, selective data transition.
- New implementation: new system, Best Practices and fit-to-standard, data migrated with the Migration Cockpit.
- Fits non-SAP sources, old or heavily modified SAP systems, process redesign and Public Edition.
- Highest process change and data migration effort; history usually stays behind.
Check your understanding · not graded
Lesson check
1. In a new implementation, which data is usually migrated?
2. Which tool does SAP position for loading data in a new implementation?
3. Which target edition can be reached only by a new implementation?
4. What is a major risk of a new implementation?