Skip to content
ERP Migration

Migrating Manufacturing BOMs and Routing Data: Technical Considerations

A technical guide to migrating Bill of Materials and Routing data during ERP transitions, covering data profiling, transformation logic, validation, and risk mitigation strategies.

10 min readSysGenPro Editorial
Migrating Manufacturing BOMs and Routing Data: Technical Considerations

Migrating Manufacturing BOMs and Routing Data Requires Rigorous Data Profiling and Validation

Migrating Bill of Materials (BOM) and routing data is one of the most complex aspects of an ERP transition because these datasets directly drive production planning, scheduling, and cost accounting. The recommended approach involves a phased strategy: first, profile and cleanse source data to identify structural anomalies; second, map legacy fields to target ERP schemas with explicit transformation rules; third, execute trial migrations in a staging environment to validate integrity; and finally, perform end-to-end business process testing before cutover. The primary risks to control include broken BOM hierarchies, incorrect operation sequences, loss of version history, and mismatches between material masters and BOM components. Failure to address these risks can result in production stoppages, inaccurate cost calculations, and significant operational downtime. Unlike simple master data, BOMs and routings are relational and hierarchical, meaning a single error in a parent component can cascade through multiple work orders. Therefore, technical considerations must focus on data lineage, referential integrity, and comprehensive reconciliation checks.

Phase 1: Data Profiling and Source System Assessment

Before any data extraction begins, a thorough assessment of the source system is required. This involves analyzing the structure of existing BOMs and routings to understand their complexity, depth, and data quality. Key metrics to evaluate include the average number of levels in BOM hierarchies, the total count of active versus obsolete BOMs, and the frequency of routing changes. Data profiling tools should be used to identify null values, duplicate entries, and inconsistent formatting in critical fields such as component quantities, scrap factors, and operation times. For routing data, assess the number of operations per routing, the types of resources assigned, and the presence of conditional logic or alternative routings. This phase also requires identifying dependencies between BOMs and other master data, such as material masters, work centers, and cost centers. Understanding these dependencies is crucial for planning the migration sequence, as BOMs cannot be migrated until their referenced materials and resources exist in the target system.

Identifying Data Quality Issues

Common data quality issues in manufacturing environments include phantom items that are not properly flagged, components with zero quantities, and routings with missing operation sequences. These issues must be documented and resolved before migration. A data cleansing plan should be developed in collaboration with manufacturing engineers and production managers to determine which records are valid and which should be archived or corrected. For example, if a BOM contains a component that is no longer used in production, it should be removed or marked as obsolete in the source system. Similarly, routings that have not been used in the past 12 months may be candidates for archival rather than migration. This step reduces the volume of data to be migrated and minimizes the risk of introducing errors into the new system.

Phase 2: Data Mapping and Transformation Logic

Data mapping involves defining how each field in the source system corresponds to fields in the target ERP. This is not a one-to-one process for BOMs and routings, as the target system may have a different data model. For instance, a legacy system might store BOM components in a flat table, while the target ERP uses a hierarchical structure with parent-child relationships. Transformation logic must be developed to handle these structural differences. This includes calculating effective dates, converting units of measure, and mapping resource types to the target system's work center definitions. Special attention must be paid to version control. If the source system supports multiple versions of a BOM or routing, the migration strategy must define which versions to migrate. Typically, only the latest active version is migrated, but historical versions may be required for audit purposes. The transformation rules should be documented in a data mapping specification that is reviewed and approved by both IT and business stakeholders.

Handling Complex BOM Structures

Complex BOM structures, such as those with multiple levels of sub-assemblies, require careful handling to ensure that the hierarchy is preserved during migration. Transformation scripts must validate that all parent-child relationships are intact and that there are no circular references. Circular references, where a component is indirectly its own parent, will cause errors in most ERP systems and must be identified and resolved before migration. Additionally, the migration process must handle phantom items correctly. Phantom items are components that are not physically stocked but are used to group sub-assemblies. In the target system, phantom items may need to be flagged with a specific attribute to ensure they are not included in inventory counts or purchasing orders. Failure to map these attributes correctly can lead to inventory discrepancies and procurement errors.

Phase 3: Trial Migrations and Validation

Trial migrations are essential for validating the transformation logic and identifying potential issues before the final cutover. At least two to three trial migrations should be performed in a staging environment that mirrors the production target system. Each trial migration should be followed by a comprehensive validation process. This includes automated checks for referential integrity, such as ensuring that all BOM components reference valid material masters and that all routing operations reference valid work centers. Manual validation should also be performed by manufacturing engineers to verify that the migrated BOMs and routings match the expected production processes. For example, engineers should review a sample of migrated BOMs to ensure that component quantities, scrap factors, and effective dates are correct. They should also review routing data to ensure that operation sequences, standard times, and resource assignments are accurate. Any discrepancies found during validation must be documented and resolved by adjusting the transformation logic or correcting the source data.

Validation CheckDescriptionResponsible Role
Referential IntegrityVerify that all BOM components and routing resources exist in the target systemIT Data Engineer
Hierarchy IntegrityCheck for circular references and ensure parent-child relationships are correctIT Data Engineer
Quantity AccuracyCompare component quantities in source and target systems for a sample of BOMsManufacturing Engineer
Routing SequenceVerify that operation sequences and dependencies are preserved in the target systemProduction Planner
Effective DatesEnsure that BOM and routing effective dates are correctly mapped and appliedMaster Data Manager

