Skip to content
ERP Migration

Handling Complex Bill of Materials and Routing Data in Manufacturing ERP Migrations

A practical guide to migrating complex BOMs and routings in manufacturing ERP systems, covering data profiling, transformation, validation, and risk mitigation strategies.

10 min readSysGenPro Editorial
Handling Complex Bill of Materials and Routing Data in Manufacturing ERP Migrations

Direct Approach to Migrating Complex BOM and Routing Data

Migrating complex Bill of Materials (BOM) and routing data in manufacturing ERP systems requires a structured approach focused on data integrity, process continuity, and risk mitigation. The recommended approach involves thorough data profiling, detailed mapping of source-to-target structures, rigorous transformation logic, and multi-stage validation before cutover. This matters because BOMs and routings are the backbone of production planning, scheduling, and cost calculation. Errors in this data can lead to production stoppages, material shortages, inaccurate costing, and significant financial losses. The main risks to control include data loss during extraction, incorrect transformation of multi-level structures, broken dependencies between materials and work centers, and validation gaps that allow corrupted data to enter the production environment. Success depends on treating BOM and routing data as critical business assets, not just database records, and implementing strict governance throughout the migration lifecycle.

Preparation Phase: Data Profiling and Assessment

The preparation phase begins with comprehensive data profiling of the source ERP system. This involves analyzing the structure, volume, and quality of BOM and routing data. Key activities include identifying all BOM levels, counting total components, detecting phantom items, and mapping routing operations to work centers. Data quality assessment should identify duplicates, missing fields, inconsistent units of measure, and orphaned records. For routing data, profile the number of operations, work center assignments, time standards, and setup times. Document the current state of data governance, including who owns BOM changes and how version control is managed. This phase requires collaboration between IT, production planning, and engineering teams to understand business rules embedded in the data. Create a data inventory that lists all BOMs and routings, their complexity levels, and associated production volumes. This inventory helps prioritize migration efforts and identify high-risk items that require special handling.

Key Data Quality Metrics to Track

  • Percentage of BOMs with complete component lists
  • Number of multi-level BOMs exceeding five levels
  • Count of phantom items and their usage frequency
  • Routing operations with missing work center assignments
  • Material master records with inconsistent units of measure
  • Duplicate BOM versions for the same product
  • Orphaned routing operations without parent BOMs
  • Time standards that are outdated or missing

Mapping and Transformation Strategy

Develop a detailed mapping matrix that defines how each source data element translates to the target ERP system. This includes field-level mappings for BOM components, routing operations, work centers, and material attributes. Transformation logic must handle structural differences between systems, such as different BOM hierarchy representations or routing operation sequencing methods. For multi-level BOMs, define how parent-child relationships are preserved during transformation. Phantom items require special handling, as they may need to be converted to regular items or handled through specific target-system features. Routing data transformation must preserve operation sequences, work center assignments, and time standards. Document all transformation rules and exceptions in a migration specification document. This document serves as the single source of truth for developers and validators. Consider using intermediate staging tables to hold transformed data before loading into the target system, allowing for validation and correction before final load.

Handling Structural Differences

Source and target ERP systems often represent BOMs and routings differently. Some systems use flat structures with level indicators, while others use recursive parent-child relationships. Routing operations may be stored as separate records or as part of a single routing document. The transformation strategy must account for these differences. For example, if the source system stores BOM components in a flat table with a level field, the target system may require a hierarchical structure. The transformation logic must reconstruct the hierarchy correctly. Similarly, routing operations may need to be split or combined to match the target system's data model. Work center mappings require careful attention, as work center names and codes may differ between systems. Create a work center mapping table that links source work centers to target work centers, including capacity and cost rate translations. This mapping must be validated with production managers to ensure accuracy.

Data Cleansing and Deduplication

Before transformation, cleanse the source data to remove duplicates, correct errors, and standardize formats. Deduplication is critical for BOM data, as duplicate BOM versions can cause confusion during production. Identify and resolve duplicate BOMs by determining which version is current and which should be archived. For routing data, deduplicate operations that appear multiple times for the same product. Standardize units of measure across all materials and BOM components. Ensure that all material codes are valid and exist in the material master. Correct missing or invalid work center assignments in routing data. Document all cleansing actions in a data cleansing log, including the reason for each change and the person who approved it. This log provides an audit trail and helps identify systemic data quality issues that need to be addressed in the target system's governance processes. Cleansing should be performed in a controlled environment with version control to allow rollback if errors are discovered.

Validation and Reconciliation

Validation is the most critical phase of BOM and routing data migration. Implement multi-stage validation to ensure data integrity. First, perform structural validation to verify that all BOM hierarchies are complete and all routing operations are properly sequenced. Second, perform referential integrity validation to ensure that all BOM components reference valid material codes and all routing operations reference valid work centers. Third, perform business rule validation to verify that BOMs and routings comply with manufacturing constraints, such as minimum order quantities and lead times. Reconciliation involves comparing source and target data to ensure that all records were migrated correctly. Use automated reconciliation tools to compare record counts, total quantities, and key attributes between source and target systems. Investigate and resolve any discrepancies before proceeding to the next stage. Validation should be performed in a staging environment that mirrors the production environment in terms of data volume and complexity.

Validation TypePurposeKey ChecksResponsible Role
Structural ValidationVerify BOM hierarchy and routing sequenceAll parent-child relationships intact, operations in correct orderData Migration Lead
Referential IntegrityEnsure all references are validMaterial codes exist, work centers assigned, no orphaned recordsERP Administrator
Business Rule ValidationVerify compliance with manufacturing constraintsMinimum order quantities, lead times, capacity constraintsProduction Planner
ReconciliationCompare source and target dataRecord counts, total quantities, key attributes matchData Quality Analyst

