Replacing Spreadsheets with a Modern CMMS: A Practical Migration Plan

Most small-to-mid-sized public works departments still run on spreadsheets. A shared Excel file with a tab per division, color-coded rows, and a dozen comments where someone tried to capture a status change three years ago. It works — until the foreman who maintains it retires, until two crews edit it at once, until the council asks for a report and someone spends their Saturday building it.

You don't need a year-long enterprise project to leave that behind. A division-by-division migration plan gets you from spreadsheet to a real CMMS in weeks, not quarters. Here is the plan that has worked repeatedly.

Why migrations fail (and how to not be that one)

Migrations fail for one of three reasons:

1. Big-bang scope. Trying to migrate every division, every asset, every PM, and every historical work order at once. The team burns out and nobody trusts the new system because nothing is fully there.
2. Data perfectionism. Six months spent cleaning a spreadsheet before importing a single row. The cleanup never finishes.
3. No champion. The vendor handed you software and walked away. Nobody internally owns the rollout.

Avoid all three by going division-by-division, importing what you have, and identifying one internal champion before kickoff.

The four-phase plan

Phase 1: Pick the division (week 0)

Pick the division that hurts the most or the one with the most willing supervisor — usually Streets or Water. Do not start with the easiest. Start where success will earn the most trust. The hard division proves the platform.

Output: one division named, one supervisor identified as champion.

Phase 2: Tenant setup and import (weeks 1–2)

Stand up the tenant. Configure roles, the chosen division's categories and SLAs, integrations the team already uses (ESRI, SeeClickFix, telematics), and notification channels. In parallel, import:

• The asset registry — even if the spreadsheet is messy. Cleanup happens in the new system.
• The active backlog of open work orders. Not historical, just open.
• User accounts for that division.

Skip historical closed work orders. Nobody will look at them. If you absolutely need them later, they can be archived as PDFs.

Output: tenant configured, one division ready to go live.

Phase 3: Pilot with that division (weeks 3–4)

Go live with the chosen division while the spreadsheet still exists in parallel. The supervisor and one or two crews work entirely in the CMMS. After two weeks, run a side-by-side: did anything fall through? What did the system do faster than the spreadsheet? What needs configuration tweaks?

Common findings in this phase:

• Categories need to be reorganized once people use them.
• One or two custom fields are missing. Add them.
• The mobile app is the surprise hit — crews want it expanded.
• The citizen portal already deflected three calls.

At the end of week 4, retire the spreadsheet for that division. The CMMS is now the system of record.

Output: one division fully on the platform, supervisor confident, crews using mobile.

Phase 4: Roll the next division (weeks 5–8, then repeat)

Bring on the next division. Reuse what you learned. Each subsequent division typically takes less time than the first because the platform is already configured, the integrations are already wired, and the supervisor sees the previous division's success.

For a typical 4–5 division department, full rollout completes in three to four months from kickoff. None of those months involve disruption — each division goes from spreadsheet to CMMS in a tight window with a parallel-run safety net.

What about historical data?

The honest answer: most of it has no operational value. The closed work order from 2019 is not informing anybody's decision today. Three rules:

• Asset registry: yes, migrate. Even imperfect, this is the foundation.
• Open backlog: yes, migrate. Active work needs to live in the new system from day one.
• Closed historical work orders: archive as a PDF or CSV. Keep them for compliance. Don't import.

This single decision saves weeks of cleanup and zero operational value is lost.

The change-management piece

The technical migration is the easy half. The harder half is getting the long-tenured technician who has used the spreadsheet for 12 years to use the new app. Three things move the needle:

1. Make the new system faster than the old one for that technician. Voice notes instead of typing. Photo attachments instead of "describe the issue." One-tap status changes. Real offline mode.
2. Eliminate the parallel system within four weeks. If the spreadsheet still exists at week 8, half the crew will keep using it. Set the retirement date and hold to it.
3. Have the supervisor lead by example. If the supervisor still asks "did you log it in the spreadsheet?", the crews will keep logging in the spreadsheet.

What success looks like at month four

• Every division is on the platform.
• The shared spreadsheet is archived, not edited.
• Crews are creating and closing work orders from the field.
• Citizens are submitting requests through the portal and getting auto-updates.
• The supervisor produces the monthly council report in five minutes.
• Nobody is asking "should we go back?"

That is a realistic outcome — not the vendor's fantasy timeline, but not a multi-year project either.

---

WorkmanIQ was designed for division-by-division rollout, with no-cost pilots for qualifying agencies. See how it works →