Skip to content
ERP Migration

Migrating Complex Manufacturing BOMs and Routing Data to Modern ERPs

A practical guide for CIOs and ERP consultants on migrating complex Bill of Materials (BOM) and routing data. Covers data profiling, transformation logic, validation strategies, and risk mitigation for manufacturing ERP upgrades.

9 min readSysGenPro Editorial
Migrating Complex Manufacturing BOMs and Routing Data to Modern ERPs

How to Migrate Complex Manufacturing BOMs and Routing Data to Modern ERPs

Migrating complex Bill of Materials (BOM) and routing data to modern ERPs requires a structured approach focused on data profiling, rigorous transformation logic, and multi-layered validation. The primary risk is not the technical transfer of records, but the loss of logical integrity in multi-level structures, effective dating, and operation sequences. If BOM hierarchies are flattened incorrectly or routing times are misaligned, production planning, costing, and shop floor execution will fail. The recommended approach involves a phased migration: first, profile and cleanse legacy data to establish a single source of truth; second, map and transform data using automated ETL tools with manual oversight for complex logic; third, execute trial migrations in a staging environment to reconcile records; and finally, perform a cutover with strict go/no-go criteria. Success depends on treating BOM and routing data as critical business assets, not just database tables, ensuring that every component and operation retains its functional context in the new system.

Phase 1: Data Profiling and Legacy Assessment

Before any data is moved, you must understand the state of your legacy manufacturing data. Complex BOMs often contain historical revisions, phantom items, and inconsistent effective dates that do not align with the new ERP's data model. Start by extracting a full snapshot of BOMs, routings, work centers, and item masters from the legacy system. Use data profiling tools to identify anomalies such as circular references, missing components, orphaned operations, and duplicate items. For routing data, analyze the distribution of setup times, run times, and scrap rates to identify outliers that may indicate data entry errors or obsolete processes. This phase is critical because migrating dirty data amplifies errors in the new system. Assign data ownership to specific business units, such as Engineering for BOM structure and Production for routing times, to ensure accountability for data quality decisions.

Identifying Structural Complexities

Complex manufacturing environments often use multi-level BOMs with deep hierarchies, which can stress the performance and logic of the new ERP. Identify items with more than five levels of depth, as these may require special handling or restructuring. Look for phantom items, which are used for grouping but not stocked; ensure the new ERP supports this concept or plan to replace them with sub-assemblies. Also, review effective dating logic. Legacy systems may use simple start/end dates, while modern ERPs may support versioned BOMs with complex effective date ranges. Mapping these differences early prevents production orders from pulling the wrong component versions during cutover.

Phase 2: Data Cleansing and Standardization

Data cleansing is the most labor-intensive part of the migration. The goal is to create a clean, standardized dataset that matches the target ERP's requirements. Deduplicate items and BOMs by merging records that represent the same physical product. Standardize units of measure, as mismatches between legacy and new systems can lead to catastrophic inventory errors. For routing data, standardize work center names and codes to align with the new system's master data. Remove obsolete BOM revisions and routings that are no longer in use, but archive them for audit purposes. This step requires close collaboration between IT and business stakeholders. IT handles the technical cleansing, while business users validate that the remaining data reflects current production reality. Document all changes made during cleansing to maintain an audit trail.

Handling Effective Dates and Revisions

Effective dating is a common source of migration errors. In the legacy system, a BOM might have a single 'current' version. In the new ERP, you may need to migrate multiple versions with specific effective dates to support historical costing and future production. Decide on a strategy: migrate only the current active BOMs and routings, or migrate a history of versions. If migrating history, ensure that the effective dates do not overlap incorrectly. For routing data, verify that operation sequences are preserved. A missing operation or a swapped sequence can break the production schedule. Use automated scripts to check for continuity in operation numbers and flag any gaps for manual review.

Phase 3: Mapping and Transformation Logic

Data mapping defines how fields from the legacy system correspond to fields in the new ERP. For BOMs, map parent items, component items, quantities, and scrap rates. For routings, map operations, work centers, setup times, run times, and labor rates. Transformation logic handles data that does not map one-to-one. For example, if the legacy system stores routing times in minutes and the new ERP requires hours, the transformation logic must convert the units. If the legacy system uses a single field for 'total time' and the new ERP requires separate 'setup' and 'run' times, you must split the data based on business rules. Use ETL (Extract, Transform, Load) tools to automate this process, but include manual checkpoints for complex transformations. Document all mapping rules and transformation logic in a data dictionary to ensure transparency and reproducibility.

Data ElementLegacy FieldTarget FieldTransformation RuleRisk Level
BOM Component QuantityCOMP_QTYCOMPONENT_QTYDirect MapLow
Routing Setup TimeTOTAL_TIMESETUP_TIMESplit based on operation typeHigh
Work Center CodeWC_IDWORK_CENTER_IDLookup table mappingMedium
BOM Effective DateSTART_DATEEFFECTIVE_FROMDate format conversionMedium
Scrap RateSCRAP_PCTSCRAP_PERCENTDirect MapLow

Phase 4: Trial Migrations and Validation

