Start with business constraints
Define what must remain stable, what must change and how much downtime or historical-data change the organisation can tolerate.
What UK organisations should look for in an S/4HANA migration partner before committing to a migration path, delivery model or cutover date.
The migration partner should do more than run a technical conversion. Brownfield, greenfield and selective transition change the risk profile for processes, historical data, custom code, integrations, roles, testing and downtime. A supplier that chooses the path before understanding those constraints may simply move risk into later phases.
Use the steps to move from assumption to evidence and then to a decision.
Define what must remain stable, what must change and how much downtime or historical-data change the organisation can tolerate.
Make the partner connect code, data, interfaces, security, testing and business readiness rather than manage them as isolated workstreams.
Use realistic volumes and business reconciliation in migration and cutover rehearsals.
Know who owns defects, monitoring, reconciliations and design decisions once the programme moves into support.
We keep deliverables tied to decisions, delivery and ownership. The exact format changes with the workstream; these are the outputs we would expect to leave behind.
Liditech focuses on difficult S/4HANA workstreams including migration readiness, custom code, integrations, data, cutover and programme recovery.
The current problem, the outcome you need and what cannot be disrupted are enough to start.