Any work related to the replacement of server or storage, data center migration, maintenance or upgrade, website consolidation and application migration always requires to migrate data. Data migration is “the process of transferring data between data storage systems, data format or computer systems”. This is a complex and lengthy process, consisting of several stages.
Typical problems that arise during migration:
- Data from different sources can contradict each other
- Manually prepared data requires reconciliation for purity and consistency
- Presence of data duplicates
- Lack of required analytics in legacy systems
- Necessity to monitor changes in legacy systems that arise during the period of data migration
Tool to simplify data migration
- Loading and consolidating of data from external sources into your own repository
- Validation of prepared data and their consistency based on configurable rules of any complexity
- Uploading of verified data in the required format (txt, xls, xlsx, etc.)
- Uploading of custom reports on data test results
- Save and edit validation rules and report templates for further use
- Providing analysts with a tool to verify and prepare data for loading into the target systems
MAGINFO has developed a tool that
- simplifies the data reconciliation process and data migration.
- allows to perform test migrations on real data stored in existing systems at the time of testing,
- tests migration results
- performs adjustment procedures for cleaning and normalizing the data according to migration results.
- has possibility of rapid data preparation ensuring execution of test migrations on real data without stopping the operation of existing legacy systems.
Preconfigured SAP validation templates
Currently, there are preconfigured templates (can be set up taking into account the specifics of the Customer) to prepare data when migration to SAP ERP and Oracle EBS:
- Material Master Record (MMR, including most angles)
- Customer/Vendor Master Record
- Sales contract
- Procurement contract
- Handbook of the parties (model TCA Oracle EBS)
Case 1. (Global Food and Beverage company)
Reference book of materials - spare parts
Each store had its own spare parts catalog, where the same items were taken into account in different ways, for example, the network cable in one warehouse was counted in coils of 100 meters, on others in coils of 50 meters, and in other cases - in meters.
If you leave everything as is, then when you migrate to SAP (similarly to Oracle) it will not be clear which of the items you need to replenish in the warehouse. The lack of a unified position in the system leads to the fact that it becomes impossible to plan the remains of materials in warehouses, when in the presence of several identical positions it is not clear how much the cable is in the warehouse, whether the time of replenishment has already come or is still enough. Ultimately, this leads to an unjustified increase in stock in the warehouse.
It is necessary to have a tool that will allow you to analyze the spare parts catalog, highlight the same ones, determine in which units the accounting is performed, select the basic unit of measure and ensure that the warehouse stock is loaded in all required units.
Case 2. (Major oil and chemical company)
List of customers
The company has several branches, where there was an established own accounting system. The same buyer could be present in the systems of branches with different own code.
If you keep the current approach in the transition to SAP, there is a risk that the same counterparty will be loaded several times to the new system. There is a probability of a situation where the counterparty should be allocated to a high risk group and all deliveries of this counterparty should be banned. Unfortunately, such a task can not be completely resolved because there are several duplicate counterparties in the system. As a consequence, this can lead to an increase in overdue accounts receivable.
When preparing data for migration, it is necessary to solve the problem of identifying duplicate clients, create on their basis only one record for each client and take into account these relationships when migrating contracts and other documents related to customers.