Open transactions are handled through an explicit disposition by object and status. Teams decide what should be completed or cancelled in the legacy system, which supported open items or orders should be migrated, which transactions must be recreated in the target system, and what reconciliation evidence will prove that the opening state is complete without duplicating or losing business activity.
Do not apply one rule to every open transaction
Accounts payable items, customer receivables, purchase orders and sales orders behave differently. SAP migration documentation lists open transactional data and balances among migration content, but support depends on the migration object and the business state of the document. The cutover design therefore needs object-specific rules rather than a generic instruction to “move all open transactions.”
Clean up the source before deciding what must move
Old, duplicated, fully satisfied or no-longer-required transactions should be reviewed before the cutover extract. SAP guidance for open purchasing and sales documents notes that partially open documents may need to be closed or cancelled in the source system. Cleaning the population reduces target-system noise and makes reconciliation easier.
Business owners must agree the disposition
The migration team should not decide alone whether an open transaction is still commercially valid. Finance, Procurement, Sales and operations need to confirm which populations are genuinely open, what follow-on processing is still expected and who owns unresolved exceptions. That decision becomes part of the cutover scope and freeze discipline.
Open receivables and payables need balance continuity
Open customer and supplier items are often part of the financial opening-state design. The key question is not merely whether records can be loaded, but whether the target system contains the correct residual open amount, currency, due-date and reference information needed for subsequent clearing and reporting. Control totals should reconcile the source population to the migrated result.
Open purchase and sales orders need process continuity
An open purchase order may have receipts or invoices already posted; a sales order may have partial delivery or billing history. SAP migration guidance notes restrictions for partially open documents and documents with follow-on activity. The cutover rule must therefore consider what history stays in legacy, which remaining quantity can continue in the target system and whether the document should instead be closed and recreated.
Freeze and delta rules protect the cutover boundary
Once the final open-transaction population is extracted, teams need a clear rule for activity that occurs afterward. Depending on the process, the business may stop posting, restrict activity to emergencies, capture a controlled delta, or plan manual recreation. Without a boundary rule, the source and target can diverge before the new system is live.
Reconciliation proves that continuity survived the move
After migration or recreation, teams should compare counts, values and important statuses against the approved source population. Financial open items need balance reconciliation; orders need quantity and status checks; material or inventory opening positions need their own control totals. The objective is to prove completeness and prevent both missing and duplicated activity.
Keep legacy responsibility explicit
Some history or transactions may remain in the legacy system by design. Users need to know which system is authoritative for historical inquiry, which transactions continue in the new ERP, and how cross-system questions will be handled after go-live. A cutover can be technically successful and still confuse operations if that ownership boundary is unclear.
Consultant thinking: classify before you migrate
The safest design begins with a disposition matrix: object type, business status, supported migration behavior, source action, target action, owner and reconciliation evidence. That turns “open transactions” from a vague migration topic into a set of controlled business decisions.
Continue with What SAP Cutover Means, How a Cutover Plan Is Built, How Cutover Dependencies Are Managed, How Data Migration Mock Loads Are Tested, and the Consulting & ERP Projects hub.