The problem
On paper: “just a data migration”. In an industrial setting it is mission-critical. Any inconsistency in BOMs, references or routings can block purchasing, halt manufacturing, or stall dispatch.
Zitron was moving from their own ERP to Infor and had three jobs in one:
- Migrate the full design and production dataset (thousands of parts, production orders, engineering trees, BOMs, histories, component relationships)
- Redefine the coding scheme in the process
- Keep the business running while it happened
What we did
We executed the migration with full validation and acted as functional consultancy and operational bridge between Zitron and the Infor implementation team:
- Defined the coding rules
- Detected gaps in the source data
- Specified the required configuration
- Accompanied the handover until operations were stable and traceable in the new system
The CAD→ERP bridge
In parallel we tackled the workflow that would have broken first without a fix: CAD to ERP. Zitron designs in PTC Creo, and the new ERP needed those models as consumable engineering/manufacturing trees — with no manual rework.
We built an integration that lets an engineer export the CAD structure to Infor-ready data with one click from inside Creo: BOMs, hierarchies and metadata, all transformed at source. Fewer human errors, faster release into production.
We handled end-user deployment, incident response, and flow robustness so the tool worked in day-to-day use, not just in a test environment.
Outcome
- A safe migration
- A controlled coding-scheme change
- A direct engineering↔manufacturing link designed to scale without friction