Legacy System / Legacy Data Migration Services





What is a legacy system data migration?

A legacy system data migration is the process that is required to move data that was stored in a legacy system, out of that system and accurately imported or published into a new system. The steps required to perform a legacy data migration usually consists of:

  1. Understanding the legacy system and its data
  2. Analyzing the data via queries, reports, profiling, etc
  3. Gathering the business rules and requirements for handling and mapping the data to the new system's fields and functionality
  4. Developing the code / solution
  5. Testing the solution
  6. Feedback cycle to fix and/or make improvements where necessary
  7. Executing and/or Deploying the solution to migrate the data into the new system
  8. Support Period

Who needs a legacy system data migration?

A legacy system data migration is typically required whenever a legacy system that contains data is upgraded to a newer system, and when either the data is not so simple and consistent to work with, or whenever the newer system does not have any simple methods for automatically importing the data from the legacy system directly into the newer system. Examples of situations or projects where a legacy data migration might be required are:

  • When upgrading to a new Enterprise Resource Planning System (ERP)
  • When upgrading to a new Product Data Management System (PDM)
  • When upgrading to a new Product Lifecycle Management System (PLM)
  • When upgrading to a new Asset Management System (AMS)
  • When upgrading to a new Dealer Management System (DMS)
  • When upgrading to a new Financial Records System
  • When upgrading to a new eDiscovery System
  • When upgrading to a new Web System
  • When upgrading to a new Backend System
  • Purchasing a new system, but no legacy system exists. Gathering and ingesting all the data and preparing it for import/publishing into the new system is another case.

Examples of legacy system data migrations

Below are just a few examples of legacy system data migrations that we have executed for our clients across the world:

Client's Industry Client's Objective Our Service Delivery / Solution
Original Equipment Manufacturer (OEM) Our client was a large OEM company using a legacy system called LinkOne. All of their Parts Catalogs were initially created and published in the legacy LinkOne system. The client purchased a subscription to a new Software as a Service (SaaS) platform that had lots of new and improved features, including making all of their parts catalogs and parts available online and accessible across their distribution and dealer networks. The objective was to accurately gather all of the legacy content, and successfully migrate it into the new system. One of the key challenges in this legacy system data migration was that the legacy system did not have a backend database; all of the content was stored in folders on a file system. This produces a uniqueness challenge, whereby assembly files can exist in different folders, with the exact same filename, but yet the assembly content could actually be different; eg, a different version or revision of the assembly. To clarify, /some/folder/1101.ldf could be entirely different from /another/folders/1101.ldf, even though they shared the same filename in different directories. To solve this, we used a special hashing algorithm to hash the contents of each file, and to determine when an assembly was actually unique. The end result was an accurate migration of unique content into the new system, without extra fluff or duplication.

In total, we migrated:
  • 100,000+ List Definition Files
  • 40,000+ unique assemblies
  • 50,000+ unique engineering diagrams/images
Drilling Equipment Supplier (Oil/Gas) Our client is one of the world's leading provides of drilling services, equipment and performance tooling for mining and drilling companies. Their after market parts manuals had been created and published in a legacy system named Catbase. They too purchased a new software solution for their after market parts catalogs, and their objective was to extract all of their existing content, and have it successfully migrated into their new online system. A challenge in this project was trying to accurately extract the data from the legacy system. The developer of the Catbase program implemented their own type of 'encryption' algorithm to make migrating data out of the system difficult. However, it turns out the files were not truly encrypted; instead, it was more an 'encrypted by obscurity' method. Once we discovered a method for accurately extracting their data, we were able to successfully migrate all of their parts catalogs into their new system.

In total, we migrated:
  • 1,000+ technical and parts manuals
  • 10,000+ unique engineering assemblies
  • 40,000+ unique engineering parts


Inquire about a legacy system data migration

If you or your company would like to inquire about or request a legacy system or legacy data migration, please contact us or use our free consultation form page to request a free consultation with one of our Lead Solutions Architects.