SAP Implementation Roadmap: Phases, Owners and Go-Live Milestones

9 min read ยท 2026-10-25

An SAP implementation roadmap lays out how your organization moves from its current systems to SAP, usually SAP S/4HANA, through a fixed sequence of phases, each closed by a quality gate. Most projects follow SAP Activate, SAP's own methodology, which runs through six phases: discover, prepare, explore, realize, deploy and run. For a single-company S/4HANA rollout with a handful of core processes, a plan of around 12 months from kickoff to stable operation is a common starting point.

The roadmap below follows those phases with the work you will actually do in each: fit-to-standard workshops, configuration sprints, data migration loads, testing cycles, training, cutover and hypercare. It adds what program managers and finance or IT leads need to run the project: owners on both the business and partner side, checkable milestones, the risks that cause most delays, and how to report to the steering committee.

The roadmap at a glance

Goal: SAP S/4HANA live for the agreed scope, with migrated data reconciled, trained users, the first month-end close completed and support handed to the run team. Duration: 12 months

  1. Discover and prepare (Months 1-2)

    Confirm scope, set up the program and get the team and systems ready.

    • Confirm the business case, scope, deployment option and the processes in scope, such as finance, procurement, sales and inventory.
    • Sign the system integrator contract and agree on the governance: steering committee, program board and design authority.
    • Name business process owners and key users for every process area.
    • Set up the project systems, tools and the starter configuration based on SAP Best Practices.
    • Write the project plan, RACI, risk log and communication plan, and hold the kickoff.

    Milestone: Quality gate 1 passed: charter signed, governance in place, team named and systems provisioned.

  2. Explore: fit-to-standard (Months 3-4)

    Walk through standard SAP processes and decide where you adapt the business instead of the system.

    • Run fit-to-standard workshops per process area, using the preconfigured system with your key users.
    • Record every gap and decide: adapt the process, use configuration, or build an extension.
    • Agree on the data migration scope, objects and source systems.
    • Define integrations, reports, interfaces, forms and authorizations in a backlog.
    • Get sign-off of the solution design from process owners and the design authority.

    Milestone: Quality gate 2 passed: signed design with a prioritized backlog of configuration, extensions and integrations.

  3. Realize: build and test (Months 5-8)

    Configure and build the solution in sprints and prove it works end to end.

    • Configure and build in short sprints, with demos to key users at the end of each.
    • Run data migration test loads and reconcile them with finance and process owners.
    • Run integration testing across processes, such as order to cash and procure to pay.
    • Run user acceptance testing with key users on realistic scenarios and migrated data.
    • Build role-based training material and the end-user training plan.

    Milestone: Quality gate 3 passed: user acceptance testing signed off, with no open critical defects and migration loads reconciled.

  4. Deploy: cutover and go-live (Months 9-10)

    Train users, run the cutover and go live.

    • Train end users by role, and confirm they can complete their key tasks.
    • Run at least one full dress rehearsal of the cutover with timings.
    • Freeze legacy changes, run the final data loads and reconcile balances.
    • Hold a go/no-go meeting with the steering committee using agreed criteria.
    • Go live and open the hypercare support desk.

    Milestone: Go-live completed, opening balances reconciled and signed off by the CFO or finance lead.

  5. Hypercare and stabilize (Months 10-11)

    Support users closely and fix issues until operations are stable.

    • Run daily issue triage with the integrator, key users and IT.
    • Track ticket volume, open critical issues and process KPIs like order processing time.
    • Support the first month-end close step by step with finance.
    • Update training material and job aids from the questions users raise.

    Milestone: First month-end close completed in SAP and critical tickets back to a normal level.

  6. Run and handover (Month 12)

    Hand over to the run organization and plan improvements.

    • Transfer support to the internal SAP team or the managed service provider, with documentation.
    • Hold a lessons-learned review with the business, IT and the integrator.
    • Close the project and the integrator's deliverables.
    • Build the backlog of next improvements and phases, such as additional sites or modules.

    Milestone: Support formally handed over, project closed and the improvement roadmap approved.

SAP Activate phases explained

SAP Activate replaced the older ASAP methodology for S/4HANA projects. It combines a ready-to-run starting configuration, a guided method and agile delivery during the build. Its key idea is fit-to-standard: start from SAP's standard processes and change the business process where you can, instead of customizing the system to match how things work today.

Each phase ends with a quality gate, a formal check that deliverables are complete before the next phase starts. Treat these gates as real decisions with the steering committee, not as paperwork. Confirm the exact deliverables for each gate with your system integrator and SAP's own Activate documentation, since they vary by deployment option.

  • Discover: confirm the business case and scope.
  • Prepare: set up the project, team, governance and systems.
  • Explore: fit-to-standard workshops and solution design.
  • Realize: configure, build, migrate data and test in sprints.
  • Deploy: train users, cut over and go live.
  • Run: stabilize, support and keep improving.

Example: a 12-month S/4HANA rollout for a mid-size manufacturer

Picture a manufacturer with one legal entity, two plants and an old ERP that is going out of support. The CFO sponsors the move to S/4HANA for finance, procurement, sales, inventory and production planning. A system integrator provides the consultants; the company provides process owners and key users.

