SAP S/4HANA· Cutover
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 9 of 11 · Implementation · Updated October 26, 2026

SAP S/4HANA cutover and go-live

Cutover is the planned move from the legacy system to SAP S/4HANA: the freeze, the final loads, the opening balances and the go/no-go call. superglue's agent writes the runbook from the project and the rehearsal, runs the final and delta loads with the tested tools, and reconciles before you and the client make the call.

Start an SAP S/4HANA projectTalk to us

How this step works

What the agent does

  • Writes the cutover runbook with tasks, owners and timings from the rehearsal.
  • Runs the final and delta loads with the tools tested in the rehearsal.
  • Reconciles opening balances and open items against the legacy system.
  • Prepares the go/no-go summary with the open issues.

What you decide and approve

  • The cutover date and the freeze window.
  • Go or no-go, together with the client.
  • The fallback plan if the answer is no.

What the client gets

  • A cutover runbook.
  • A signed go-live reconciliation.

What makes a SAP S/4HANA cutover work

  1. 01

    Import the last transports before the freeze

    Move the final transports to PRD and stop changes in DEV before the final loads. A late transport changes the system you rehearsed.

  2. 02

    Control posting periods during the load

    Open only the migration period for the balance loads and keep later periods closed. Open the go-live period after the loads reconcile.

  3. 03

    Start jobs and interfaces after go/no-go

    Release MRP runs, payment runs, output and IDoc processing only after the go/no-go decision. A job that starts early sends documents built on half-loaded data.

  4. 04

    Sign off each company code

    Agree the checks per company code, such as the trial balance, open AR and AP, inventory value and asset values. When several company codes go live together, each one passes on its own.

Frequently asked questions

What makes a SAP S/4HANA cutover go well?

Import the last transports before the freeze; Control posting periods during the load; Start jobs and interfaces after go/no-go; Sign off each company code. The agent runs the final loads with the tools tested in the rehearsal.

Who makes the go-live call?

You and the client do. The agent prepares the reconciliation and the list of open issues for the go/no-go meeting.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into SAP S/4HANA?

Common sources are SAP ECC, Oracle E-Business Suite, Microsoft Dynamics AX, JD Edwards and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live SAP S/4HANA project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.