EN 
DE 
Database migration in SAP
Migration from legacy databases into the leading SAP system
The replacement of legacy applications, whether due to a lack of acceptance of the existing license models or as a strategic decision, presents many organizations with major challenges. Here, it is important to define the right document type concepts and data models in advance and to use them to derive the digital processes in the SAP system to which the transferred information from the legacy system can be assigned.
The challenge may seem daunting, but with the right experts on your side and the appropriate migration frameworks in place, you can avoid lost productivity and protect your investment for the long term.
The most important questions and answers on the subject
1. is a direct SAP integration of sensitive "document-based" business processes fully possible without losses?
Yes, numerous implementation projects in various industries have shown that the requirements of an isolated solution can usually be mapped much more simply in the SAP system.
2) How important is a good requirement-specific process model when replacing legacy databases?
Extremely important, because only with the correct analysis of existing data and processes can the implementation be successfully planned and realized. Data, including keywording and metadata, must be imported into the new target structure of the SAP solution in a controlled, sequential and rule-based manner, taking into account all dependencies.
3. What are some of the challenges to be considered?
On the user side of the business departments, there are often concerns because existing legacy databases often work well, even if they are not necessarily up to date. Here, the interests of the IT department do not necessarily coincide with the interests of a business department. These challenges should not be underestimated from the outset and should be taken into account when proceeding.
Examples from the field: Migration of Lotus Notes applications into SAP! Learn more
