Connected business operations. Flexible deployment.
A practical guide for CIOs and ERP consultants on migrating complex BOM and routing data. Covers profiling, mapping, validation, and risk mitigation to ensure production continuity.
Manufacturing data migration, specifically the transfer of Bill of Materials (BOM) and Routing data, is the most complex aspect of any ERP implementation. Unlike financial data, manufacturing data is highly structural, hierarchical, and interdependent. A single error in a BOM level or a missing operation in a routing can halt production, cause material shortages, or lead to significant financial loss. The recommended approach is a phased, validation-heavy process that prioritizes data cleansing and structural mapping over simple extraction and loading. The primary risks to control are data integrity loss, broken dependencies between materials and work centers, and production downtime during cutover. Success depends on rigorous profiling, clear ownership of data quality, and comprehensive reconciliation testing in a representative staging environment.
Before any data is moved, you must understand the current state of your manufacturing data. This phase involves extracting a sample of BOMs and routings from the legacy system and analyzing them for structure, completeness, and anomalies. BOMs are hierarchical structures that define the components required to build a product. Routings define the sequence of operations, work centers, and labor/machine times required to produce that product. These two datasets are tightly coupled; a routing references specific operations that may consume specific components from the BOM.
You must map the dependencies between the BOM, Routing, Material Master, and Work Center data. For example, a routing operation might reference a specific work center that has capacity constraints. If the work center data is not migrated correctly, the routing becomes invalid. Similarly, a BOM component might have a specific version or revision that must match the material master. Failure to identify these dependencies leads to orphaned records in the new system, which cannot be used for production planning.
Legacy systems often contain obsolete BOMs, duplicate routings, or missing standard times. During profiling, identify records that are no longer in use. Migrating obsolete data increases the complexity of the new system and confuses users. Establish criteria for what constitutes 'active' manufacturing data. This might include BOMs with recent production orders or routings used in the last 12 months. This decision requires input from production managers and planners, not just IT.
Data cleansing is the most labor-intensive part of the migration. It involves correcting errors, standardizing formats, and removing duplicates. This process must be owned by business users, not IT. IT can provide tools and reports, but business users must make decisions about which data is correct. For BOMs, this means verifying component quantities, units of measure, and scrap factors. For routings, it means confirming operation sequences, standard times, and work center assignments.
Once data is cleansed, you must define how it will be transformed from the legacy format to the new ERP format. This involves creating mapping tables that translate legacy fields to new ERP fields. For example, a legacy 'Part Number' might map to the new ERP's 'Material Code'. A legacy 'Operation Sequence' might map to the new ERP's 'Operation Number'. Transformation rules must handle complex logic, such as converting time units or calculating derived fields.
| Legacy Field | New ERP Field | Transformation Rule | Validation Check |
|---|---|---|---|
| Part_No | Material_Code | Direct Map | Must exist in Material Master |
| Comp_Qty | Component_Quantity | Convert to Base Unit | Must be > 0 |
| Op_Seq | Operation_Number | Multiply by 10 | Must be unique per Routing |
| WC_Code | Work_Center_ID | Lookup Table | Must exist in Work Center Master |
| Std_Time | Standard_Time | Convert to Minutes | Must be > 0 |
Never attempt a production migration without multiple trial migrations in a staging environment. The staging environment must be a replica of the production environment, including hardware performance and data volume. During trial migrations, load the cleansed data into the new ERP and run reconciliation reports. These reports compare the source data with the target data to identify discrepancies.
Key reconciliation metrics include the number of BOMs loaded, the number of components per BOM, the number of routings loaded, and the number of operations per routing. Any discrepancy must be investigated and resolved before the next trial. Common issues include missing parent-child relationships, invalid work center references, and data type mismatches. Document all issues and their resolutions to create a knowledge base for the final cutover.
After technical reconciliation, business users must perform UAT. Planners and production managers should create test production orders using the migrated BOMs and routings. They should verify that material requirements planning (MRP) runs correctly, that production orders are generated with the right components, and that backflushing works as expected. UAT is critical for catching logical errors that technical checks might miss.
Cutover is the final step where data is moved from the legacy system to the new ERP in production. This must be planned with extreme precision. Define a freeze window where no changes are made to the legacy system. Perform a final data extraction, transformation, and load. Verify the data in the new system using the same reconciliation reports used in trial migrations. Only after successful verification should the new system be declared live.
After go-live, the migration is not complete. The first few weeks are critical for stabilization. Monitor production orders for errors, such as missing components or invalid work centers. Provide hypercare support to users who may encounter issues. Track key performance indicators (KPIs) such as production order cycle time, material availability, and planning accuracy. Compare these KPIs with pre-migration baselines to identify any regressions.
Continuously refine the data migration process based on lessons learned. Document any issues and their resolutions to improve future migrations. Ensure that data governance processes are in place to maintain data quality in the new ERP. This includes regular audits of BOMs and routings, clear ownership of data updates, and automated checks for data integrity. By following this structured approach, you can minimize risk and ensure a successful manufacturing data migration.
Common questions on this topic. Talk to our team for anything specific to your business.
Data cleansing and validation. Migrating dirty data leads to production errors. Ensure all BOMs are accurate, complete, and free of obsolete components before loading them into the new ERP.
Use a hierarchical loading strategy. Load parent items first, then child items, ensuring that all parent-child relationships are preserved. Validate the structure after loading to ensure no levels are missing.
Common risks include missing work center references, incorrect operation sequences, and invalid standard times. These can lead to production delays and inaccurate cost calculations.
The duration depends on the complexity of the data and the size of the organization. It can range from several weeks to several months. Profiling and cleansing often take the longest.
Yes, absolutely. Migrating uncleaned data will result in a new system with the same problems as the old one. Cleansing is essential for data integrity and user adoption.
Use reconciliation reports to compare source and target data. Additionally, perform User Acceptance Testing (UAT) by creating test production orders and verifying that MRP runs correctly.
Learn how to modernize ERP for professional services firms to connect project operations with financial reporting, reduce manual work, and improve executive visibility.
A practical guide to migrating vendor and customer data during ERP transitions, focusing on data profiling, mapping, deduplication, and reconciliation to prevent business disruption.
Learn how to design retail ERP reporting structures that unify data across channels and regions, enabling faster, data-driven decisions for finance, operations, and supply chain leaders.
Discuss your workflows, modules and deployment options with our team.
Back to resources