Types of Data to Consider for a Migration

View all posts on Tools & Technology

Types of Data to Consider for a Migration

Data is a generic term that is used to describe all of the information that is required to drive the operational processes for the business.

Many migration programs have the myopic perspective that ALL data is required, when this simply is not the case. Trying to migrate every piece of information can actually hinder growth and performance after your "Go Live" by clogging the system with unnecessary data.

The types of data that should be considered for a migration are as follows:

  • Configuration Data provides the fundamental data upon which a system will operate. This data remains very static. It must be loaded into the development system through the IMG / Solution Manager, and then transported through the System Landscape to the QA and the Production environments. Examples of configuration data include: Country Codes, Units of Measure, Material Groups, Plants, Company Codes and Sales Organizations.
  • Core Master Data objects provide the foundation for subsequent loads of Supplementary Master Data, Transactional Data, and Historical Data. Examples of Core Master Data objects include: Bank Master, Vendor Master, Material Master, and Customer Master
  • Supplementary Master Data provides the data requirements that are used to drive the operational processes. Master data remains relatively unchanged (compared to transactional data) over time. As this data is static, it provides the foundation for other transactional / balance data to be loaded. Examples of Supplementary Master Data include Purchasing Information Records, Source Lists, Customer Master Information Records, and Customer Hierarchies
  • Transactional Data is information that has been created by business processes / transactions. This type of data is not static and changes on a day-to-day basis. Transactional data falls into one of two categories:
    • Open Transaction Data is transactional data that has not completed its business cycle, for example a service ticket that remains open with additional activities required prior to being closed
    • Closed Transaction Data is transactional data that has completed its business cycle and is subsequently used for information purposes only, for example a service ticket with all related activities completed and a ticket status of closed
  • Historical Data is data that has completed the business cycle and is used for some isolated processes (such as sales forecasting), reference and reporting purposes only. Historical data may be archived to preserve future access. Legacy system historical data is subject to the franchises policies and procedures regarding data retention.

When in the planning stages of a migration, it is important to fully understand the types of data that take the highest priority. This will help ensure a clean and scalable environment to support ongoing innovation and process improvement.