Document data migration in SAP

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 understandFirst 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 
KGS User Story from - Armin Rehm
“Thanks to the KGS solution, we are working with state-of-the-art technology. Document access is very fast, which is quite a feat, considering that the system has to deal with 500 million documents. What our internal departments needed was a solution that could ensure that any front-end customer consultant taking a call has the required document on screen within a second.”
Armin Rehm, Service Manager DMS / EnBW Group

“Traditional archive systems generally require a dedicated database server. This generates additional administrative costs, which we can avoid with KGS ContentServer4Storage, because this tool directly accesses the SAP tables.”

Hagen Hoss, Platforms and Storage Solutions Architect / Coats

“KGS ContentServer4Storage is able to map ERP-related
document archiving processes much leaner,
more efficiently and in a more integrated manner than
any other archive operated in an SAP environment.”

Philip von Melle, Managing Director / Globetrotter

„Thanks to the KGS corporate product
license, each SAP workstation automatically
also serves as an archive workstation. This
means that relicensing is a thing of the past.
The solution will thus have paid for itself in
only two years.“

Florian Beck, Head Application Management / Knauf

“What makes our approach so fundamentally different from other ECM solutions is the lean architecture of the KGS application. We now only need a single server that even operates without a database. The Windows file system acts as the physical storage, so no proprietary storage solution is required.”

Peter Pollich, Head of Infrastructure & Application Management / Rhein Chemie

“The KGS migration software truly made a seamless transition from the old to the new archive. Our users did not even notice that a migration was taking place; there were hardly any disruptions.”

Oliver Fischer, Head of IT / Loewe

„When sounding out the market, KGS was the only provider whose solution met our special requirements within this unique system landscape.“

Volker Blum, Head of SAP system basic support unit / Trumpf
“The simple customizing process delivered by KGS ZADOC makes it easy to define attributes to set up different document types.”
Andreas Lupfer, Team Leader SAP Application Support / Röchling Automotive

„With the KGS archive running in the background, we have been able to carry out a complete SAP transformation within the company, from SAP ECC through MaxDB and SAP Suite on Hana, and finally, to S4/HANA. We didn‘t have to adapt anything in the archive throughout the whole process and were able to concentrate solely on the implementation of S4/HANA.“

Dr. Marco Lenck, Head of Group IT / Döhler GmbH

Contact Us!

Relevant Products