There are many reasons for migrating data into an SAP environment: Merging of companies, realignment and streamlining of the IT landscape, moves to reduce running costs. A company may even want to focus on the archiving functions required for SAP and introduce a more streamlined archiving solution.
Requirements from an administrative and user perspective:
When carrying out a migration the following generally applies:
- All documents and data should remain accessible, even during the archive migration process
- As far as possible, the migration should be automated
- Comprehensive evidence must be provided that the migration has been carried out full
- It should not be necessary to make modifications to any applications during an archive system migration, especially within a productive environment
- An archive system replacement must be clear for the user to understand. First of all, it’s important to establish whether the migration will take place within or outside of the SAP system. As SAP can only access different archiving systems via different content repositories, SAP-side migrations always involve copying from one content repository to another before clearing the link tables. Overall, the clear disadvantage of this approach is that the necessary procedures in a productive SAP landscape pose significant risks and require highly complex change management in this respect, which is often an insurmountable barrier, particularly for large companies and corporations.SAP-side migrations therefore only make sense if adjustments to the archive contents are required in addition to the migration itself.You can get further information in our Whitepaper