The SAP S/4HANA Migration Cockpit allows you to transfer data from legacy SAP or non-SAP systems into S/4HANA in a controlled and auditable way. During this migration process, one key setting you must define is the data retention period — the amount of time migration-related data is kept in the system before it is automatically deleted.
What Is the Data Retention Period
The data retention period determines how long data stored in the staging tables and project logs remain in the system after a migration project finishes. When the retention period expires, the system removes this temporary data to free up space and maintain database performance.
Keeping migration data indefinitely is unnecessary and can affect system efficiency. Setting the right retention period ensures that you retain essential audit information for the required time while keeping your database lean.
When to Specify the Data Retention Period
You specify the data retention period when creating a new migration project in the SAP S/4HANA Migration Cockpit. During project creation, you define several important parameters such as:
- Project name and description
- Migration approach (File upload or Staging tables)
- Mass Transfer ID
- Data retention period (in days)
In the “Migrate Your Data – Migration Cockpit” app:
- Choose Create Project.
- Fill in project details.
- In the Retention Period (in Days) field, enter how long the data should remain after migration completion.
- Save and continue with migration object selection and template setup.
This is the only stage when the system allows you to define the retention period for that specific project.
Why Setting the Retention Period Matters
Database efficiency: Large volumes of staging and log data can occupy significant storage space. Defining a retention period ensures that old data is cleaned up automatically.
Performance optimization: Periodic deletion of expired data helps maintain high performance of staging tables and indexes.
Compliance and auditing: Some organizations are required to retain migration logs for a specific duration (for example, 30 or 90 days) for internal or external audits.
Automated housekeeping: After the retention period, the system automatically deletes old data, reducing manual maintenance.
Also Read: SAP S/4HANA Migration Cockpit step by step process
Recommended Retention Periods
- Sandbox or test migrations: 7–14 days is sufficient since these projects are for validation only.
- Production or cut-over migrations: 30–90 days provides enough time for reconciliation, verification, and audit review.
- Very large projects: Monitor database space regularly and adjust the retention period according to storage usage.
Always document the retention policy in your migration plan and approval checklist.
What Happens After the Retention Period Ends
Once the retention period expires, SAP automatically deletes:
- All staging table records belonging to the project
- Job logs and execution details
- Temporary transformation results and audit entries
This cleanup runs as a background task, helping keep the system optimized without manual intervention.
Also Read: How to connect sap bw to snowflake python
Summary
You specify the data retention period during the creation of a migration project in the SAP S/4HANA Migration Cockpit. It defines how long migration data and logs remain available before the system deletes them automatically. Selecting an appropriate period maintains a balance between data retention for auditing and system performance.
In short: set shorter periods for test migrations and longer periods for production environments to maintain control, compliance, and efficiency throughout your SAP S/4HANA migration process.