CMMS migration: what to do with old work order history

Why does old work order history get lost in a CMMS switch?#

Old work order history gets lost in a CMMS switch because migration projects focus on what the new system needs on day one. Implementation teams import the asset register, PM schedules and open work orders, then treat closed history as optional. Field names, failure code lists and asset hierarchies rarely line up between systems, so history that does not map is left behind.

The loss usually becomes permanent later. A hosted CMMS contract ends and the account is closed, or an on-premise server in the maintenance office is decommissioned during an IT cleanup. By the time a reliability engineer needs to see how often a gearbox failed before the switch, nobody can open the old database.

What migrates and what gets archived?#

Masters and open work migrate, and closed transactions are usually archived, though some plants also load a summary of recent history into the new system. The table shows a common split for a plant-level CMMS.

Decide early where downtime lives. If the old CMMS recorded downtime against work orders while production tracked it in the MES or on spreadsheets, the archive should keep the CMMS side intact and note the overlap. Joining the two later is far easier when both keep their original timestamps and asset references.

The full-export step to finish before shutoff#

The full-export step is a complete, verified copy of the old CMMS database, taken while the system and its vendor support still exist. Reports and saved views are not enough, because they show only selected fields and often truncate notes.

Ask for the export in the contract exit plan, not in the last month. Hosted vendors differ on what a full export includes, whether it is self-service and how long data stays available after cancellation, so read the agreement and confirm the method in writing.

• 1Request a full database backup or table-level export, including custom fields and audit history.
• 2Export code tables, the asset hierarchy and user lists as they stood on the cutover date.
• 3Export attachments with a file index that links each file to its work order or asset.
• 4Check record counts and date ranges against the old system's own reports.
• 5Store the export read-only, with checksums and access limited to named roles.
• 6Write a short description of each table, its key fields and its code values.
• 7Record who exported what, when, and from which system version.

Keep the work order story readable#

A readable work order story connects a symptom, the work performed, the parts used and the outcome to an asset that still exists. Without the asset ID crosswalk, an archived work order points to an asset number the new system has never heard of.

Keep technician notes exactly as written. Notes such as found coupling insert worn, replaced and realigned, vibration back to normal are what make maintenance history valuable to reliability engineers and to AI teams building maintenance assistants. Summaries and codes lose the reasoning.

Keep the old failure codes beside the mapped new codes rather than replacing them. Old codes reflect how technicians thought about failures at the time, and a mapping can be revised later if it turns out to be wrong.

Illustrative: an extrusion plant changes CMMS#

Illustrative: a fictional aluminum extrusion plant has run an on-premise CMMS on a server in the maintenance office for many years and is moving to a cloud CMMS. The implementation partner plans to load assets, PMs and open work orders, and nothing else.

The VP of operations adds an archive workstream. IT takes a full database backup and a table-level export, the maintenance planner builds a crosswalk from old asset numbers to the new hierarchy, and a reliability engineer writes a one-page description of the failure code list. The old server is retired only after record counts are checked.

When a press hydraulic pump fails after the switch, the planner pulls years of prior work orders for that press from the archive quickly. The same archive later becomes the basis for an inventory of maintenance records when leadership asks what operating history the plant holds.

What to check before anyone outside sees the archive#

Maintenance archives need a sensitivity check before any outside use because they record people, contractors and sometimes customers. The check belongs to maintenance and IT, with legal or HR advice where names and incidents appear.

Most of these items can be masked or removed without losing the work order story.

• 1Technician names and employee IDs in labor entries and notes.
• 2Contractor company names, rates and invoices.
• 3Injury, near-miss and incident references linked to work orders.
• 4OEM manuals and service bulletins, which belong to the equipment makers.
• 5Customer-owned tooling or equipment maintained under customer agreements.
• 6Photos showing people, badges or customer markings.

How SourceX approaches maintenance history#

SourceX treats work order history as one of the core record families in manufacturing, because it links asset, symptom, action and outcome. The initial fit check asks only about systems, years of history and record types, and no exports are shared at that stage.

If a package proceeds through the SourceX five-step transaction, large archives stay in the company's own storage or ship on encrypted drives, technician and contractor names are removed during Preparation, and the SourceX Evidence Packet documents where the records came from, the permitted use, the privacy record and who authorized release.