News Article
Your S/4HANA Migration Is Underway. But Have You Got the Right People for What Comes Next?
author
Mark Janson
Date
November 05 2026
There's a conversation we come back to regularly with businesses running SAP transformation programmes.
They've got the project underway. The team is in place, the plans have been agreed and everyone is focused on getting to the next stage.
At some point the conversation changes. A new phase is approaching. Testing is taking longer than expected. A specialist skill set is suddenly becoming more important. Someone who was central to the original implementation is moving on. Or the business starts thinking about what happens when the project team eventually steps away.
And the question becomes: Have we got the people we need for what's coming next?
Businesses can spend months planning the technology, the budget and the delivery milestones, but the resource plan doesn't always move at the same pace.
The team you started with might not be the team you need to finish
An S/4HANA programme isn't a static project. Priorities change, timelines move and the demands on the team evolve. The people who were essential during the initial design and build might not be the people you need in the same numbers when testing, cutover and go-live approach. Not because the original team wasn't right, it simply means the project has moved on.
We've seen how quickly resource requirements can change. A business might initially be looking for strong functional expertise, only to find that its next challenge is securing experienced testing resource, integration specialists or people who have been through multiple cutovers.
These aren't always straightforward profiles to find. The more specific the experience, the smaller the available talent pool can become. Add a fixed project deadline or a requirement for someone to start quickly, and the options can narrow further.
The difficult hires are often the ones you didn't plan for
There's a difference between knowing you'll need SAP consultants and knowing exactly which experience will make the difference at a particular point in your programme.
Some of the most challenging requirements aren't necessarily the biggest teams or the most obvious vacancies.
They might be:
- Someone with genuine experience of a similar S/4HANA transformation, rather than simply having S/4HANA on their CV.
- A specialist who can come into a challenging programme, understand what's happening quickly and make an immediate contribution.
- Someone who has handled complex cutovers and knows what can go wrong when the pressure is on.
- An experienced consultant who can help transfer knowledge before key project resources move on.
These are the sorts of requirements where a broad search for SAP experience isn't enough. Context, previous project experience, and understanding what someone has actually delivered is extremely important. And this is also why leaving these conversations until a vacancy becomes urgent can be risky.
Go-live isn't the end of the resource conversation
Another important consideration is what happens after the implementation team has done its job. Getting to go-live is a huge achievement, but the business still needs to operate, support users, resolve issues and get the most out of its new SAP environment.
We've seen businesses focus so heavily on getting the implementation over the line that the longer-term resource conversation gets pushed further down the list. Who will take ownership once the programme team moves on? Where will the internal knowledge sit? Will the existing SAP team have the capacity and experience to support the new environment? These aren't questions to start asking a few weeks before go-live.
Some contractors will have completed their part of the project. Others may be needed for stabilisation, specialist support or further improvements. Permanent teams may need strengthening to take on additional responsibilities.
The right approach will look different for every business, but the important thing is to have the conversation early enough to make informed decisions.
Don't wait until you need someone yesterday
One of the biggest challenges in specialist SAP recruitment is timing. The right person may be available today but committed to another project next month. A consultant with exactly the experience you need might have a notice period or be finishing an assignment elsewhere. And when a requirement becomes urgent, businesses can find themselves competing for a much smaller pool of available talent.
That doesn't mean hiring months in advance for every possible requirement. It means having a clearer view of what's coming, understanding where the gaps might emerge and starting conversations before those gaps become delivery problems. It also means being realistic about the profiles you're looking for, the experience genuinely required and the flexibility available around location, rates and start dates.
From our position, we get a view of both sides of these conversations: what businesses are going to need and what experienced SAP professionals are looking for in their next move or project. This perspective can be valuable when plans change or a requirement becomes more specialised than originally anticipated.
What's next for your SAP team?
If your S/4HANA migration is already underway, it's worth looking beyond your immediate vacancies. Are you confident you have the right expertise for the next project milestone? Have you thought about who will support the business after go-live? And are you having conversations about future resource requirements early enough to give yourself options?
The technology might be at the centre of your transformation, but it's people who need to be there to make it work.