Connected business operations. Flexible deployment.
A practical guide for CIOs and ERP consultants on migrating Bill of Materials and Routing data. Covers data profiling, mapping, validation, and risk mitigation to ensure production continuity.
Migrating Bill of Materials (BOM) and Routing data is the most critical phase of a manufacturing ERP implementation. These datasets define how products are built and how labor and machine time are consumed. A failure here does not just result in data errors; it halts production, disrupts supply chains, and invalidates cost accounting. The recommended approach is a phased, validation-heavy process that prioritizes data cleansing in the source system before extraction. You must treat BOM and Routing migration not as a simple database copy, but as a business process re-engineering exercise. The primary risks to control are structural mismatches between legacy and target systems, loss of effective dating logic, and the silent corruption of multi-level hierarchies. By establishing strict data ownership, performing rigorous reconciliation, and using representative staging environments, you can ensure that the new ERP reflects the true state of your manufacturing operations.
Before writing a single line of migration code, you must understand the quality and structure of your existing data. Legacy systems often contain years of accumulated technical debt, including duplicate items, orphaned components, and inconsistent naming conventions. Start by profiling the source database to identify the volume of BOMs, the average depth of multi-level structures, and the number of active versus obsolete routings. Identify data anomalies such as negative quantities, missing work centers, or operations with zero setup times. This phase requires collaboration between IT and Operations. IT provides the technical schema, while Operations validates the business logic. For example, if a legacy system uses a specific flag to denote a 'phantom item' (an item that is not stocked but is part of the BOM), you must document this logic explicitly. Without this documentation, the migration script may incorrectly create stockable items for phantom components, leading to inventory discrepancies.
Assign clear ownership for each data domain. The Production Manager should own the BOM structure and component quantities. The Industrial Engineering team should own the routing operations, work centers, and time standards. The IT team owns the technical mapping and ETL scripts. This separation ensures that business rules are validated by those who understand the shop floor, while technical integrity is maintained by the IT team. During this phase, also assess the target ERP's capabilities. Does it support multi-level BOMs with the same depth as the legacy system? Does it handle co-products and by-products in the same way? Compatibility and support for specific data structures must be verified against the vendor's official documentation for the exact source and target versions. Do not assume that all custom fields or legacy logic will map directly.
Data cleansing is the most labor-intensive but most valuable step. Migrating dirty data into a new system only amplifies existing problems. Focus on deduplication first. If two items in the legacy system represent the same physical part but have different codes, they must be merged before migration. This is particularly dangerous for BOMs, as merging items without updating all parent BOMs will break the hierarchy. Next, standardize units of measure. If the legacy system uses 'boxes' and 'pieces' interchangeably, define a standard unit for the new ERP. For routing data, ensure that all operations reference valid work centers. If a work center has been decommissioned but still appears in active routings, it must be remapped to a current resource. This process requires a formal change control process. Any changes made to the source data during cleansing must be logged and approved by the data owners to maintain an audit trail.
Learn how distribution businesses can eliminate manual tracking by aligning ERP inventory and vendor management processes, integrating systems, and establishing clear data ownership.
A practical guide for CIOs and finance leaders on migrating fixed asset registers and depreciation schedules. Covers data profiling, mapping, reconciliation, and risk mitigation to ensure financial accuracy during ERP transitions.
Transform your manufacturing ERP from a passive database into an active workflow orchestration platform. Learn how to connect procurement, production, and finance to reduce manual work and improve operational visibility.
Discuss your workflows, modules and deployment options with our team.
Back to resources