New Century and Integrity Plus Blog

Data Conversion versus Data Migration. What’s the Difference?

Posted by Shelly on Jun 15, 2016 1:31:29 PM

Data conversion and data migration can be quite confusing, and many people don’t understand the difference between the two. What are they? Are they different? Why are they important? 

This week’s blog will try to clear up some of that confusion and explain the difference between the two...yes, there is a difference.

Conversion vs. Migration: The difference is clear...

Data Migration: Is the transferring of data from one system to another.

When to use:

  • Update PODS model from 3.2 to 6.0
  • Switch from UPDM to PODS data model
  • Newly acquired pipeline data

Data Conversion: Is the transformation (or translation) of data from one format to another. Data is extracted from a source, it is then transformed and loaded to another system. The extraction is based on a specified set of requirements.

When to use:

  • Legacy data stored in paper files, spreadsheets or CAD files
  • Gather information from survey notebooks, as-built alignment sheets, or plant maps
  • Convert job books such as hydrotests or FLC reports
  • Newly acquired pipeline data

Who’s Involved in These Processes?

Data Technician

What they do:

  • Capture, convert and load pipeline data
  • Compare converted data with source documents

GIS Technician

What they do:

  • Analyze spatial and technical data
  • Create databases
  • Create and manage feature classes and spatial data

 

Conversion Process

A time frame for this process depends on the size of the pipeline(s) data provided. Here is a general process a typical conversion would follow.

  1. Identify Data Source(s): Review where the data is coming from and what information might be missing or inconsistent.

  2. Identify Data Destination(s): Create and review what the appropriate database(s) or system(s) the data will be transferred to will be. Define the data requirements and ensure the needed data can be properly translated and converted. 

  3. Data Load and Review: Review and test the data being loaded into the new database or system for accuracy. Once the data has been validated it can be loaded and put into production.


Migration Process

The migration process is very detailed and can take months to complete. Here is a general process a typical data migration would follow.

  1. Database Review: Review of the database and a review of the current implementation is conducted.

  2. Data Mapping: Thoroughly review the tables and data in the database to find unique tables and columns, as well as potential data discrepancies or inconsistencies. It’s important to track which tables the data currently resides in and where the data will be migrated to using data mapping.

  3. Migration: Once the mapping is complete, the migrated data can be transferred from the original database to the new database that can be tested and put into production. 



Keep up with current industry changes by migrating to PODS 6.0. PODS 6.0 offers more flexibility and better prepares your data to implement PODS for APR if desired. We have a dedicated migration team setup ready to help you!

Topics: Data Management, PODS, data, conversion, migration

Subscribe to Email Updates

Recent Posts

Posts by Topic

see all

Follow Us