Connected business operations. Flexible deployment.
A practical guide to managing BOM and routing data migration during ERP upgrades, covering data profiling, structural mapping, validation, and risk mitigation for manufacturing operations.
Manufacturing Bill of Materials (BOM) and routing migration during ERP upgrades presents significant risks due to the complex hierarchical nature of production data. The recommended approach involves rigorous data profiling, detailed structural mapping, and multi-stage validation to ensure that component relationships and operation sequences remain intact. Failure to address these challenges can lead to production halts, inaccurate costing, and supply chain disruptions. Key risks to control include data loss during transformation, broken dependencies between BOM levels, and misaligned routing steps that affect work center scheduling. By treating BOM and routing data as critical business assets rather than simple records, organizations can maintain operational continuity and protect long-term ERP maintainability.
BOMs and routings are not flat datasets; they are deeply interconnected structures. A BOM defines the parent-child relationships between finished goods and components, often spanning multiple levels. Routings define the sequence of operations, work centers, and labor or machine times required to produce an item. In an ERP upgrade, the schema for these objects may change, requiring careful mapping of fields such as component quantities, scrap factors, and operation sequences. Unlike simple master data, errors in BOM or routing data propagate through production planning, material requirements planning (MRP), and costing modules. Therefore, the migration strategy must account for the structural integrity of these datasets, not just the presence of individual records.
BOM hierarchies can be multi-level, with sub-assemblies containing their own components. During migration, the system must preserve these parent-child links. If a sub-assembly is migrated before its parent, or if the link is broken, the BOM becomes invalid. Similarly, routings depend on work centers and resources. If a work center is renamed or restructured in the target ERP, the routing must be updated to reference the new identifier. These dependencies require a careful sequencing of data loads, often starting with master data (materials, work centers) before loading BOMs and routings.
Many manufacturing environments use BOM and routing variants to handle different product configurations. For example, a product may have a standard BOM and a custom BOM for a specific customer. During migration, these variants must be preserved, along with their selection criteria. If the target ERP handles variants differently, a transformation strategy is needed to map the source variants to the target structure. This is a common source of errors, as variant logic is often embedded in custom code or complex rules that are not easily transferred.
The preparation phase is critical for identifying data quality issues before migration. Data profiling involves analyzing the source BOM and routing data to understand its structure, volume, and quality. This includes checking for orphaned components, missing work centers, and inconsistent quantities. It also involves identifying custom fields that may not have direct equivalents in the target ERP. The goal is to create a data dictionary that maps every source field to a target field, including transformation rules for any mismatches. This assessment should be conducted by a team with both technical and manufacturing domain expertise to ensure that the data reflects actual production processes.
Common data quality issues in BOM and routing data include duplicate records, obsolete items, and inconsistent units of measure. For example, a component may be listed in kilograms in one BOM and in grams in another. These inconsistencies must be resolved before migration to prevent errors in the target system. Data cleansing involves standardizing units, removing obsolete items, and resolving duplicates. This process should be documented to ensure that all changes are auditable and reversible if needed.
Mapping the source BOM and routing structures to the target ERP requires a detailed understanding of both systems. This includes identifying how the target ERP handles BOM levels, routing operations, and work center assignments. For example, if the source ERP uses a flat BOM structure and the target ERP uses a multi-level structure, a transformation is needed to convert the flat data into a hierarchical format. This mapping should be validated with test data to ensure that the transformation rules work as expected.
The technical execution phase involves extracting data from the source ERP, transforming it according to the mapping rules, and loading it into the target ERP. This process should be automated using migration tools to reduce manual errors. The extraction should be performed in a controlled environment to ensure that the source data is not modified. The transformation step applies the mapping rules, including any necessary data cleansing or standardization. The loading step should be performed in a staging environment first to validate the data before loading it into the production system.
The order in which data is loaded is critical for maintaining referential integrity. Master data such as materials, work centers, and resources should be loaded first, followed by BOMs and routings. This ensures that all dependencies are satisfied before loading the dependent data. For example, a BOM cannot be loaded if its components have not yet been loaded into the target system. Similarly, a routing cannot be loaded if its work centers have not been defined. This sequencing should be documented and tested to ensure that it works as expected.
Custom fields and logic in BOM and routing data can be challenging to migrate. If the target ERP does not support the same custom fields, a decision must be made to either drop the fields or map them to standard fields. Dropping fields may result in loss of information, while mapping them may require changes to business processes. Custom logic, such as rules for selecting BOM variants, may need to be re-implemented in the target ERP. This requires close collaboration between IT and business stakeholders to ensure that the new logic meets business requirements.
Validation is the most critical phase of the migration process. It involves checking the migrated data in the target ERP to ensure that it is accurate, complete, and consistent. This includes validating BOM hierarchies, routing sequences, and work center assignments. Validation should be performed using automated tools and manual checks to catch errors that may be missed by automated processes. The goal is to ensure that the migrated data reflects the actual production processes and that it can be used for production planning and execution.
Automated validation checks can be used to verify the integrity of BOM and routing data. These checks include verifying that all components in a BOM exist in the material master, that all work centers in a routing exist in the work center master, and that all quantities are positive. Automated checks can also be used to verify that BOM hierarchies are valid, meaning that there are no circular references or orphaned components. These checks should be run after each data load to catch errors early.
Manual validation involves reviewing a sample of BOMs and routings to ensure that they are correct. This should be performed by users who are familiar with the production processes, such as production planners or engineers. User acceptance testing (UAT) involves testing the migrated data in a realistic production scenario to ensure that it works as expected. UAT should include testing of production planning, material requirements planning, and costing to ensure that the migrated data does not cause errors in these modules.
The deployment phase involves moving the migrated data from the staging environment to the production environment. This is typically done during a cutover window, which is a period of time when the old ERP is taken offline and the new ERP is brought online. The cutover plan should include detailed steps for data loading, validation, and go-live. It should also include a rollback plan in case the migration fails. The cutover window should be scheduled during a period of low production activity to minimize the impact on operations.
Cutover planning involves defining the steps, roles, and responsibilities for the migration. This includes identifying the data that needs to be loaded, the order in which it should be loaded, and the validation checks that should be performed. It also includes defining the go/no-go criteria, which are the conditions that must be met before the new ERP is brought online. The cutover execution involves following the plan step by step, with clear communication between the IT team and the business stakeholders. Any issues that arise during the cutover should be documented and resolved as quickly as possible.
A rollback strategy is essential for mitigating the risks of a failed migration. It involves defining the steps to revert to the old ERP if the new ERP fails to meet the go/no-go criteria. This includes restoring the old ERP database, re-enabling the old ERP, and communicating the rollback to all stakeholders. The rollback strategy should be tested in a staging environment to ensure that it works as expected. It is important to note that a rollback may result in data loss if transactions have been processed in the new ERP, so the go/no-go criteria should be set to minimize the risk of a rollback.
The stabilization phase involves monitoring the new ERP after go-live to ensure that it is stable and that the migrated data is being used correctly. This includes monitoring production planning, material requirements planning, and costing to identify any errors or discrepancies. It also includes providing support to users who may have questions or issues with the new ERP. The stabilization phase should continue for a period of time after go-live, typically until the new ERP is considered stable and the users are comfortable with it.
Monitoring involves tracking key performance indicators (KPIs) such as production order completion rates, material availability, and costing accuracy. These KPIs can be used to identify any issues with the migrated data. For example, if the material availability is lower than expected, it may indicate that the BOM data is incorrect. Issue resolution involves investigating any issues that are identified and resolving them as quickly as possible. This may involve correcting the data in the new ERP or adjusting the business processes to accommodate the new data.
User training and adoption are critical for the success of the migration. Users need to be trained on how to use the new ERP and how to work with the migrated data. This includes training on any changes to the BOM and routing structures, as well as any new features or functionalities in the new ERP. User adoption involves ensuring that users are comfortable with the new ERP and that they are using it correctly. This may involve providing ongoing support and training to address any issues that arise.
Mitigating the risks of BOM and routing migration requires a combination of technical and business strategies. Technical strategies include using automated migration tools, performing rigorous validation, and having a well-defined rollback plan. Business strategies include involving key stakeholders in the migration process, providing user training, and monitoring the new ERP after go-live. Best practices include starting the migration process early, involving users in the validation process, and documenting all changes and decisions. By following these best practices, organizations can reduce the risks of BOM and routing migration and ensure a successful ERP upgrade.
| Phase | Key Activities | Responsible Roles | Key Risks |
|---|---|---|---|
| Preparation | Data profiling, mapping, cleansing | IT, Business Analysts | Data quality issues, mapping errors |
| Execution | Extraction, transformation, loading | IT, Migration Team | Data loss, broken dependencies |
| Validation | Automated checks, UAT | IT, Users | Validation gaps, user errors |
| Deployment | Cutover, go-live | IT, Project Manager | Downtime, rollback needs |
| Stabilization | Monitoring, support | IT, Support Team | Post-go-live issues, user adoption |
Manufacturing BOM and routing migration is a complex process that requires careful planning, execution, and validation. By understanding the complexity of BOM and routing data, preparing thoroughly, executing the migration carefully, validating the data rigorously, and stabilizing the new ERP, organizations can mitigate the risks of migration and ensure a successful ERP upgrade. The key to success is to treat BOM and routing data as critical business assets and to involve all stakeholders in the migration process. By following the best practices outlined in this article, organizations can protect their production operations and improve their long-term ERP maintainability.
Common questions on this topic. Talk to our team for anything specific to your business.
Common errors include broken parent-child links, missing components, incorrect quantities, and lost variant logic. These errors can lead to production halts and inaccurate costing.
Validate routing data by checking that all operations reference valid work centers, that sequences are correct, and that labor and machine times are accurate. Use automated checks and manual UAT.
BOM structures can be migrated automatically using tools, but only if the source and target structures are compatible. Complex hierarchies and custom fields often require manual mapping and transformation.
Minimize downtime by scheduling the cutover during low production activity, pre-loading master data, and having a well-rehearsed cutover plan with clear go/no-go criteria.
Handle custom fields by mapping them to standard fields in the target ERP or by dropping them if they are not critical. Document all decisions and test the impact on business processes.
Tools for data profiling include ERP migration tools, data quality software, and custom scripts. These tools help identify data quality issues, such as duplicates, missing values, and inconsistencies.
Learn how to establish ERP governance in professional services firms to ensure consistent project financial management, accurate cost tracking, and scalable operations without excessive customization.
A practical guide for CIOs and finance leaders on migrating Chart of Accounts and period-end balances during ERP upgrades, covering mapping, reconciliation, and risk mitigation.
Learn how to design a construction ERP architecture that unifies project commitments, real-time costs, and change order management. This guide covers system-of-record decisions, integration patterns, and governance models for enterprise visibility.
Discuss your workflows, modules and deployment options with our team.
Back to resources