A new CMMS does not need every record from the old maintenance world. It needs the information required to operate correctly on day one, plus historical evidence worth preserving for future decisions. Those are not the same thing as “everything we have.”
The dangerous assumption is: if the data exists, move it.
Existing data is evidence, not automatically an asset
AlexRenew documented an unusually candid problem during its CMMS procurement. It stated that the quality of data in its current CMMS is in many cases questionable or incomplete, making it unclear whether data migration is a useful effort.
Its implementation scope therefore makes the contractor responsible for reviewing the data, identifying gaps and obsolete data such as that associated with retired or decommissioned assets, and checking the accuracy of the data to be loaded.
Migration should preserve useful maintenance truth, not reproduce historical uncertainty at higher speed.
The Migration Decision
The Migration Decision is a CMMSBuyersGuide framework. For each data set choose one disposition:
- Migrate
- Transform
- Rebuild
- Archive
- Retire
- Verify first
Do not default to migrate.
Day-One Truth and Historical Evidence
Day-One Truth and Historical Evidence is a CMMSBuyersGuide framework.
| Category | Definition | Examples |
|---|---|---|
| Day-One Truth | Information that must be correct for the new system to operate. | Active assets, current hierarchy, active PM, open work, current parts, current users, required procedures |
| Historical Evidence | Past information useful for analysis, traceability or decision context. | Completed work, failure history, past costs, old readings, retired assets, attachments |
Day-one data has to run the future. Historical data has to justify the cost and risk of carrying the past.
Start with the destination
Before cleaning old data, establish what the new system should represent: asset hierarchy, location structure, equipment identity, PM structure, parts model, statuses, codes and ownership. Otherwise the team can clean old data into an old structure.
Migration mapping begins with the destination, not the spreadsheet.
Inventory the sources
Create a record for each source. Different sources can have different authority.
- Source
- Objects
- Owner
- Quality
- Authority
- Format
- History depth
- Target
- Disposition
Migration Worth
Migration Worth is a CMMSBuyersGuide framework. Evaluate data using three questions, without calculating a numeric score.
| Test | Question |
|---|---|
| Operational necessity | Will the new system operate incorrectly without it? |
| Decision value | Will future maintenance decisions materially benefit from it? |
| Migration confidence | Do we understand it well enough to move it without creating false confidence? |
Asset records need identity testing
The guide on equipment maintenance software and CMMS established that a position and a physical unit are not necessarily the same thing.
Ask whether an old record represents active equipment, a location, a position, a retired unit, a duplicate, a component, a financial asset or an old naming convention.
The Identity Continuity Test
- What object does this record describe?
- Will the same object exist in the new model?
- What history belongs to it?
- What history belongs to the position?
- What happens to retired or replaced units?
A clean import can still be wrong if it attaches history to the wrong thing.
PM migration is policy migration
A PM record can manufacture future maintenance demand. Before migrating an active PM, ask whether the task is still required, whether the interval and trigger are correct, whether the asset is active, whether the procedure is current and who owns it.
Rebuild the program deliberately using the preventive maintenance program guide where the old rules cannot be defended.
Migrating a bad PM rule schedules the mistake into the future.
Open work and closed history are different
Open work can represent an active obligation. Ask whether it is still required, on the correct asset, at the correct priority, with the correct owner, and whether it duplicates work already completed elsewhere.
Closed history is evidence. Ask what future decision requires this information inside the new system, using the questions in the maintenance tracking guide.
Parts
- Is the part still stocked?
- Is quantity trustworthy?
- Are duplicate item numbers present?
- Are units consistent?
- Are obsolete parts mixed with active inventory?
- Does the new CMMS need historical transactions or current inventory and opening balance?
Documents
Classify each document before moving it. This guide does not provide legal retention advice.
- Current operating document
- Historical evidence
- Duplicate
- Superseded
- Unknown
East County AWP shows deliberate data creation
East County AWP expects project data collected through design, construction and startup to be aggregated, quality reviewed and standardized into a format usable in both an electronic operations manual and the CMMS.
Its planned conversion covers facility asset and equipment data, pipeline asset data, maintenance procedures and tasks, equipment O&M manuals, testing and calibration reports, and spare parts and materials inventory. The conversion is expected to be phased as construction progresses and additional data becomes available.
The lesson is important: good migration can begin before there is a legacy CMMS. It is a data-design problem.
The Migration Funnel
The Migration Funnel is a CMMSBuyersGuide framework. Nothing jumps directly from source to production.
SOURCE DATA → PROFILE → CLASSIFY → CLEAN / TRANSFORM → MAP → TEST LOAD → VALIDATE → ACCEPT → PRODUCTION
Validation is not row counting
A migration can move every row and still fail. Test:
- Work history lands on the correct asset
- PMs generate against correct equipment
- Part quantities reconcile
- Parent and child relationships survive
- Documents open
- Open work remains actionable
- Meters make sense
- Retired assets are distinguishable
Migration completeness asks whether the data arrived. Migration validity asks whether the maintenance meaning survived.
Meaning Preservation
Meaning Preservation is a CMMSBuyersGuide framework. For important migrated objects test five properties.
| Property | Question |
|---|---|
| Identity | Did the correct object arrive? |
| Relationship | Are its connections intact? |
| State | Is current state correct? |
| History | Is history attached appropriately? |
| Behavior | Does the record behave correctly in the new CMMS? |
Archive is a valid destination
Not migrating data does not require deleting it. Some information can remain in a read-only archive, a legacy database, a document repository or a controlled export.
The choice is not migrate or destroy. Archive is an information architecture decision.
The Historical Depth Test
What decision becomes worse if we cannot see this record inside the new CMMS?
If the answer is unclear, determine whether searchable archival access is sufficient. Integrated history may matter for repeat failures, repair or replace analysis, compliance, warranty or lifecycle cost depending on the operation.
Cutover
Define the freeze point, delta migration, open-work handling, inventory reconciliation, new records created during transition, final validation and recovery plan.
Place these steps inside the wider implementation plan so acceptance and cutover readiness are tested together.
A migration plan has to explain what happens between the last extract and the first live work order.
Data ownership after migration
Assign continuing ownership for assets, PM, parts, codes, users, documents and meters.
Where records cross a system boundary, agree the authority questions in the CMMS integrations guide before go-live.
Migration quality has an expiration date unless someone owns the data afterward.
Migration worksheet
For each source record, complete the worksheet and then choose a disposition: migrate, transform, rebuild, archive, retire or verify first.
- Source
- Object
- Authority
- Current quality
- Day-one necessity
- Historical value
- Disposition
- Transformation
- Validation method
- Owner
Final perspective
CMMS migration is a decision about what maintenance truth deserves to survive into the new operating model.
Migration should preserve useful maintenance truth, not reproduce historical uncertainty at higher speed.
Migration mapping begins with the destination, not the spreadsheet.
Migrating a bad PM rule schedules the mistake into the future.
Migration completeness asks whether the data arrived. Migration validity asks whether the maintenance meaning survived.
The choice is not migrate or destroy.
Sources
- Alexandria Renew Enterprises — RFP No. 22-001, Provision, Implementation and Maintenance of CMMS
States that the quality of data in the current AlexRenew CMMS is in many cases questionable or incomplete, making it unclear if data migration is a useful effort. The data loading task requires reviewing the data, identifying gaps and obsolete data such as retired or decommissioned assets, checking accuracy, and loading all relevant data.
- East County Advanced Water Purification Joint Powers Authority — CMMS Request for Proposals
Data conversion appendix describes aggregation, quality review and standardization of project data into a format usable in an electronic operations manual and the CMMS, lists conversion categories including facility asset/equipment data, pipeline asset data, maintenance procedures and tasks, O&M manuals, testing and calibration reports and spare parts inventory, and anticipates phased conversion as construction progresses.