Phase 4: Cutover Planning and Execution

The cutover phase involves the final migration of BOM and routing data to the production target system. This phase must be carefully planned to minimize downtime and ensure data consistency. A detailed cutover runbook should be developed, outlining the sequence of steps, responsible parties, and estimated durations for each task. The cutover window should be scheduled during a period of low production activity, such as a weekend or holiday, to reduce the impact on operations. Before the final migration, a data freeze should be implemented in the source system to prevent changes to BOMs and routings during the migration process. This ensures that the data being migrated is consistent and that no new changes are lost. The final migration should be performed using the same transformation logic that was validated in the trial migrations. After the migration, a final reconciliation check should be performed to ensure that the number of records migrated matches the number of records in the source system. Any discrepancies must be investigated and resolved before the system is declared live.

Rollback Strategy

A rollback strategy is essential in case the final migration fails or significant issues are discovered after cutover. The rollback plan should include steps to restore the target system to its pre-migration state and to revert any changes made to the source system. This may involve restoring database backups, re-applying data patches, or re-running the migration process with corrected transformation logic. The rollback plan should be tested during the trial migrations to ensure that it is feasible and that the estimated rollback time is acceptable. The go/no-go decision for the final cutover should be based on the results of the final validation checks and the readiness of the rollback plan. If any critical issues are identified, the cutover should be postponed until the issues are resolved.

Post-Migration Stabilization and Monitoring

After the final migration, the system enters a stabilization phase where close monitoring is required to identify and resolve any issues that may not have been detected during testing. This phase typically lasts for several weeks and involves daily reviews of production data, work orders, and inventory transactions. Manufacturing engineers and production planners should be available to provide support and to report any discrepancies in BOM or routing data. A defect triage process should be established to prioritize and resolve issues based on their impact on production. Common issues during this phase include incorrect component quantities, missing routing operations, and mismatches between BOMs and work orders. These issues should be resolved by correcting the data in the target system and, if necessary, updating the transformation logic for future migrations. The stabilization phase also involves user training and adoption support to ensure that users are comfortable with the new system and understand how to manage BOMs and routings in the target ERP.

  • Monitor production work orders for errors related to BOM or routing data
  • Review inventory transactions for discrepancies caused by incorrect BOM components
  • Provide daily support to manufacturing engineers and production planners
  • Track and resolve defects using a prioritized triage process
  • Conduct user training sessions to address common issues and best practices

Key Risks and Mitigation Strategies

The migration of BOM and routing data carries several key risks that must be actively managed. Data loss is a significant risk, particularly if the migration process fails or if data is corrupted during transformation. This risk can be mitigated by performing regular backups of the source and target systems and by testing the restore process. Broken customizations are another risk, as custom code or configurations in the source system may not be compatible with the target ERP. This risk can be mitigated by thoroughly testing customizations in the staging environment and by developing a plan to re-implement or replace customizations in the target system. Integration failures are also a concern, as BOM and routing data are often integrated with other systems, such as MES, PLM, and supply chain management systems. These integrations must be tested and validated during the migration process to ensure that data flows correctly between systems. Finally, user adoption is a critical risk, as users may resist the new system or make errors in managing BOMs and routings. This risk can be mitigated by providing comprehensive training and support and by involving users in the migration process from the beginning.

RiskImpactMitigation Strategy
Data LossLoss of BOM or routing data, leading to production stoppagesRegular backups, restore testing, and data validation
Broken CustomizationsCustom code or configurations fail in the target systemThorough testing in staging environment and re-implementation plan
Integration FailuresData flows between systems are disruptedEnd-to-end integration testing and validation
User AdoptionUsers make errors or resist the new systemComprehensive training, support, and user involvement
Performance RegressionsSystem performance degrades after migrationPerformance testing and optimization

Conclusion

Migrating manufacturing BOMs and routing data is a critical component of any ERP transition that requires careful planning, execution, and validation. By following a phased approach that includes data profiling, mapping, trial migrations, and post-migration stabilization, organizations can minimize risks and ensure a successful migration. The key to success is to involve manufacturing engineers and production planners in the process, to thoroughly test the transformation logic, and to establish a robust rollback strategy. By addressing the technical considerations outlined in this guide, organizations can protect their business data, maintain operational continuity, and improve the long-term maintainability of their ERP system.

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 common errors in BOM data migration?

Common errors include broken hierarchies, incorrect component quantities, missing effective dates, and circular references. These errors can lead to production stoppages and inventory discrepancies.

02How do you validate routing data after migration?

Routing data is validated by checking operation sequences, resource assignments, and standard times. Manual review by manufacturing engineers is essential to ensure that the routing matches the actual production process.

03Can BOMs be migrated automatically in ERP upgrades?

While some ERP systems offer automatic migration tools, BOMs often require manual intervention due to structural differences and data quality issues. A combination of automated tools and manual validation is recommended.

04What is the best way to handle phantom items in BOM migration?

Phantom items should be flagged with a specific attribute in the target system to ensure they are not included in inventory counts or purchasing orders. This attribute must be correctly mapped during the migration process.

05How does routing data affect production scheduling in new ERP?

Routing data defines the sequence of operations and the resources required for production. Incorrect routing data can lead to scheduling errors, resource conflicts, and production delays.

06What tools are used for BOM data transformation?

Data transformation tools such as ETL (Extract, Transform, Load) tools, SQL scripts, and custom programming are used to transform BOM data from the source system to the target system.

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