Common migration scenarios
| Scenario | Effort |
|---|---|
| Same controller brand, similar machine | Low: adjust limits, M-codes, tool changer |
| Same controller, new kinematics (3-axis to 5-axis) | Medium: add multi-axis logic and TCP |
| Different controller brand | Medium to high: new dialect and cycles |
| Lathe to mill-turn | High: channels, C-axis, live tools, synchronisation |
What carries over
- Shop format: headers, comments, tool lists.
- Safety logic: safe start, retract strategy, restart blocks.
- Standard probing and tool check routines (if the new machine supports them).
What changes
- Kinematics, travel limits and rotary configuration.
- Tool changer behaviour and tool change position.
- Controller dialect, cycles and TCP / tilted-plane codes.
- MTB M-codes for coolant, clamps, conveyors and doors.
- Program transfer method and file naming.
Re-posting existing programs
The biggest benefit of a proper migration is that existing CAM files can be re-posted for the new machine instead of hand-converting old G-code. Check that tools, holders and work-holding in the CAM files still match the new machine's envelope.
Migration checklist
[ ] Machine data sheet and controller options collected
[ ] Kinematics and limits configured in CAM and post
[ ] MTB M-code list reviewed
[ ] Test program set posted and simulated
[ ] Dry run and single-block proving on new machine
[ ] Top 10 production programs re-posted and proved
[ ] Old machine post archived, new post under version controlPlan the post processor as part of the machine purchase, not after the machine arrives.
Migrate your posts with ENGIMANDI
See our CNC post processor development service and migrating posts between controllers.