Connected business operations. Flexible deployment.
A practical guide to migrating manufacturing data, focusing on Bill of Materials (BOM) integrity, routing logic, and work order status management to ensure operational continuity.
Manufacturing data migration is the most complex aspect of ERP modernization because it directly impacts production continuity. The recommended approach is a phased, validation-heavy strategy that prioritizes the integrity of Bill of Materials (BOM) structures, routing logic, and the status of open work orders. Unlike financial data, manufacturing data is highly relational; a single error in a BOM component or a missing routing operation can halt production lines. The primary risks to control are data loss, broken dependencies between items and routings, and the inability to schedule production accurately in the new system. Success depends on rigorous data profiling, precise mapping of legacy fields to target schemas, and extensive reconciliation testing before cutover. This guide outlines the technical and operational steps required to migrate these critical datasets safely.
Before extracting data, you must understand the current state of your manufacturing master data. Data profiling involves analyzing the legacy system to identify data quality issues, such as duplicate items, orphaned BOM lines, or routings without associated work centers. This phase is critical for defining the scope of the migration. You need to determine which data is essential for the new system and which can be archived. For example, historical closed work orders may not need to be migrated if they are not required for active audits, but open work orders must be transferred to ensure continuity. Gap analysis compares the legacy data structure with the target ERP's schema to identify missing fields or incompatible data types. This step requires collaboration between IT, production managers, and process engineers to define business rules for data transformation.
Decide whether to migrate all historical data or only active records. A common strategy is to migrate all active BOMs and routings, along with open work orders and recent closed work orders for reference. Historical data older than a defined period (e.g., 3-5 years) is often archived in a data warehouse rather than migrated to the live ERP. This reduces migration time and improves system performance. Document these decisions clearly, as they will affect the data extraction scripts and validation checks. Ensure that all stakeholders agree on the scope to avoid scope creep during the migration process.
BOMs are the backbone of manufacturing data. They define the components required to produce a finished good. Migration of BOMs requires careful handling of multi-level structures, phantom items, and alternative BOMs. In the legacy system, BOMs may be stored in a flat structure or a hierarchical one. The target ERP may require a specific format, such as a parent-child relationship with unique identifiers for each line. You must map legacy component codes to target item codes, ensuring that all components exist in the target item master before loading BOMs. Phantom items, which are used for grouping but not stocked, must be correctly flagged in the target system to prevent inventory errors. Alternative BOMs, used for different production scenarios, must be preserved with their specific validity dates and conditions.
Multi-level BOMs require recursive validation to ensure that all sub-assemblies and raw materials are correctly linked. A missing link at any level can cause MRP (Material Requirements Planning) failures. Phantom items must be identified and mapped to the target system's equivalent concept. If the target ERP does not support phantom items, you may need to restructure the BOM to eliminate them, which requires process engineering approval. Validate the quantity and unit of measure for each BOM line, as discrepancies here can lead to significant material waste or shortages. Use automated scripts to check for circular references, where a component is also a parent of itself, which is a common data error in legacy systems.
Routings define the sequence of operations required to manufacture a product. They include work centers, standard times, and setup times. Migrating routings is complex because they are tightly coupled with BOMs and work centers. You must map legacy operation codes to target operation types, ensuring that the sequence is preserved. Work centers must be migrated before routings, as routings reference work center IDs. Standard times, such as setup, run, and teardown times, must be converted to the target system's time units. If the legacy system uses different time calculation methods, you may need to adjust the values to reflect actual production times. Routing validation should check for missing work centers, invalid operation sequences, and zero-time operations that may cause scheduling issues.
Work centers are the resources where operations are performed. They include capacity, efficiency, and calendar data. Ensure that work center calendars are migrated correctly, as they affect production scheduling. If the legacy system uses different calendar formats, you must transform them to match the target ERP's requirements. Operation mapping requires defining how legacy operations correspond to target operations. Some legacy operations may need to be split or combined to fit the target system's granularity. Document these mapping rules and validate them with production managers to ensure that the new routings reflect actual production processes. This step is critical for maintaining accurate production planning and capacity loading.
Work orders represent the production tasks in progress. Migrating open work orders is essential for continuity, as they contain information about materials issued, labor hours, and completion status. Closed work orders are typically not migrated unless required for audit or historical analysis. For open work orders, you must map the status codes from the legacy system to the target system's status codes. For example, a legacy status of 'In Progress' may map to 'Released' or 'In Production' in the target ERP. You must also migrate the associated material movements and labor entries to ensure that the cost and quantity balances are accurate. This requires careful reconciliation between the legacy and target systems to prevent discrepancies in inventory and financial records.
Status mapping is a critical step in work order migration. Define a clear mapping table that translates legacy status codes to target status codes. Ensure that the target system's workflow supports the mapped statuses. For example, if a legacy work order is 'On Hold,' the target system must have a corresponding 'On Hold' status that prevents further processing. Reconciliation involves comparing the quantity and cost of materials issued in the legacy system with the quantity and cost recorded in the target system. Any discrepancies must be investigated and resolved before cutover. Use automated reconciliation tools to compare data between the two systems and generate reports for review. This step ensures that the financial and inventory records are accurate after migration.
Data transformation involves converting legacy data into the format required by the target ERP. This includes standardizing item codes, converting units of measure, and normalizing dates. Data cleansing involves removing duplicates, correcting errors, and filling in missing values. For manufacturing data, cleansing is particularly important for BOMs and routings, as errors here can have significant operational impacts. Use data cleansing tools to identify and fix common issues, such as invalid characters in item descriptions or inconsistent decimal places in quantities. Document all transformation and cleansing rules to ensure that the process is repeatable and auditable. This documentation is essential for troubleshooting issues during and after migration.
Validation is the process of ensuring that the migrated data is accurate and complete. It involves running automated checks and manual reviews to verify that the data meets the defined quality standards. For BOMs, validate that all components are linked correctly and that the quantities are accurate. For routings, validate that the operation sequences are correct and that the work centers are valid. For work orders, validate that the status codes are mapped correctly and that the material and labor entries are reconciled. Use test environments to simulate production scenarios and verify that the migrated data supports accurate planning and scheduling. Conduct user acceptance testing (UAT) with production managers and planners to ensure that the data meets their needs. Address any issues found during testing before proceeding to cutover.
Cutover is the final step in the migration process, where the legacy system is decommissioned and the new ERP is activated. Plan the cutover carefully to minimize downtime and ensure a smooth transition. Define a cutover runbook that outlines the steps, responsibilities, and timelines for the migration. Freeze data changes in the legacy system during the cutover window to ensure data consistency. Perform the final data load, including any incremental changes that occurred since the last test migration. Validate the data in the target system and confirm that all open work orders are active and that BOMs and routings are accessible. Communicate the cutover plan to all stakeholders and provide support during the transition. Have a rollback plan in place in case of critical issues, although rolling back manufacturing data is complex and should be a last resort.
After cutover, the focus shifts to stabilizing the new system and ensuring that users can operate effectively. Monitor the system for any issues with BOMs, routings, or work orders. Provide training and support to users to help them adapt to the new system. Conduct post-migration audits to verify that the data is accurate and that the system is performing as expected. Address any issues promptly and document the resolutions. Use the feedback from users to identify areas for improvement and make necessary adjustments. Stabilization is an ongoing process that continues until the system is fully integrated into the business operations. Regular reviews and continuous improvement efforts are essential for long-term success.
| Data Type | Key Risks | Validation Checks | Responsible Role |
|---|---|---|---|
| BOMs | Broken links, incorrect quantities | Multi-level integrity, phantom item flags | Process Engineer |
| Routings | Missing work centers, invalid sequences | Operation sequence, work center validity | Production Manager |
| Work Orders | Status mismatches, cost discrepancies | Status mapping, material/labor reconciliation | IT Director |
Common questions on this topic. Talk to our team for anything specific to your business.
Yes, open work orders should be migrated to ensure production continuity. Map status codes and reconcile material/labor entries to maintain accuracy.
Use recursive validation to ensure all sub-assemblies and raw materials are correctly linked. Check for circular references and phantom items.
Validate operation sequences, work center assignments, and standard times. Conduct UAT with production managers to ensure accuracy.
Migrate only open work orders and recent closed ones for reference. Archive older historical data in a data warehouse to reduce migration time.
Define a mapping table that translates legacy operation codes to target operation types. Validate with production managers to ensure accuracy.
Common risks include broken BOM links, missing work centers, status mismatches, and cost discrepancies. Mitigate with rigorous validation and reconciliation.
Discover how to manage integration middleware risks during ERP migrations, including API compatibility, data consistency, and cutover strategies for multi-system environments.
Learn how distribution companies can shift from lagging financial reports to real-time operational intelligence using modern ERP architecture, master data governance, and integrated supply chain processes.
A technical guide for CIOs and ERP consultants on managing custom fields, database schema changes, and data integrity during Odoo version upgrades and migrations.
Discuss your workflows, modules and deployment options with our team.
Back to resources