Migrating Manufacturing BOMs and Routing Data to New ERP Systems

How to Migrate Manufacturing BOMs and Routing Data to New ERP Systems

Migrating Bill of Materials (BOM) and routing data is the most critical phase of a manufacturing ERP implementation. These datasets define how products are built and how resources are consumed. Errors here directly impact production scheduling, inventory accuracy, and cost accounting. The recommended approach involves a rigorous data profiling phase, precise mapping of multi-level structures, and extensive validation in a staging environment before cutover. The primary risks to control are data loss, broken parent-child relationships in BOMs, incorrect operation sequences in routings, and integration failures with downstream systems like MES or WMS. Success depends on treating data migration not as a technical task, but as a business process validation exercise.

Phase 1: Data Profiling and Source Assessment

Before extracting data, you must understand the quality and structure of the source data. Legacy systems often contain orphaned BOM lines, duplicate routings, or obsolete work centers. Conduct a comprehensive data profiling exercise to identify these issues. Analyze the depth of BOM levels, the number of active versus inactive items, and the complexity of routing operations. Identify custom fields in the legacy system that do not have direct equivalents in the target ERP. This phase requires collaboration between IT and manufacturing operations to determine which data is truly necessary for go-live. Inactive or obsolete data should be archived rather than migrated to reduce complexity and improve performance.

Key Data Elements to Profile

• BOM Header: Item number, version, effective dates, and status.
• BOM Lines: Component item, quantity, scrap factor, and position number.
• Routing Header: Item number, version, and default work center.
• Routing Operations: Sequence number, work center, standard hours, and setup times.
• Work Centers: Capacity, cost rates, and calendar availability.

Phase 2: Data Mapping and Transformation Rules

Mapping defines how source fields translate to target fields. This is where many migrations fail due to subtle differences in data models. For BOMs, ensure that the parent-child relationship is preserved correctly. If the target ERP uses a different structure for multi-level BOMs, transformation logic must be written to reconstruct the hierarchy. For routings, map operation sequences to the target system's step structure. Pay close attention to units of measure, as mismatches can lead to catastrophic inventory errors. Define transformation rules for data cleansing, such as removing leading zeros from item numbers or standardizing work center codes. Document all mapping decisions in a data dictionary to ensure auditability and reproducibility.

Phase 3: Data Cleansing and Deduplication

Cleansing is essential to prevent garbage-in-garbage-out. Remove duplicate BOM versions where only one is active. Resolve conflicts where multiple routings exist for the same item without clear precedence. Standardize naming conventions for work centers and operations. Deduplicate material master records that may have been created multiple times in the legacy system. This phase should be iterative, with business users reviewing samples of cleansed data to confirm accuracy. Establish clear ownership for data issues; IT handles technical fixes, while operations managers decide on business logic conflicts. Document all changes made during cleansing to maintain a clear audit trail.

Phase 4: Trial Migrations and Validation

Perform multiple trial migrations in a staging environment that mirrors the production target system. The first trial focuses on technical success: did the data load without errors? Subsequent trials focus on business validation. Compare source and target data using reconciliation reports. Check for missing BOM lines, incorrect quantities, and broken routing sequences. Validate that production orders can be created and scheduled using the migrated data. Test edge cases, such as BOMs with deep hierarchies or routings with complex branching logic. Involve key users from production planning and shop floor operations to verify that the data supports their daily workflows. Defects found during trials must be triaged and fixed before the next trial.

Validation Checkpoints

• Record Count Reconciliation: Source vs. Target row counts.
• Structural Integrity: Verify all BOM parents have valid children.
• Routing Sequence: Ensure operations are in correct order.
• Cost Accuracy: Validate standard costs calculated from BOM and routing.
• Scheduling Test: Create test production orders and check capacity load.

Phase 5: Cutover Planning and Execution

Cutover is the final data load during the freeze window. Plan for minimal downtime by pre-staging all data and having transformation scripts ready. Define clear go/no-go criteria based on the results of the final trial migration. If critical defects remain, do not proceed. During cutover, execute the final data load, run validation scripts, and obtain sign-off from business stakeholders. Coordinate with integration teams to ensure that downstream systems are ready to receive the new data. Have a rollback plan in place, which typically involves restoring the legacy system from a backup taken before the freeze. Communication is critical; keep all stakeholders informed of progress and any delays.

Post-Migration Stabilization and Monitoring

After go-live, monitor the system closely for data-related issues. Track production order creation rates, inventory discrepancies, and scheduling errors. Establish a hypercare period where a dedicated team is available to resolve data issues quickly. Compare actual production consumption against BOM expectations to identify any remaining data gaps. Gather feedback from users and make necessary adjustments to BOMs or routings. Document lessons learned and update the data migration playbook for future projects. Stabilization is not complete until the system has run through a full production cycle without significant data-related interruptions.

Risk Management and Mitigation Strategies

The primary risk in BOM and routing migration is data integrity failure. Mitigate this by implementing strict validation rules and automated reconciliation checks. Another risk is user resistance due to unfamiliar data structures. Mitigate this by involving users early in the mapping and validation process. Technical risks include performance issues during large data loads. Mitigate this by optimizing database indexes and using batch processing. Ensure that all custom fields and integrations are tested thoroughly. Maintain a detailed rollback plan that has been tested in the staging environment. Regularly review the risk register and update mitigation strategies as the project progresses.

Conclusion

Migrating manufacturing BOMs and routing data is a complex but manageable process when approached with discipline and attention to detail. By following a structured methodology that includes profiling, mapping, cleansing, validation, and careful cutover planning, organizations can minimize risk and ensure a successful transition. The key to success is treating data migration as a business process, not just a technical task. Involve all stakeholders, validate data thoroughly, and maintain a clear audit trail. With the right preparation and execution, your new ERP system will provide accurate and reliable data for production planning and operations.