SAP S/4HANA migration services: choose your path, check custom code and data, and plan your timing. Read this before you begin.

SAP S/4HANA Migration: What to Get Right Before You Start the Project

Before an S/4HANA migration starts, settle three things: your path (fresh build, conversion or a mix), the state of your custom code and data, and your timing against SAP’s maintenance dates. SAP S/4HANA migration services work best when these choices are made first, not mid-project.

This is for finance, operations and IT leaders still running SAP ECC and planning the move. You’ll get a plain comparison of the paths, the timing facts as we understand them, and the things that quietly blow out budgets.

What should you decide before you start?

Decide the path first, because everything else follows from it. There are three common ones. A new implementation (greenfield) builds S/4HANA fresh. A system conversion (brownfield) converts your existing system in place. Selective data transition is a blend of both.

Path What it means Suits What to watch
New implementation Fresh system, processes redesigned Messy or heavily modified systems, or consolidating several ERPs Usually migrates master data, open items and balances only, not full history
System conversion Existing system converted, processes and custom code carried over Stable, well-run systems you mostly want to keep Your system must be on a recent release, and old problems come with it
Selective data transition Mix of the two, often phased by country or business unit Businesses that want fresh design plus selected history More planning, and more parties involved

That table follows a 2023 SAPinsider session by Lemongrass Consulting on the three paths. Treat it as a starting point, not a verdict.

If your processes work and your system is clean, conversion is often quicker. If your system is a patchwork of workarounds, moving it unchanged just moves the mess.

What do SAP’s maintenance dates mean for your timing?

They set a deadline, but they shouldn’t choose your path. Forrester’s January 2025 analysis calls 2027 the current mainstream maintenance end date for the older ERP, with extended maintenance to 2030. It also reports a separate, conditional SAP option running to the end of 2033, aimed at large and complex environments, and notes it isn’t a blanket offer. E3 Magazine reported in October 2025 that extended maintenance to 2030 is optional and chargeable.

Details like these change, and parts of the 2033 option were still being clarified when those pieces were written. Confirm your own dates and any fees with SAP before you plan around them. And don’t squeeze a project into a rushed timeline just to meet a date.

How do you find out what you’re in for?

Run the SAP Readiness Check early. The Lemongrass session recommends doing it at the start to get a planning baseline. It describes it as a cloud-based self-service tool in the SAP Support Portal that covers simplification item relevance, custom code at a high level, Fiori app recommendations, sizing, add-on compatibility and business functions.

It’s a baseline, not a plan. It’ll tell you what needs attention. It won’t tell you who’ll fix it or how long that takes.

Why are custom code and processes the hidden bill?

Because every old modification has to be reviewed, retired or rebuilt, and each one needs an owner. Many ECC systems carry years of tweaks that nobody fully remembers.

That’s why the early strategy work matters. Pansoft lists SAP Strategy and Consulting alongside implementation and migration on its SAP page, and the pairing makes sense: decide what to keep, change or drop before anyone configures anything. This is also where business process re-engineering belongs. If a process only exists because the old system forced it, a migration is your chance to drop it.

What about the data?

Plan it as its own workstream. SAP’s S/4HANA migration cockpit comes with migration object templates, maps source data to the target, runs validation checks, and can load through staging tables. SAP says there’s no extra cost to use it. It also offers direct migration from an SAP system over an RFC connection.

It loads data. It doesn’t clean it. Duplicate customers, dead suppliers and mismatched codes remain your job, and ERP data migration is where many projects lose weeks. Our ERP solutions overview covers how that work is structured, and the same questions apply whichever path you pick.

Should you look at other platforms at the same time?

Sometimes. A forced move can be a good moment to ask whether SAP is still the right fit, and Oracle is the usual alternative for large ERP. Pansoft also works with Oracle, so we can speak to both.

But switching vendors is a bigger project than upgrading, with new processes, new skills and a full data move. Do it because the business case supports it, not because the deadline is close.

What should you do before you start?

  1. Choose your preferred path, and write down why.
  2. Run the SAP Readiness Check and read the results with your finance and operations leads.
  3. List custom code and workarounds, and mark each one keep, rebuild or retire.
  4. Name an owner for each data set, and start profiling the data now.
  5. Confirm your SAP maintenance dates and any fees directly with SAP.
  6. Ask for a plan from a provider who knows SAP Solutions Australia projects, with SAP implementation, data and testing as separate workstreams.

Frequently asked questions

Do we have to move to S/4HANA by 2027?

Not necessarily. Reports describe 2027 as the end of mainstream maintenance, with optional extended maintenance to 2030 and a conditional option to 2033. Confirm your dates, fees and eligibility with SAP, then plan around your business needs rather than just the deadline.

Is a new implementation or a system conversion better?

It depends on your system. A clean, well-run system often suits conversion. A heavily modified or messy one often suits a fresh build. Some weigh a mix of the two. A readiness check and a code review will show which is realistic.

Can we keep our historical data?

Often yes, but it depends on the path. A new implementation commonly migrates master data, open items and balances only, while conversion carries the existing data across. Selective data transition aims to keep chosen history. Decide what you really need before you commit.

Want a second opinion on your S/4HANA plan?

If you’re planning the move and want a straight view before you commit, get in touch with Pansoft on (07) 5646 4560 or through the contact page. There’s no pressure. We’re happy to look at your scope and tell you what we’d check first.

Leave A Comment