Trial Migrations and Testing

Conduct multiple trial migrations in a staging environment before the production cutover. Each trial migration should use a representative subset of production data, including complex BOMs and routings that represent the most challenging scenarios. Test the entire migration process, from extraction through transformation to load and validation. Measure the time required for each step and identify bottlenecks. Test the rollback process to ensure that the system can be restored to a known good state if the migration fails. User acceptance testing (UAT) should involve production planners, engineers, and shop floor supervisors who will use the migrated data. They should verify that BOMs and routings are correct and that production planning and scheduling functions work as expected. Performance testing should verify that the target system can handle the migrated data volume without degradation in response times. Document all test results and defects, and track defect resolution before proceeding to the next trial.

Cutover Planning and Execution

Develop a detailed cutover plan that defines the sequence of activities, responsible parties, and timing for each step. The cutover plan should include a freeze window during which no changes are made to source BOM or routing data. Define go/no-go criteria that must be met before proceeding with the production load. These criteria should include successful completion of all validation checks, resolution of all critical defects, and sign-off from key stakeholders. The cutover execution should follow a documented runbook that specifies each step, the person responsible, and the expected outcome. Include communication plans to notify all stakeholders of the cutover timeline and any potential impacts on production. Have a rollback plan ready in case the migration fails. The rollback plan should specify the conditions that trigger a rollback, the steps to execute the rollback, and the estimated time to restore the system to a pre-migration state. Conduct a cutover rehearsal in the staging environment to test the runbook and identify any gaps or issues.

Post-Migration Stabilization

After the production cutover, enter a stabilization phase where the focus is on monitoring, issue resolution, and user support. Monitor the target system for any data integrity issues, performance problems, or user-reported errors. Establish a war room with key stakeholders from IT, production, and engineering to address issues in real time. Track all issues in a defect management system and prioritize resolution based on business impact. Provide additional training and support to users who are unfamiliar with the new system's BOM and routing features. Conduct post-migration audits to verify that data integrity is maintained over time. Review data governance processes to ensure that BOM and routing changes are properly controlled in the new system. Document lessons learned from the migration process and update migration playbooks for future projects. The stabilization phase should continue until the system is operating normally and all critical issues are resolved.

Risk Mitigation and Continuity

Mitigate migration risks by implementing strict controls at each phase. Data loss risk is mitigated by performing verified backups before each migration step and testing restore procedures. Broken customizations risk is mitigated by thoroughly testing all custom BOM and routing functions in the staging environment. Integration failures risk is mitigated by testing all integrations that depend on BOM and routing data, such as procurement and inventory systems. Reporting discrepancies risk is mitigated by validating that all reports that use BOM and routing data produce accurate results after migration. Security misconfiguration risk is mitigated by reviewing access controls for BOM and routing data in the target system. Performance regressions risk is mitigated by conducting performance testing with production-level data volumes. User adoption risk is mitigated by providing comprehensive training and support during the stabilization phase. Rollback limits risk is mitigated by defining clear rollback triggers and testing the rollback process before cutover. All risk mitigation activities should be documented and reviewed by the project team.

Decision Criteria and Ownership

Define clear decision criteria for key migration decisions, such as whether to migrate historical BOM data or start fresh, how to handle phantom items, and which BOM versions to migrate. Assign ownership for each decision to a specific role, such as the production planning manager for BOM version selection and the engineering manager for phantom item handling. Document all decisions in a decision log, including the rationale and the person who made the decision. This log provides an audit trail and helps resolve disputes during the migration process. Dependencies between BOM and routing data and other data domains, such as material master and work centers, must be clearly defined and managed. Ensure that all dependent data is migrated and validated before BOM and routing data is loaded. This prevents referential integrity errors and ensures that the production system is fully functional after cutover.

Measurable Checks and Success Metrics

Define measurable checks and success metrics to evaluate the migration's success. Key metrics include the percentage of BOMs and routings migrated without errors, the number of data integrity issues discovered during validation, the time required for the cutover process, and the number of user-reported issues during the stabilization phase. Track these metrics throughout the migration and compare them to predefined targets. For example, the target for BOM migration accuracy might be 99.5% with no critical errors. If the actual accuracy falls below the target, investigate the root cause and implement corrective actions before proceeding to the next phase. Use these metrics to report progress to stakeholders and to make go/no-go decisions. Continuous monitoring of these metrics during the stabilization phase helps identify any lingering issues and ensures that the system is operating as expected.

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 include data loss during extraction, incorrect transformation of multi-level structures, broken dependencies between materials and work centers, and validation gaps that allow corrupted data to enter the production environment. These risks can lead to production stoppages, material shortages, and inaccurate costing.

02How do you handle multi-level BOMs in ERP migration?

Multi-level BOMs require careful mapping of parent-child relationships and level indicators. The transformation logic must reconstruct the hierarchy correctly in the target system. Validation must verify that all levels are intact and that component quantities are accurate at each level.

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

Validate routing data by checking operation sequences, work center assignments, and time standards. Use automated reconciliation tools to compare source and target data. Perform business rule validation to ensure that routings comply with manufacturing constraints.

04How long does it take to migrate manufacturing data?

The time required depends on the volume and complexity of the data, the number of trial migrations, and the extent of data cleansing required. A typical migration may take several weeks to several months, with the cutover itself taking a few days to a week.

05Should we migrate historical BOM data or start fresh?

This decision depends on business needs. If historical data is required for reporting or audit purposes, migrate it. If the goal is to start with a clean slate, consider migrating only current BOMs and archiving historical data separately. Document the decision and its rationale.

06How do we handle phantom items during BOM migration?

Phantom items require special handling. Determine whether the target system supports phantom items or if they need to be converted to regular items. Document the handling strategy and validate that phantom items are correctly represented in 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