ERP Cutover: How to Plan an SAP Cutover, and Where AI Agents Help With ERP Data Migration
An ERP cutover moves the final data, interfaces and users from the old ERP to the new one. The SAP cutover plan, go-live checks, and where AI agents help.

An ERP cutover is the planned window in which a company stops working in its old ERP, moves the final balances, open items and master data into the new one, switches its interfaces and users, and starts transacting in the new system.
In an SAP S/4HANA project, SAP describes the cutover plan as every task that must be performed before go-live, with timelines, responsibilities, resources and contingency plans, executed in the days before go-live once integration testing and user acceptance testing are complete.
Most of the risk sits in a few days: data taken at the wrong moment, a balance that does not agree, or an interface still posting to the old system. That is where checks matter more than tools.
Where engini fits: engini is not a migration or cutover tool, and the load itself belongs in SAP's tools. engini works around the cutover: its SAP S/4HANA connection reads and writes through the OData services your SAP administrator selects, and its database, file and on-prem connections reach the legacy side, so you can run the same reconciliation checks after every rehearsal and at the final cutover, and rebuild the interfaces that fed the old ERP against S/4HANA. See the SAP S/4HANA connection docs.
Key Takeaways
- An ERP cutover is the final move from the old system to the new one: last data loads, interface switches, user access and a go or no-go decision.
- SAP's guidance puts cutover execution in the days before go-live, after end-to-end integration tests and user acceptance testing, and ends it with go-live acceptance criteria, including validation of the master and transactional data loaded.
- Rehearse the cutover at least once with production-like data, and run the same reconciliation checks every time.
- AI agents help by comparing, explaining and reporting; the load belongs in SAP's migration tools, and pass or fail belongs to fixed checks.
- Interfaces are part of the cutover: every system that sent data to the old ERP has to send it to the new one from the first day.
What Is an ERP Cutover?
An ERP cutover is the switch from the legacy ERP to the new ERP at a fixed point in time, the cut-off, after which all new transactions are entered only in the new system. It covers more than data: the cutover also moves interfaces, user access, printers and output, bank files and the reporting that depends on the ERP.
In data migration, "cutover" means the final, production load. Earlier loads in test systems are rehearsals; the cutover load takes the data as it stands at the cut-off, loads it into production and proves it arrived intact. Master data such as customers, vendors, materials and the chart of accounts often moves before the cutover weekend, while open items and balances move at the cut-off because they change every day.
The same idea applies outside SAP. A bank replacing its core system, or a company moving from NetSuite to another ERP, runs a cutover with the same parts: a freeze, a final load, reconciliation, a decision and a period of close support. For the banking case, see core banking migration with AI agents.
What Goes Into an SAP Cutover Plan?
An SAP cutover plan lists every task between the last rehearsal and the first day on the new system, with an owner, a start time, a duration and a fallback. SAP's own guidance for S/4HANA Cloud Private Edition says the plan includes timelines, responsibilities, resources required and contingency plans, and that the customer signs off go-live against predefined acceptance criteria.
SAP lists data integration validation, meaning the accuracy of master and transactional data loaded into the new system, among its common go-live acceptance criteria, next to integration and acceptance testing, end-user training and the absence of critical open issues.
Tip: write the cutover plan as a minute-by-minute runbook, and time every step during the rehearsal. The rehearsal tells you whether the plan fits inside the window you have.
The tools that do the load
SAP's tools load the data; the cutover plan decides when. SAP's course material describes the SAP S/4HANA Migration Cockpit as an embedded tool at no additional cost that migrates data from SAP or non-SAP legacy systems, either through staging tables or directly from an SAP ERP system over an RFC connection. For the other tools and when each fits, see SAP data migration tools, and for the errors they raise, see SAP S/4HANA data migration troubleshooting.
Big Bang, Phased or Parallel: Choosing a Cutover Strategy
The cutover strategy decides how much moves at once. A big bang cutover moves everything in one window; a phased cutover moves one company, region or process at a time; a parallel run keeps both systems live for a period and compares them. Each trades risk against effort.
A phased cutover adds interfaces that exist only during the transition, for example intercompany postings between an entity already on S/4HANA and one still on the legacy ERP. Plan them, test them and plan their removal.
What Goes Wrong in an ERP Cutover
Most cutover failures are data that loaded without an error but means something different in the new system, or data taken at different moments. These are the problems finance teams usually find in the first period close:
- Chart of accounts mapping. A legacy account with no clear S/4HANA equivalent is mapped to the closest one, and costs land in the wrong account. The record loads cleanly; the error appears in reporting.
- Different cut-off times. Balances taken on Friday night and open items taken on Saturday morning will not agree, because something was posted in between.
- Currency and rounding. Historical balances translated at different rates or rounding rules than the new system uses leave small differences that add up across accounts and periods.
- Intercompany balances. If trading partners are not mapped the same way on both sides, intercompany balances stop eliminating in consolidation.
- Interfaces left behind. A CRM, store or bank file still sends data to the old ERP after cutover, and transactions go missing from the new one.
Agree with the controller, before the first rehearsal, which differences are acceptable by account and amount, and who signs off. For the wider risks of connecting older finance systems to new ones, see legacy accounting system integration.
Where AI Agents Help in an SAP Cutover, and Where They Do Not
AI agents help a cutover where people read, compare and report; they should not load data or decide whether the cutover passes. The load belongs in SAP's tools, and the go or no-go belongs to fixed checks and the people who signed the acceptance criteria.
Note: a cutover needs results you can repeat and audit. Read and write through each system's APIs rather than its screens, and keep the comparison logic fixed so every rehearsal is measured the same way.
How Do AI Agents Connect to an ERP Like SAP S/4HANA?
AI agents connect to an ERP through its APIs, with a layer in between that holds the credentials, limits what the agent may call and records what it did. In S/4HANA the standard web APIs are OData services, which your SAP administrator enables and authorizes, so the agent works with business data rather than with SAP's screens.
The layer in between matters more during a cutover than at any other time, because two systems hold the truth at once. A useful setup gives a reconciliation agent read access to both the legacy system and S/4HANA, and no write access to either. For how agents reach other systems, see engini connectors.
How engini Helps Around an SAP Cutover
engini does not migrate data or run the cutover. It runs the checks and the interfaces around it, on the legacy side and on S/4HANA.
- Reconciliation after every rehearsal and at cutover. A workflow in Workflow Studio, engini's visual builder, reads records from S/4HANA through the OData services your SAP administrator selects, reads the legacy extract from a database or a CSV file, compares totals by company code and account, and writes each difference into an engini Table for the finance team. Each run stays in the workflow's run history, so one rehearsal can be compared with the next.
- The legacy side, wherever it sits. Databases such as SQL Server, Oracle Database and IBM DB2, and file drops in local folders and network shares, through the on-prem agent, which opens only outbound connections, so you open no inbound ports. Extracts can also arrive over SFTP.
- A read-only agent for questions. From the SDK or REST API, give a reconciliation agent a toolset that allows only reads on the S/4HANA and legacy connections. engini's server refuses any call outside it, so the agent can compare and explain but cannot change a record.
- Judgment where it helps. An AI agent step can group differences by likely cause and write a short summary for the cutover call; the finance team decides what to fix.
- Interfaces built before go-live. Rebuild the flows that fed the old ERP, from the CRM, the online store, bank files and internal databases, against S/4HANA, and test them in a separate development or staging environment inside your engini workspace before the switch. Every integration runs both ways, so invoices and payment status can flow back to Salesforce or HubSpot. See our Salesforce and SAP integration guide.
- Controls. Roles, single sign-on, and an audit log with export and streaming to a SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call. engini holds SOC 2 Type II and ISO 27001.
What engini does not do: it does not load data into S/4HANA, it has no direct connection to SAP ECC, and SAP's IDoc and RFC interfaces are not documented for its SAP connection, so read the legacy side from extracts, databases or files.
When you do not need engini: if your data comes from one SAP system that SAP's own tools move directly, no other system exchanges data with the ERP, and your migration tool's reconciliation reports give finance the checks it needs, SAP's tools may be all the cutover requires.
Frequently Asked Questions
What is an ERP cutover?
An ERP cutover is the planned switch from the old ERP to the new one at a fixed cut-off, after which new transactions are entered only in the new system. It covers final data loads, interfaces, user access and a go or no-go decision.
What is cutover in data migration?
Cutover in data migration is the final load into the production system at the cut-off point. Earlier loads are rehearsals; the cutover load takes current balances and open items, loads them and proves they reconcile.
What is an SAP cutover plan?
An SAP cutover plan lists every task that must be done before go-live, with timelines, owners, resources and contingency plans. SAP places its execution in the days before go-live, after integration and user acceptance testing.
How do you integrate AI agents with an ERP?
You integrate AI agents with an ERP through its APIs, with a layer that holds credentials, limits which actions the agent may call and logs each call. In SAP S/4HANA, those APIs are OData services.
engini provides that layer for agents built with MCP, the SDK, the REST API or the CLI, and for workflows built in Workflow Studio. See the engini documentation.
Can AI agents migrate data into SAP without code?
AI agents should not run the load; SAP's migration tools should, and the Migration Cockpit already provides predefined migration object templates. AI agents are useful around the load, comparing and explaining the results.