Home / SAP staffing / Staffing an S/4HANA migration

Staffing an S/4HANA migration: which roles you need in each phase

An S/4HANA migration doesn't need the same team from start to finish. The roles change as the program moves through SAP Activate, and most staffing problems come from adding a role one phase too late. This guide maps the roles to each phase, flags the ones that need to start early, and is honest about what staffing can't fix.

Book a hiring call Call (561) 567-8381

First: which kind of migration?

Your migration type decides the staffing mix more than anything else.

Greenfield (new implementation). Design-heavy. Functional leads and the data migration lead carry the program, and data moves into the new system with tools such as the SAP S/4HANA Migration Cockpit.
Brownfield (system conversion). Technical-heavy. Basis runs the conversion, ABAP developers fix the custom code the simplification checks flag, and functional consultants handle the business changes the conversion forces, such as the Universal Journal in finance.
Selective data transition. A mix of both: technical migration work plus functional redesign for the parts of the business you're changing.

Roles by phase

Phase	What happens	Roles usually added	Bring them in
Prepare	Plan, team set-up, system readiness	Program or project manager, solution architect, Basis for sandbox and readiness checks	Before the phase starts
Explore	Fit-to-standard workshops and design	Functional leads per module, data migration lead, integration architect, security lead	At the start of Explore, not after design sign-off
Realize	Build, unit and integration testing, mock data loads	ABAP and Fiori developers, integration developers, test lead and testers, more functional consultants for configuration	Test lead before integration testing is planned
Deploy	Final testing, cutover, go-live	Cutover lead, Basis, data load support, training support	Cutover lead during Realize, when the cutover plan is written
Run	Hypercare, then steady operations	Module support consultants, Basis, a handover to your permanent team	Permanent owners named before go-live

What our recruiters see: roles requested a phase too late

These are the requests we see arrive late most often, and what the delay costs the program.

A data migration lead after design sign-off

Design assumes clean source data. The first mock load shows otherwise, and the fixes reopen decisions the business already signed. We ask for this role at the start of Explore.

A test lead when testing starts

Nobody has planned the test cycles, the test data or the business testers' time, so integration testing slips while the plan gets written. The test lead should be in place before integration testing is planned.

A cutover lead weeks before go-live

The cutover plan gets written by people still finishing the build, and the rehearsals get squeezed. Name the cutover lead during Realize, when the plan is written.

Permanent owners after hypercare

Contractors roll off before anyone on the permanent team has run a period-end close or a release on the new system. Name the owners before go-live and write the handover into each contract.

Contract or permanent, phase by phase

Contract fits phase-bound peaks: build and test in Realize, cutover, and hypercare.
Contract-to-hire fits roles you'll need after go-live but want to see in action first, such as the module leads who'll own support.
Full-time fits the people who'll run the system after hypercare: module owners, Basis and security. See full-time hiring.

What staffing can fix, and what it can't

Staffing can close skill gaps, get people in before the phase that needs them, add test capacity, and protect the handover to your permanent team. It can't fix scope changes, sponsor decisions, the quality of your source data, your integrator's contract terms or licensing questions. If those are the problem, more people won't solve it.

A staffing checklist for your plan

Migration type decided: greenfield, brownfield or selective
Data migration lead named before Explore
Integration architect named before design sign-off
Test lead in place before integration testing is planned
Cutover lead named during Realize
Permanent owner named for each module before go-live
Knowledge transfer written into every contractor's end date

Questions program leads ask

When should we start recruiting for an S/4HANA migration?

Start with the roles that shape design: the data migration lead, the integration architect and functional leads for your core modules, before Explore begins. Build and test roles can follow during Explore, since Realize is where you need them.

Does a brownfield conversion need fewer people?

Not necessarily fewer, but different ones: more technical work in Basis and custom code, and less redesign.

Can contractors hand over to our permanent team?

Yes, if it's planned. Write knowledge transfer into each contract and name the permanent owner before hypercare starts.

Send us your project plan.

We'll point out the roles that look late or thin and tell you how quickly we can fill them, with submittals within 48 hours of a clear requirement.

Book a hiring call Share your requirements