Connected business operations. Flexible deployment.
A practical guide to migrating manufacturing Bill of Materials (BOM) and routing data during ERP transitions. Learn how to handle version control, phantom items, and routing dependencies to ensure production continuity.
Migrating manufacturing Bill of Materials (BOM) and routing data requires a structured approach focused on data cleansing, structural mapping, and rigorous validation to prevent production disruptions. The primary risks include broken parent-child relationships, incorrect operation sequences, and loss of version history, which can lead to inaccurate material planning and production delays. To mitigate these risks, organizations must profile source data, map fields to the target ERP schema, execute trial migrations in a staging environment, and perform end-to-end reconciliation before cutover. This process ensures that the new system accurately reflects current manufacturing processes, maintaining operational continuity and data integrity.
The foundation of a successful migration is a thorough understanding of the source data. Manufacturing data is complex, involving hierarchical structures for BOMs and sequential logic for routings. Before any extraction, IT and operations teams must profile the legacy system to identify data quality issues, such as duplicate items, orphaned components, or inconsistent units of measure. This phase involves documenting the current state of BOM structures, including multi-level assemblies, phantom items, and co-products. Similarly, routing data must be analyzed for operation sequences, work center assignments, and time standards. Identifying these elements early allows for the creation of accurate mapping rules and transformation logic.
BOMs and routings are not standalone entities; they depend on the material master, work centers, and resource definitions. A common pitfall is migrating BOMs before the underlying material records are established in the target system. This leads to failed imports or broken links. Therefore, the migration sequence must be strictly defined: first, master data (materials, work centers, resources); second, BOM structures; and third, routing operations. Understanding these dependencies prevents circular reference errors and ensures that the target system can validate incoming data against existing records.
Several specific issues frequently arise during BOM migration. One major pitfall is the handling of phantom items. In many legacy systems, phantom items are used to group components without creating a separate production order. If the target ERP does not support phantom items or handles them differently, these structures must be flattened or restructured. Another common issue is version control. Legacy systems may contain multiple active versions of a BOM for different plants or dates. Migrating all versions without a clear strategy can clutter the new system and confuse planners. It is often recommended to migrate only the current active version and archive historical versions separately, unless specific regulatory or audit requirements demand full history retention.
Deeply nested BOM structures can cause performance issues and complexity during migration. If a BOM has more than five or six levels, it may be beneficial to review the structure for optimization. Some ERP systems have limits on BOM depth or performance degradation with very deep structures. During the mapping phase, teams should identify these deep structures and decide whether to maintain them as-is or restructure them into sub-assemblies. This decision should be made in collaboration with manufacturing engineers to ensure that the new structure aligns with production workflows and does not disrupt material requirements planning (MRP) calculations.
Routing data migration is often more error-prone than BOM migration due to its sequential nature. A routing defines the sequence of operations required to manufacture a product, including work centers, setup times, run times, and labor costs. A common pitfall is the loss of operation sequence integrity. If operations are imported out of order, the production system may generate invalid work instructions or fail to calculate accurate lead times. Another issue is the mapping of work centers. Legacy systems may use generic work center codes that do not align with the new ERP's resource hierarchy. If work centers are not correctly mapped, capacity planning and scheduling will be inaccurate, leading to bottlenecks and missed delivery dates.
Routing data often includes time standards used for costing and scheduling. These values must be accurately transferred to maintain financial integrity. If setup times or run times are lost or incorrectly converted, product costs will be inaccurate, affecting pricing and profitability analysis. Additionally, some legacy systems store time standards in different units (e.g., minutes vs. hours) or use different calculation methods. The transformation logic must account for these differences to ensure that the target system calculates costs and lead times correctly. Validation checks should compare the total standard cost of a product in the legacy system with the calculated cost in the new system to identify discrepancies.
Once data is profiled and pitfalls identified, the technical execution phase begins. This involves creating detailed mapping documents that define how each field in the legacy system corresponds to fields in the target ERP. For BOMs, this includes mapping parent items, component items, quantities, units of measure, and scrap rates. For routings, it involves mapping operation numbers, work centers, setup times, run times, and labor rates. Transformation rules are then developed to handle data cleansing, such as removing duplicates, standardizing units of measure, and converting date formats. These rules should be automated using migration tools or scripts to ensure consistency and reduce manual errors.
| Data Element | Common Pitfall | Solution |
|---|---|---|
| BOM Version | Multiple active versions cause confusion | Migrate only current active version; archive history |
| Phantom Items | Target system may not support phantoms | Flatten structure or reconfigure as sub-assemblies |
| Operation Sequence | Out-of-order import breaks logic | Enforce sequence validation during import |
| Work Centers | Mismatched resource codes | Map legacy codes to new resource hierarchy |
| Time Standards | Unit conversion errors | Standardize units and validate cost calculations |
Validation is the most critical phase of the migration. After loading data into the staging environment, teams must perform rigorous reconciliation to ensure that the migrated data matches the source data. This involves comparing record counts, checking for broken links, and validating business rules. For BOMs, this means verifying that all components are linked to the correct parent and that quantities are accurate. For routings, it involves checking that operation sequences are correct and that work centers are assigned properly. Automated validation scripts can be used to flag discrepancies, but manual spot checks are also necessary to catch logical errors that automated tools may miss.
Beyond data validation, end-to-end business process testing is essential. This involves creating test production orders using the migrated BOMs and routings to verify that the system can generate accurate material requirements, work instructions, and cost estimates. Test scenarios should cover various product types, including simple items, complex assemblies, and items with co-products or by-products. This testing helps identify issues that may not be apparent in data validation, such as MRP calculation errors or scheduling conflicts. Feedback from testing should be used to refine mapping rules and transformation logic before the final cutover.
Cutover is the final step in the migration process, where data is moved from the legacy system to the production environment. This phase requires careful planning to minimize downtime and ensure a smooth transition. A detailed cutover runbook should be created, outlining each step, responsible parties, and estimated duration. The runbook should include data extraction from the legacy system, transformation, loading into the target ERP, and final validation. Downtime should be scheduled during a period of low production activity, such as a weekend or holiday, to minimize impact on operations. Communication with all stakeholders, including production managers, planners, and finance teams, is crucial to ensure that everyone is prepared for the transition.
Before proceeding with the cutover, a go/no-go decision must be made based on predefined criteria. These criteria should include the completion of all validation checks, resolution of critical defects, and sign-off from key stakeholders. If any critical issues remain unresolved, the cutover should be postponed to avoid introducing errors into the production environment. A rollback strategy must also be in place in case the cutover fails. This strategy should include a plan to restore the legacy system and resume operations if the new system is not stable. Regular backups of the legacy system should be taken before the cutover to ensure that data can be recovered if necessary.
After the cutover, the focus shifts to stabilizing the new system. This involves monitoring the system for errors, addressing user issues, and fine-tuning configurations. A hypercare period should be established, where a dedicated support team is available to assist users and resolve issues quickly. During this period, teams should closely monitor production orders, material requirements, and cost calculations to ensure that the system is functioning as expected. Any discrepancies should be investigated and resolved promptly to prevent them from escalating into larger problems. Feedback from users should be collected and used to improve the system and training materials.
Migrating manufacturing BOMs and routing data is a complex but manageable process if approached with careful planning and rigorous validation. By identifying common pitfalls, such as phantom item handling and operation sequence integrity, and implementing robust data cleansing and mapping strategies, organizations can ensure a smooth transition to their new ERP system. The key to success lies in thorough preparation, detailed testing, and effective communication with all stakeholders. By following these best practices, businesses can maintain operational continuity, protect data integrity, and realize the full benefits of their ERP investment.
Common questions on this topic. Talk to our team for anything specific to your business.
The most common error is the loss of parent-child relationships due to incorrect mapping of item codes or failure to migrate material master data before BOMs. This results in orphaned components and broken structures.
Check if the target ERP supports phantom items. If not, flatten the BOM structure by moving phantom components directly to the parent item or restructure them as sub-assemblies. Consult with manufacturing engineers to ensure the new structure aligns with production workflows.
Generally, migrate only the current active version to keep the new system clean and efficient. Archive historical versions in a separate repository if required for audit or regulatory purposes. Migrating all versions can clutter the system and confuse planners.
The duration depends on the volume of data and complexity of the routing structures. For a mid-sized manufacturer, the technical migration may take a few days, but the overall process, including profiling, mapping, testing, and validation, can take several weeks to months.
Use a combination of automated reconciliation scripts to compare record counts and field values, and manual spot checks to verify business logic. Perform end-to-end testing by creating test production orders to ensure that material requirements and cost calculations are accurate.
Yes, but they are interdependent. BOMs define the materials, while routings define the process. It is recommended to migrate BOMs first, then routings, ensuring that all referenced materials and work centers exist in the target system. Validate the integration between BOMs and routings after both are migrated.
Learn how to validate ERP migration success using critical KPIs for data integrity, system performance, and business continuity. A practical guide for CIOs and IT leaders.
Learn how to harmonize project, resource, and financial processes in a Professional Services ERP to eliminate billing delays, improve margin visibility, and scale delivery operations without increasing operational complexity.
Learn how to build a construction ERP reporting framework that connects project costs, procurement, and financials for real-time executive visibility and better decision-making.
Discuss your workflows, modules and deployment options with our team.
Back to resources