Never perform a production migration without successful trial migrations in a staging environment. Load the transformed data into a replica of the new ERP and run validation scripts. Check for referential integrity: every BOM component must exist in the item master, and every routing operation must reference a valid work center. Validate the structure: ensure that multi-level BOMs are correctly nested and that there are no circular references. For routing data, verify that the total time for a product matches the sum of its operations. Use reconciliation reports to compare record counts and key values between the legacy and new systems. Any discrepancies must be investigated and resolved before proceeding. This phase may require multiple iterations. Each trial migration should be documented, with a log of errors found and fixes applied.

Business Process Validation

Technical validation is not enough. You must validate that the migrated data supports business processes. Create test production orders for a sample of complex products. Run Material Requirements Planning (MRP) to see if the system can calculate the correct component requirements. Check if the production schedule is generated correctly based on the migrated routing times. Involve production planners and shop floor supervisors in this testing. They can identify logical errors that automated scripts might miss, such as a routing that is technically valid but operationally impossible. This user acceptance testing (UAT) is critical for gaining confidence in the migrated data.

Phase 5: Cutover and Deployment

The cutover is the final migration of data from the legacy system to the new ERP. Plan a freeze window where no changes are made to BOMs or routings in the legacy system. Perform a final delta load to capture any changes made since the last trial migration. Execute the migration scripts and load the data into the production environment. Immediately after the load, run the same validation scripts used in the trial migrations. Compare the results to ensure consistency. If any critical errors are found, trigger the rollback plan. The rollback plan should involve restoring the legacy system to its pre-cutover state and delaying the go-live. Do not attempt to fix critical data errors in the new system during the cutover window; it is safer to roll back and fix the source data.

Post-Migration Stabilization and Monitoring

After go-live, monitor the new ERP closely for the first few weeks. Track production orders for errors in component picking and routing execution. Monitor MRP runs for unexpected shortages or excesses, which may indicate BOM errors. Set up alerts for data quality issues, such as new BOMs being created with missing components. Provide support to users who encounter issues with production planning or shop floor execution. Collect feedback from production teams and make adjustments to the data or processes as needed. This stabilization phase is where the true value of the migration is realized. It allows you to fine-tune the data and processes to ensure long-term operational continuity.

  • Monitor MRP results daily for the first two weeks.
  • Track production order completion rates for complex products.
  • Review error logs for data integrity issues.
  • Hold daily stand-ups with production and IT teams.
  • Document any data corrections made post-go-live.

Risk Management and Rollback Strategies

Risk management is essential for a successful migration. The primary risks are data loss, broken BOM structures, and incorrect routing times. Mitigate these risks by maintaining verified backups of the legacy system and the new ERP before cutover. Test the restore process to ensure that backups are valid. Define clear go/no-go criteria based on the results of the final trial migration. If more than a certain percentage of records fail validation, do not proceed with the cutover. Have a documented rollback plan that outlines the steps to revert to the legacy system. This plan should include communication protocols, data restoration procedures, and a timeline for resuming operations. By preparing for failure, you increase the likelihood of success.

Conclusion

Migrating complex manufacturing BOMs and routing data is a critical task that requires careful planning, rigorous validation, and close collaboration between IT and business stakeholders. By following a phased approach that includes data profiling, cleansing, mapping, trial migrations, and post-migration monitoring, you can minimize risks and ensure a smooth transition to a modern ERP. The key is to treat data as a business asset, not just a technical artifact. Invest time in understanding the data, validating the transformations, and testing the business processes. This investment will pay off in the form of accurate production planning, reliable costing, and efficient shop floor execution. As you proceed with your migration, remember that the goal is not just to move data, but to improve the quality and usability of your manufacturing master data.

Written by
SysGenPro Editorial

SysGenPro Editorial

Platform & solutions team

Practical guidance on ERP, AI automation, cloud deployment and enterprise transformation from the SysGenPro team.

Share this article

Frequently asked questions

Common questions on this topic. Talk to our team for anything specific to your business.

01What are the biggest risks when migrating BOM data?

The biggest risks are structural errors in multi-level BOMs, incorrect effective dating, and loss of phantom item logic. These errors can lead to incorrect production planning and costing.

02How do you handle phantom items during ERP migration?

Phantom items should be mapped to the new ERP's equivalent concept, if available. If not, they may need to be replaced with sub-assemblies or removed, depending on the business process.

03What is the best way to validate routing data after migration?

Validate routing data by checking referential integrity, operation sequences, and total times. Run test production orders to ensure the system can schedule operations correctly.

04How long does it take to migrate complex manufacturing data?

The timeline depends on the complexity of the data and the number of products. It can range from several weeks to several months, including profiling, cleansing, and validation.

05Should we clean data before or during the migration?

Data should be cleaned before the migration. Migrating dirty data amplifies errors and makes validation more difficult. Cleansing should be done in the legacy system or in a staging environment.

06How do we handle version control for BOMs in a new ERP?

Decide whether to migrate only current BOMs or a history of versions. If migrating history, ensure that effective dates are correctly mapped to the new ERP's versioning logic.

Continue learning
View all articles
Explore the platform

Where to go next

Browse the knowledge hub

See how SysGenPro fits your business

Discuss your workflows, modules and deployment options with our team.

Back to resources