What makes a carve-out so technically complex?

Basically, there are many areas to consider. There are often multiple interfaces and cross-links to previous or subsequent systems that also need to be taken into account. In addition, proper data separation requires IT to be familiar with the relations and structures of the tables in the database. This requires a deep understanding of the database and tables. In addition, there are other issues, such as data protection, which must also be taken into account – the keyword being intended use.

What questions should be addressed before executing a carve-out?

1) What data needs to be carved out? 

2) Can this data be identified via a company code or client?

3) Which systems contain the data to be archived?

4) Which time period is relevant?

5) Are there individual developments within the system that would have to be taken into account?

6) Is there a need to anonymize or delete data prior to extraction due to DSGVO requirements?

7) Is there a specific timeline by when the extraction must be completed?

8) Should data be transferred to the new productive system?

Before starting the project, it is best to create a to-do list and use it to develop a project plan to better track progress.

How can AvenDATA support such a project?

We have been specializing in data archiving for over 15 years. This can be the case due to carve-outs as well as for reasons of complete system shutdown. A proven and standardized archiving process ensures successful project implementation. Approximately 180 specialists work daily on the implementation of global archiving projects with the highest understanding of database as well as database structures. The approach as well as the software is certified.

If you are looking for a company that understands the carve-out of company codes, clients or plants or similar, then you have come to the right place. Carve-out is quasi the little brother of the complete archiving. This means that the carve-out is very similar to complete archiving in terms of the procedure and technical processes. In this respect, it was not surprising that after a few archiving and shutdowns of legacy systems, customers approached us with the request to also perform corresponding carve-outs. Carve-outs from existing systems such as SAP, Oracle, Navision require a very deep understanding of database structures and database models. A carve-out is always a technical challenge, which AvenDATA has been facing for many years. The backbone here is our experienced SQL Developer department consisting of about 50 people who deal exclusively with database models and their challenges on a daily basis.