Connected business operations. Flexible deployment.
A practical guide for CIOs and ERP consultants to migrate Bill of Materials and Routing data safely, covering profiling, mapping, validation, and cutover strategies to ensure production continuity.
Migrating Bill of Materials (BOM) and routing data is one of the most critical and high-risk components of any ERP implementation or upgrade. These datasets define how products are built and how operations are executed; errors here directly impact production scheduling, inventory accuracy, and cost calculation. The recommended approach is a phased, validation-heavy process that prioritizes data cleansing and structural integrity over speed. The primary risks to control include broken BOM hierarchies, incorrect routing sequences, unit of measure (UOM) mismatches, and loss of version history. By following a structured framework that separates preparation, technical execution, validation, and stabilization, organizations can ensure that the new ERP system reflects accurate manufacturing logic, thereby protecting operational continuity and financial reporting accuracy.
Before any data is moved, a comprehensive assessment of the source data is required. This phase involves extracting a representative sample of BOMs and routings from the legacy system to understand the current state of data quality. Many legacy systems contain orphaned components, duplicate BOM versions, or routings with missing work centers. The goal is to identify these anomalies early. Responsible roles include the ERP project manager, data governance lead, and manufacturing operations manager. The operations manager must define which BOMs and routings are active and relevant for the new system, while the data team profiles the volume and complexity of the data. This step establishes the baseline for success criteria and helps in estimating the effort required for cleansing.
Clearly define the scope of the migration. Determine whether historical BOMs are needed or only current active versions. Establish data ownership: who is responsible for validating the cleansed data? Typically, the manufacturing engineering team owns BOM accuracy, while the production planning team owns routing logic. Document these responsibilities in a data ownership matrix. This prevents ambiguity during the validation phase and ensures that business users, not just IT staff, are accountable for the accuracy of the migrated data.
Once the scope is defined, the data must be cleansed and transformed to fit the target ERP schema. This is often the most labor-intensive phase. Key activities include deduplicating BOMs, resolving circular references, standardizing UOMs, and mapping custom fields to standard ERP fields. For routing data, ensure that operation sequences are logical and that work centers exist in the target system. Transformation rules must be documented and version-controlled. For example, if the legacy system uses a custom field for 'setup time' that maps to a standard 'setup minutes' field in the new ERP, this rule must be explicitly defined. Automated scripts can handle bulk transformations, but manual review is essential for complex or high-value items.
Manufacturing BOMs are often versioned to reflect design changes. The migration strategy must decide how to handle these versions. Typically, only the latest active version is migrated to the new system to reduce complexity and data volume. However, if historical cost analysis is required, older versions may need to be archived or migrated with specific effective dates. Ensure that the effective date logic in the new ERP aligns with the business's need for historical traceability. Mismanaging version dates can lead to incorrect material requirements planning (MRP) results.
With cleansed data ready, the technical team executes the migration into a staging environment. This is not the production system. Use the ERP's standard import tools or a dedicated data migration tool. The loading process should be idempotent, meaning that running the migration multiple times does not create duplicate records. Start with master data (items, work centers) before loading BOMs and routings, as the latter depend on the former. Monitor the logs for errors and warnings. Common errors include missing parent items, invalid component quantities, or routing operations referencing non-existent work centers. Resolve these errors iteratively until a clean load is achieved.
| Data Element | Common Error | Resolution Strategy |
|---|---|---|
| BOM Parent Item | Item does not exist in target | Verify item master data load order |
| Component Quantity | Zero or negative value | Cleansing rule to reject invalid quantities |
| Routing Work Center | Work center code mismatch | Map legacy codes to new standard codes |
| UOM Conversion | Missing conversion factor | Define UOM conversions in item master |
Validation is the most critical phase for ensuring data integrity. Do not rely solely on system logs. Perform business-level validation. Compare the number of BOMs and routings in the source and target systems. More importantly, validate the structure. Select a sample of high-volume or complex products and manually verify that the BOM hierarchy and routing sequences match the source data. Check for UOM consistency and effective dates. Use reconciliation reports to identify discrepancies. Any discrepancy must be investigated and resolved before proceeding. This phase requires close collaboration between IT and business users to ensure that the data not only loads but also makes business sense.
Beyond static data validation, test the dynamic behavior of the data. Run a Material Requirements Planning (MRP) cycle in the staging environment to ensure that the BOMs and routings generate correct planned orders. Create test production orders and verify that the system calculates the correct material requirements and operation times. This end-to-end testing reveals issues that static validation might miss, such as incorrect lead times or missing dependencies. If the MRP results are incorrect, the BOM or routing data is likely flawed, and the cycle must return to the cleansing phase.
Cutover is the final migration to the production environment. This should be planned during a period of low production activity to minimize disruption. The cutover plan must include a detailed runbook with step-by-step instructions, owners, and time estimates. Before cutover, perform a final backup of the legacy system and the new ERP staging environment. During cutover, load the final delta of BOM and routing data that has changed since the last staging load. Verify the load immediately. Do not go live until the go/no-go criteria are met, which should include successful reconciliation of key metrics and sign-off from the manufacturing operations manager.
After go-live, the system enters a stabilization period. Monitor production orders closely for any anomalies in material requirements or routing times. Establish a rapid response team to address data-related issues. Users may discover that certain BOMs or routings were not migrated correctly or that the new system behaves differently than expected. Track these issues in a defect log and prioritize fixes based on business impact. Continue to reconcile data between the legacy system (if still running in parallel) and the new ERP for a defined period. This phase is crucial for building user confidence and ensuring that the migration delivers the intended benefits.
Despite careful planning, risks remain. The primary risk is data loss or corruption, which can halt production. To mitigate this, maintain a verified rollback plan. This includes a tested restore procedure for the new ERP database and a plan to revert to the legacy system if critical failures occur. Define clear rollback triggers, such as a certain percentage of failed production orders or critical data discrepancies. Ensure that the legacy system is kept in a read-only state during the cutover window to prevent data divergence. Regularly test the rollback procedure in the staging environment to ensure it is feasible within the planned downtime window.
Manufacturing environments often use custom fields in BOMs and routings to capture specific operational data. These fields must be carefully mapped to the new ERP. If the new ERP does not have a direct equivalent, decide whether to use a custom field in the new system or archive the data. Additionally, consider integrations with other systems, such as MES or PLM. Ensure that the data contracts for these integrations are updated to reflect the new data structure. Test these integrations in the staging environment to ensure that data flows correctly between systems. Failure to update integrations can lead to data silos and operational inefficiencies.
Migrating manufacturing BOMs and routing data is a complex task that requires a disciplined, phased approach. By focusing on data cleansing, rigorous validation, and thorough testing, organizations can mitigate the risks associated with this critical migration. The key to success lies in collaboration between IT and business users, clear ownership of data quality, and a well-defined cutover and rollback plan. Following this framework ensures that the new ERP system supports accurate production planning and execution, ultimately driving operational efficiency and business growth.
Common questions on this topic. Talk to our team for anything specific to your business.
Common errors include missing parent items, circular references, incorrect unit of measure conversions, and duplicate BOM versions. These errors can lead to inaccurate material requirements and production delays.
Validate routing data by comparing operation sequences, work center assignments, and time standards between the source and target systems. Additionally, run test production orders to ensure that the routing logic generates correct planned orders.
While the initial load can be done in a staging environment, the final cutover to production typically requires a short downtime window to ensure data consistency. However, the duration can be minimized with thorough preparation and automated scripts.
The best tools depend on the ERP system. Many ERPs have built-in import tools, but dedicated data migration tools or ETL (Extract, Transform, Load) platforms are often used for complex mappings and transformations.
Typically, only the latest active version of a BOM is migrated to the new system. Historical versions can be archived or migrated with specific effective dates if required for cost analysis or traceability.
UOM conversion ensures that component quantities are correctly interpreted in the new system. If the legacy system uses different units than the new ERP, conversion factors must be defined to prevent calculation errors in material requirements.
Learn how to implement ERP process governance in professional services to align project delivery with revenue recognition, ensuring financial accuracy and operational consistency.
A practical guide to migrating CRM and sales pipeline data in Odoo, covering data profiling, mapping, validation, and risk mitigation for successful upgrades.
Discover how construction firms can modernize ERP systems to unify multi-project reporting, enhance cash flow visibility, and standardize financial controls across complex job sites.
Discuss your workflows, modules and deployment options with our team.
Back to resources