The ECC 6.0 to S/4HANA migration was supposed to be straightforward.

Three months in, it looked more like a disaster zone than a transformation.

Had a conversation with a CIO at a $3B manufacturing firm today.

He told me something that stuck with me.

Data migration issues everywhere. material masters, open purchase orders, uncleared FI documents that wouldn’t pass HANA’s stricter validation.

Custom code hidden in places no one documented.
Department heads fighting over their must-have features.

ABAP modifications buried in MRP, pricing exits in SD, years of Z-programs nobody wanted to own.

The original plan? Hire one big consultancy to manage everything.

Their response to every challenge? “That’ll require additional scope.”

Then something shifted.

Instead of one generalist team trying to handle it all, they brought in specialists:

→ A data migration expert who’d survived every migration nightmare – LSMW, BODS, failed IDocs and all
→ A process consultant who could translate between business and technical
→ An integration specialist who understood the legacy chaos – PI/PO, EDI , the WMS connections nobody had mapped
→ A change management pro who recognized this as the people challenge it actually was

The conversations changed overnight.

Problems got solved instead of kicked upstairs.
Timelines became achievable.
Teams started believing in the process again.

The difference wasn’t more budget or better technology.

It was pairing specific expertise with actual problems instead of hoping one team could cover everything.

The big consultancy model works fine when your challenge is straightforward.

But complex migrations aren’t straightforward.

They’re messy, political, and deeply technical all at the same time.

What’s your experience? Have you been on a project where specialists made the difference, or where keeping it simple with one vendor actually delivered?