PackFields
Try the demo Get early access
CMMS data migration cleanup

Send us the CMMS data mess. You approve the import file.

The nameplate photos your techs shot in the dark. The 2019 spreadsheet nobody trusts. We rebuild it into your CMMS import file — every uncertain value flagged, never guessed.

PackFields is a CMMS migration data cleanup service. We read your nameplate photos and old asset spreadsheets, match every value against your approved reference lists, flag every uncertain value for your review, and deliver a clean import file for Fiix, Maximo, eMaint, SAP PM, or Limble. Nothing imports until you approve it.

See it work on sample data Request early access
Early access · Q3 2026 We're onboarding a small number of teams this quarter
  1. 1Send your files
  2. 2We match & flag
  3. 3You approve
  4. 4Import-ready
Why accuracy matters

One serial typed wrong is one PM that never fires.

One asset that silently never gets inspected. One location code that doesn't match, so the tech can't find the equipment. That's the cell you're approving — so you approve it looking at the nameplate, not trusting a guess.

The 2019 export, the duplicate IDs, the location names that drifted — asset codes that repeat, serial columns half-empty, the same location typed four ways. We don't ask you to clean it first. Send it the way your team keeps it today.

assets_plant2.xlsxsample data · last edited 2019
How it works

You send what you have. We send back what your CMMS needs.

You send us — however your team keeps it
nameplate photos the old asset export location list your CMMS template
cmms_import.xlsx — what you receive
Rosemount 3051S · P2-PRS-007import-ready
Parker HPU-150 · P2-HYD-003import-ready
Trane RTAC 400 · criticality missingneeds you
UNIT-77 · nameplate unreadablerejected
…plus an exceptions list and the source files behind every accepted value. sample data
How we check

We match against approved manufacturer, location, and asset class lists.

Not a generic database. We match every value against the reference lists you approve — your manufacturers, your location hierarchy, your asset classes. If you don't have them yet, we draft them from your files.

A value, checked against your lists sample data

Matched, flagged, or held — never guessed.

raw value from your filesread off a nameplate photo, a spreadsheet cell, a ticket scan
"CAT" → Caterpillarmatched to your approved manufacturer alias — import-ready
"BLDG 4 MECH RM" → 2 candidatesBuilding 4 Mechanical or MCC Room — held for your review, not picked for you
"WILO" → Wilo Pumpsmatched to your approved manufacturer alias — import-ready
into your import file — with the evidenceevery accepted value is delivered alongside the photo or row it came from

You review what we flag. We do the rest.

The review room

You only touch what we flag.

Records that match approved reference lists are marked import-ready. You open the few we weren't sure of, look at the evidence, and approve. Your name goes on the import — so we make sure you can stand behind every value.

Demo project · 5 of 14 need you
Grundfos CRN 45-3P2-PMP-012 · Pump House✓ import-ready
ABB ACS580 DriveP2-WTP-LVL1-MCC2✓ import-ready
Allen-Bradley PF525"BLDG 4 MECH RM" → 2 matches◌ needs you
(unreadable nameplate)photo too blurry — never guessed✕ rejected
Caterpillar C18"CAT" → your alias✓ import-ready
Grundfos CRN 45-3same ID + serial, different location⧉ duplicate
PackFields flagged this — your call
AssetAllen-Bradley PowerFlex 525
SerialKCMP19400543✓ from photo
LocationBLDG 4 MECH RM◌ 2 candidates
Our suggestion, matched to your location list: P2-WTP-LVL1-MCC2 · Building 4 Mechanical
Once you approve it, "BLDG 4 MECH RM → Building 4 Mechanical" is saved to your project — the next batch already knows it. In the demo, this one correction matches ~15 records in Plant 1.

Nothing is marked import-ready until you approve it. Every value in your file was either matched to approved reference lists or reviewed by you.

Your deliverable

The file we deliver.

A 4-sheet workbook: the import file, the exception log, the alias table, and a source-evidence index so every value traces back.

cmms_import_cascade_p2.xlsxsample
8 matched automatically. 3 resolved by you. 1 held for your input. 1 duplicate flagged. 1 rejected — nothing silently dropped.

4 corrections. ~74 records skip review.

Every alias you approve is saved to your project. The next batch already knows it — so the pile that needs your review keeps shrinking.

Baldor → ABBmatches 31 records in Plant 1
CAT → Caterpillarmatches 23 records in Plant 1
E+H → Endress+Hausermatches 12 records in Plant 1
Pump House → P2-WTP-LVL1-PMPmatches 8 records in Plant 1
~74 records
in Plant 1 would skip review — based on 4 corrections from a 14-asset diagnostic batch in Plant 2.
From the demo project — try it yourself

A generic tool reads your nameplate the same on day 1 and day 500. Your project remembers every decision you've ever made.

Early access

Tell us about your pile. We'll scope a diagnostic batch.

A diagnostic batch covers up to 100 assets — enough to see the import file, the exception list, and how much review your data actually needs.

Your deliverable: a multi-sheet XLSX containing the import file for your CMMS, an exceptions log, an alias table of every correction, and source files organized by record so you can trace any value back to where it came from.

Prefer to just email? [email protected] — send us whatever you have.

What we promise — and what we won't do
✓
We flag, we never guess.If we're not sure, it's flagged for your review — never silently written into your file.
✓
Nothing is marked import-ready until you approve it.Every value was either matched to approved reference lists or reviewed by you.
✓
Every accepted value is delivered with its source.The nameplate photo, the spreadsheet row, the ticket scan — organized by record so you can trace any value back to where it came from.
✓
If the file won't load into your CMMS, we fix it.You get a file that imports — or we rework it until it does.
✓
Your data stays yours.Files are encrypted in transit and at rest. Processed in Canada. Deleted within 30 days of project completion. We'll sign your NDA before you send a single file.
—
We won't replace your CMMS, or become your ops department.We do CMMS asset-migration cleanup — that one job. The work ends when you have the file.
—
We won't invent data you don't have.An unreadable nameplate gets an "unreadable" flag — never a fabricated serial.

What happens next: We review your request within 2 business days and email you a diagnostic proposal — what we'd process, what we'd need from you, and what it costs. No commitment until you see the proposal. No call required — unless you want one.

Questions

Common questions.

Can you clean messy CMMS asset data — duplicates, missing serials, inconsistent locations?

That's the point — send it the way your team keeps it. We read what's readable, flag what isn't, and report what's missing. You never get a false "all clear" on a serial we couldn't actually read.

Do we need clean reference lists before starting CMMS data migration?

We can draft them from your files, and you approve them before we match anything. Building your reference lists is part of the work, not something you have to finish first.

Which CMMS do you import to?

We build to your target system's import format — Fiix, Maximo, eMaint, SAP PM, Limble, or a custom template. If the file won't load, we fix it.

My CMMS vendor offers migration support. Why would I need this?

Your vendor's migration support helps you import a clean file. We help you build the clean file. If your data is already in one spreadsheet with consistent names and complete serials, you probably don't need us — use your vendor's import tool. If your data is scattered across an old export, technician photos, and location lists that don't match, that's the work we do. We turn the pile into the file your vendor's tool expects.

How do you handle our data?

Your files are encrypted in transit and at rest, processed on infrastructure in Canada, and deleted within 30 days of project delivery. We don't train models on your data. We'll sign your NDA before the project starts — ask us on the scoping call.

Does CMMS data cleanup use AI or manual data entry?

We use AI to read the photos and spreadsheets. But you're buying a clean import file you approve — not an AI subscription. When the AI is uncertain, it flags the value for your review. It never guesses into your file.

×