Legacy data migration is one of the most challenging and under-estimated components of enterprise system deployments. Razorleaf’s consulting team collectively has decades of experience in extraction, transformation, and loading (ETL) of legacy data for many, many types of business systems including PDM, PLM, MRP, ERP, CRM, and custom applications.
Legacy Data Migration Experience
The first question clients ask related to legacy data migration is inevitably, “have you worked with <insert system name here>?” Although this is far from the most critical question to ask related to ETL projects, it is certainly top-of-mind for most people, and Razorleaf has experience working with all of these systems, either as the source system or destination system in a migration or integration project:
- Windows and UNIX/LINUX file systems
- Oracle RDBMS, SQL Server, Interbase, and Access databases
- Enterprise PDM (Conisio) and PDMWorks Workgroup
- ENOVIA SmarTeam
- ENOVIA V6 and MatrixOne
- Autodesk Fusion Lifecycle
- Autodesk Vault
- Aras Innovator
- BlueCielo/Cyco Meridian and AutoManager
- Arena and BOM.com
- Agile PLM
- Infor SyteLine, Fourth Shift, VISUAL (Manufacturing), XA (MAPICS), LX (BPCS)
- Oracle Applications and Oracle E-Business Suite
Razorleaf’s Approach to Migrating Data
Razorleaf’s project managers, developers, and consultants have been cleaning, transforming, and migrating legacy data for years, and have developed an internal set of guidelines and techniques for legacy data migrations and ETL projects. The company’s long history in technical document management has provided unique expertise in migration of version history, CAD structures, and object relationships which are frequently misunderstood (and underestimated) concepts. Razorleaf’s approach includes steps to identify scope, assess data quality, define transformations, plan iteration and testing models, and document success criteria (via use cases, test matrices, etc.).
In many cases, Razorleaf proposes hybrid migration projects where the client cleans and migrates some data manually while Razorleaf cleans and migrates other data via automated tools. Specifications, sample data, use cases, and detailed logging figure prominently in Razorleaf’s approach to legacy data migration, ensuring top quality results and consistent data integrity.