Philippine SAP Record-Migration Retention Checklist

What must IT approve before SAP record migration?

IT should approve one disposition for every historical SAP record set before cutover: migrate it, preserve it in a tested archive, or delete it under an authorized rule. The decision needs a business owner, legal basis, retrieval test, retention period, and evidence that the chosen action completed.

Key takeaways

• Every historical record set needs one approved disposition before the migration load is finalized.
• A successful data load does not prove that archived records remain searchable, readable, and exportable.
• Philippine retention duties and privacy limits should be mapped by record type, not applied as one blanket period.
• Deletion needs authorization and completion evidence, not an unchecked project task.

SAP Learning's migration cockpit course, retrieved in September 2026, identifies three transition paths: system conversion, selective data transition, and new implementation. It also names two migration cockpit approaches for new implementations: staging tables and direct transfer from an SAP system. These are useful technical choices. They do not decide which historical records the business must retain or how an auditor will retrieve an archived item.

The Philippine boundary is specific. Republic Act No. 10173, approved August 15, 2012, says personal information should be adequate and not excessive. Section 11 also says it should be retained only as long as needed for its purpose, legal claims, legitimate business purposes, or a rule in law.

“Retained only for as long as necessary for the fulfillment of the purposes for which the data was obtained or for the establishment, exercise or defense of legal claims, or for legitimate business purposes, or as provided by law.”

That wording does not set one retention period for all SAP data. Legal, finance, tax, privacy, records, and process owners should identify the applicable basis for each record class. IT then implements the approved disposition and proves that it worked.

Which records should move, remain archived, or be deleted?

Records should move when current operations need them in the target system, remain archived when a valid purpose requires retrieval but not daily processing, and be deleted when no approved purpose or duty remains. The following record map is an original editorial decision aid, not an SAP template or legal opinion.

The record map should separate master data, open transactions, closed transactions, attachments, audit trails, output documents, and personal information. A single “history” category hides different owners and duties. The 2019 Revised Corporation Code illustrates why retrieval matters. Section 73 requires corporations to keep and carefully preserve specified corporate information. Section 74 requires a corporation to provide its most recent financial statement to a stockholder or member within ten days of receiving a written request. Section 74 also states a ₱600,000 asset-or-liability threshold for when the president and treasurer may certify the financial statements under oath, subject to any amount later set by the Department of Finance.

Those provisions do not say that SAP must hold every record or that every company has the same retention schedule. They show why a migration decision cannot be based only on storage cost or technical convenience. Counsel and accountable record owners should confirm scope. IT should record the approved basis, effective period, holds, disposal trigger, and retrieval method for each class before the source system is retired.

How should IT test an SAP archive before cutover?

IT should test an SAP archive by retrieving representative records through the future operating route, without relying on the source system or migration team. The test must prove search, authorization, readability, context, export, and reconciliation for records that will not move into the target ERP.

Run the test in this order:

1. Select real record patterns from each approved archive class, including an older period, an amended item, an attachment, and a record under hold when applicable.
2. Search with the identifiers the future support team will actually receive, such as document number, customer, vendor, date, amount, or company code.
3. Open the record and verify its linked context, including approvals, changes, attachments, and related accounting or operational entries.
4. Export the record in a readable form, record elapsed time, and confirm that an authorized reviewer can explain what the evidence proves.
5. Reconcile the sample to the source control total, then repeat the test after cutover credentials and support ownership are in place.

The SAP Business Technology Platform service is the relevant Appcentric route when a migration needs integration, data management, analytics, or an extension outside the core. The existing guide to unifying data management with SAP BTP addresses connected data and governance. Neither page proves that a specific archive can answer a records request.

For private-cloud S/4HANA programs, the RISE with SAP service is the matching Appcentric route. The separate guide on which custom code should survive an S/4HANA migration decides the treatment of software objects. This checklist decides the treatment and future retrieval of historical business records. Keep those approvals separate.

What do IT leaders ask about migration retention?

IT leaders usually need clear answers about ownership, archive testing, personal information, deletion evidence, and the migration cockpit. Each answer should resolve one approval question before the source environment is retired.

Does a successful migration load prove record retention?

Does a successful migration load prove record retention?

No. A load result proves that selected data reached the target under the project's technical checks. Record retention also requires an approved purpose, complete context, authorized access, readable output, search keys, and a tested retrieval route. Archived and deleted classes need their own evidence because they are outside the target load.

Can every closed SAP transaction remain in the archive?

Can every closed SAP transaction remain in the archive?

Not automatically. The accountable owner should identify the legal, contractual, audit, claim, or legitimate business basis for each record class. Section 11 of Republic Act No. 10173 limits identifiable personal information to necessary retention. A legal hold or another law may require longer preservation, so counsel should confirm conflicts.

Who approves deletion after an SAP migration?

Who approves deletion after an SAP migration?

The business record owner should request the disposition, while legal, privacy, tax, finance, or records owners confirm the applicable authority and exceptions. IT executes only the approved scope and retains completion evidence. A project manager should not infer deletion authority from a successful cutover or an expired application-support contract.

Should archived records stay in the old SAP system?

Should archived records stay in the old SAP system?

Only when the approved operating design can support it for the full required period. Test licenses, infrastructure, access administration, backup, readable output, and support ownership after cutover. If retrieval still depends on an unsupported source application or one former project specialist, the archive has not passed the operating test.

Does the SAP migration cockpit set retention periods?

Does the SAP migration cockpit set retention periods?

No. SAP Learning describes the migration cockpit, migration objects, staging tables, direct transfer, and selection criteria for data movement. The business still decides what should move and why. Philippine legal and record owners set the applicable retention and disposal rules; IT configures and tests the approved result.