Skip to main content

Data Conversion vs. Data Migration: What’s The Difference?

In the past I have worked as Migration lead and now I am working as conversion lead for one of the ERP implementation project. As having worked on both(migration/conversion) this is an effort to put forward the difference between migration and conversion.

The terms Data Conversion and data migration are still sometimes used interchangeably on the internet. However, they do mean different things. Data conversion is thetransformation of data from one format to another. It implies extracting data from the source, transforming it and loading the data to the target system based on a set of requirements.
Data Migration is the process of transferring data between silos, formats, or systems. Therefore, data conversion is only the first step in this complicated process. Except for data conversion, data migration includes data profiling, data cleansing, data validation, and the ongoing data quality assurance process in the target system.
Both terms are used as synonymous by many internet resources. I think the reason for that might be that there are very few situations when a company has to convert the data without migrating it.
What is the need of Migration/Conversion?
Migration/Conversion are required when we are upgrading to one version to another (e.g. Oracle Apps R11 to Oracle Apps R12) or moving data from some legacy system to Oracle Apps. There will be bulk  of data (sometimes millions or even more than that) that needs to be moved from one system to another  and  before moving the data it should be validated and only valid records should be entered into Oracle Apps.
If both the systems (Target and source) are not having same structure for data (Tables are not same/Table Structure is not same/The data is being stored in database is not same), it needs to be translated (e.g. upgrading from Oracle 11i to R12 where table structures are not same) then we say it as conversion (any kind of translation of data on Source data to make it suitable for Target system) otherwise migration. Reimplementation of same Oracle apps version is good example of Data Migration.

What is Conversion?
Conversion of data means translating the data to suite target system (data should be formatted according to target system) and then move the translated data using Interface Programs/APIs.
• Identify the data to be imported to new system (Business requirement).
• Extract into flat file/Staging table
• Translate/Convert/Format the data
• Load the data into Interface Table (using SQL* Loader/DB Link/Others) after validation (If loading the data using Interface) and then launch standard Interface concurrent program to load the data to Oracle Apps Base Tables
• If using API, fetch the data, validate it and then call API to import the data

Conversion can be complex because you need to have a complete understanding of the source you’re converting from, and then format you’re converting to. If you don’t, you run the risk of compromising your data and ruining its integrity during the conversion process.
Example: Conversion of data like suppliers, customers from Oracle ERP to Workday ERP.
What is Migration?
Migration of data means moving the data from one system to another using Interface Programs/APIs where both the systems have same structure of data.
Process of Migrating of data:
• Identify the data to be imported to new system (Business requirement).
• Extract the data into flat file/Staging table
• Load the data into Interface Table (using SQL* Loader/DB Link/Others) after validation (If loading the data using Interface)
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. 
Where data conversion deals with individual data fields, data migration is the process of moving and merging entire databases or programs. 
For example clients migrates data from multiple databases into a single database, or migrates data from one CRM/ERP system to another.
Data migration may appear simple at first glance, but just like data conversion, it’s actually pretty complex! It usually involves what’s called data mapping, a strategic process that maps data from one database to another by looking at where the data lives currently, and where it will live once it’s moved.
Before migrating data, you need to be sure that the data fields in your old database exist in the new database. You also have to understand how both programs handle different types of file formats, and whether or not any data fields will be merged during the process.
How conversion/Migration and interface differ?
There are good numbers of parameter on which they can be categorized. Take few of them:

Frequency 
• Conversions/Migration are a one-time event
• interfaces are ongoingOccurrence in the project timeline
• conversions/Migration executed before production
• interfaces executed during productionManner of execution• Conversions/Migration are batch
• Interfaces may be batch or real timeComplexity
• Conversion/Migration does have very complex, it’s totally depends upon the data mapping activity.
• Coordinating with other systems make interfaces more complex 
Maintenance
• Maintenance of interface is bit cost intensive task.
Labels:

Comments

Post a Comment

Popular posts from this blog

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...
1 comment
Read more

O2C Cycle with Accounting Entries

  ORDER    TO  CASH  PARTICULARS  DR  CR SPL NOTES ACCOUNT IS PULLED FROM Sales order entry No Accounting Sales Order Pick From Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup To Sub Inventory A/c 100 At Standard Cost(Staging) Sub-inventory Material A/c Setup Sales Order Issue COGS 100 It can be fetched from five places Master Item/Org/Order Type/Line Type/Shipping Params To Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup Transaction level Receivable A/c 120 Auto Accounting Tax A/c 10 Auto Accounting Freight A/c 10 Auto Accounting Revenue A/c 100 Auto Accounting Receipts Receipts with no remittance method Cash 100 Before application of the receipt Receipt class Unapplied A/c 100 Receipt class Unapplied A/c 100 After application of the receipt to the transaction Receipt class Receivables A/c 100 Receipt class Cash A/c 100 Receipt class Unidentified A/c 100 In case of receipt without customer...
Post a Comment
Read more

R12 Oracle E-Business Tax Configuration Guide

Applies to: Oracle E-Business Tax - Version: 12.0 to 12.2 Information in this document applies to any platform. Abstract R12 Oracle E-Business Tax Configuration Guide Document History R12 Oracle E-Business Tax Configuration 1. Tax Basic Tax Configuration Tax Definition: comprises the tax data that you set up for each tax regime and tax that your company or institution is subject to. The Tax Authority designates the regulations and rates that apply to the tax regime. Required Task List a) External Dependencies Create First Party: Legal Entity and Establishments Create Reporting and Collecting Tax Authorities b) Tax Configuration Create Tax Authorities Party Tax Profiles Create Tax Regimes Create First Party Legal Entity Party Tax Profile Create Tax Create Tax Status Create Tax Jurisdictions Tax Rate Responsibility: Tax Manager Path: Tax Managers -> Tax Managers -> Home Complete the following setup tasks: -Legal Entities and Establishments -Reporting and Collecting Tax Authorities ...
1 comment
Read more