Here is how the roadmap could look filled in, with an owner and a milestone per phase.

  • Months 1-2 (program manager): governance set, seven process owners named, starter system provisioned. Milestone: kickoff held and quality gate 1 passed.
  • Months 3-4 (process owners and integrator leads): fit-to-standard workshops; most gaps closed by adapting the process, a few extensions approved for plant labels and a customer portal interface. Milestone: design signed.
  • Months 5-8 (integrator and key users): four build sprints, three migration test loads, integration testing and UAT. Milestone: UAT signed with no critical defects.
  • Months 9-10 (program manager and IT lead): two cutover rehearsals, go-live over a weekend after the month-end close. Milestone: opening balances signed off by the CFO.
  • Months 10-11 (finance lead): first month-end close in SAP with integrator support. Milestone: close completed.
  • Month 12 (head of IT): handover to the internal support team. Milestone: improvement roadmap approved, including a third plant next year.

Who owns what

SAP projects fail more often from missing business ownership than from technical problems. The system integrator configures the system, but only your people can decide how your business should run on it. Name business process owners for each area and free up their time.

A common rule of thumb is to plan a large share of key users' time for the project during explore and realize. Back-fill their day jobs, or the project will wait on them.

  • Executive sponsor (often the CFO or COO): owns the business case, chairs the steering committee, settles scope disputes.
  • Program manager: owns the plan, budget tracking, risks and reporting.
  • Business process owners: decide the future process and sign off design and testing.
  • Key users: attend workshops, test, train end users and support at go-live.
  • System integrator lead: owns configuration, build quality and the integrator team.
  • IT lead: infrastructure, integrations, security, authorizations and the run organization.
  • Data migration lead: data cleansing, mapping, loads and reconciliation.
  • Change and training lead: communication, training plan and readiness checks.

Data migration and cutover planning

Data migration is the part most often underestimated. Start cleansing data in the prepare phase, not in realize. Decide what to migrate: usually master data such as customers, vendors and materials, open items such as open orders and invoices, and balances, with history kept in an archive or the old system in read-only mode.

Plan several test loads, each reconciled by the business, before the final one. The cutover itself needs a runbook: an hour-by-hour list of tasks with owners, dependencies and checkpoints, rehearsed at least once in full. The go/no-go meeting should use criteria agreed in advance, such as reconciled balances, no open critical defects and users trained.

  • Data objects: list each one with its source, owner and migration method.
  • Test loads: at least three, each reconciled and signed off.
  • Cutover runbook: tasks, owners, start times, durations and rollback points.
  • Go/no-go criteria: agreed with the steering committee before the meeting.

Risks and dependencies

Write each risk with an owner and a fallback in the risk log and review it at every program board. The ones below come up in most SAP programs.

Watch business calendars closely. Go-live dates that collide with year-end, peak season or an audit put extra load on the same people who need to support the new system.

  • Too many customizations: owner is the design authority; fallback is to reject gaps that do not have a clear business case.
  • Key users pulled back to their day jobs: owner is the sponsor; fallback is back-fill or a revised timeline.
  • Dirty data: owner is the data migration lead; fallback is an extra test load and a cleansing sprint.
  • Integration delays with third-party systems: owner is the IT lead; fallback is a manual interim process for go-live.
  • Late testing defects: owner is the test lead; fallback is to move go-live rather than skip UAT.

How to report to the steering committee

Keep the steering committee pack short and decision-focused. One page should show phase, next quality gate date, overall status, budget against plan, top five risks and decisions needed. Add a slide on business readiness, such as training completion and data quality, because that is what usually delays go-live.

Leave configuration details, defect lists and sprint burndowns to the program board. The steering committee should see trends and decisions, not tickets. Ahead of each quality gate, send the gate checklist with each item marked complete or not, and the decision you need: pass, pass with conditions, or hold.

Common mistakes to avoid

  • Customizing SAP to match old processes adds cost and makes upgrades harder, so use fit-to-standard and change the process where you can.
  • Treating SAP as an IT project leaves design decisions without owners, so name business process owners and give them time.
  • Starting data cleansing late delays go-live, so begin in the prepare phase and plan several test loads.
  • Rushing user acceptance testing to protect the date moves problems into production, so agree on go-live criteria and stick to them.
  • Skipping a full cutover rehearsal leaves timings untested, so rehearse the whole runbook at least once.
  • Ending support at go-live leaves users stranded during the first close, so plan hypercare through at least one month-end.

Frequently asked questions

What are the phases of an SAP implementation?

SAP Activate, the methodology SAP recommends for S/4HANA, has six phases: discover, prepare, explore, realize, deploy and run. Older projects used the ASAP methodology, with phases such as project preparation, business blueprint, realization, final preparation, and go-live and support.

How long does an SAP implementation take?

It depends on scope, number of countries and entities, data quality and how much you customize. A single-company S/4HANA rollout with standard processes can fit in about a year, while global programs with many entities often run in waves over several years. Your integrator should estimate based on your actual scope.

What is fit-to-standard in SAP?

Fit-to-standard is the approach used in the explore phase. Key users walk through SAP's standard processes in a preconfigured system and decide where the business can adapt, keeping customization to real gaps. It replaces the older blueprint approach of designing everything from scratch.

Who should be on an SAP implementation team?

You need an executive sponsor, a program manager, business process owners, key users, a data migration lead, an IT lead, a change and training lead, and the system integrator team. Business people must own design decisions and testing, not only the integrator.

What is hypercare after SAP go-live?

Hypercare is a period of close support right after go-live, with daily issue triage and fast fixes. It usually lasts until operations are stable, often through the first month-end close, before support moves to the normal run team.

Generate this roadmap with AI