Replacing Spreadsheets with a CMMS: A Practical Migration Plan

Plenty of public works departments still track their work in spreadsheets. Usually it is one shared Excel file with a tab for each division, rows colored by status, and cell comments where someone once tried to record a change. That setup holds together for a while. It starts to fail when the foreman who keeps it up retires, when two crews edit it at the same time, or when the council asks for a report and someone gives up a Saturday to build it.

Getting off the spreadsheet does not require a large enterprise project. If you move one division at a time, you can have a working CMMS in place within a few weeks for the first division and a few months for the whole department. The plan below is the one we have seen work most often.

Why migrations stall

When a migration goes badly, the cause is usually one of these three:

1. Trying to do it all at once. The team attempts to load every division, asset, PM schedule, and historical work order in one push. People get worn out, and since nothing is complete, nobody trusts the new system.
2. Waiting for clean data. The department spends six months tidying the spreadsheet before importing anything. The cleanup never ends, so the import never starts.
3. Nobody owns it. The vendor delivers the software and leaves, and no one inside the department is responsible for the rollout.

You can avoid all three by moving one division at a time, importing the data you have as it stands, and naming an internal champion before kickoff.

The four-phase plan

Phase 1: Pick the division (week 0)

Choose the division with the most pain or the supervisor who is most willing to try something new. That is usually Streets or Water. Resist the urge to start with the easiest group. A win in a difficult division earns more trust from the rest of the department than a win in an easy one.

Output: one division chosen and one supervisor named as champion.

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

Set up the tenant. Configure user roles, the categories and SLAs for the first division, the integrations the team already relies on (ESRI, SeeClickFix, telematics), and how notifications go out. While that is happening, import the following:

• The asset registry, messy or not. You can clean it up inside the new system.
• Open work orders from the current backlog. Leave the closed ones out.
• User accounts for the people in that division.

Do not import historical closed work orders. In practice nobody goes back to them, and if you need them later you can keep them as archived PDFs.

Output: the tenant is configured and the first division is ready to go live.

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

Take the first division live and keep the spreadsheet running alongside it. The supervisor and one or two crews do all of their work in the CMMS. After two weeks, compare the two. Check whether anything was missed, where the new system saved time, and what configuration needs adjusting.

Things that commonly come up during the pilot:

• Categories get reorganized once people start using them day to day.
• One or two custom fields turn out to be missing, so you add them.
• Crews like the mobile app more than anyone expected and ask to use it for more of their work.
• The citizen portal has already handled a few requests that would otherwise have been phone calls.

At the end of week 4, stop using the spreadsheet for that division. From then on, the CMMS is the system of record.

Output: one division fully moved over, with a confident supervisor and crews working from their phones.

Phase 4: Move the next division (weeks 5 to 8, then repeat)

Start the next division and apply what you learned from the first. Later divisions tend to go faster. The platform is already configured, the integrations are already connected, and the next supervisor has watched the first division make the switch.

A department with four or five divisions usually finishes the full rollout three to four months after kickoff. Operations keep running during that time because each division switches over in a short window, and the spreadsheet stays available as a backup until the pilot is done.

What about historical data?

Most historical data has little day-to-day use. A work order closed in 2019 is not guiding anyone's decisions now. We suggest three rules:

• Asset registry: migrate it. It is the foundation for everything else, even with gaps.
• Open backlog: migrate it. Active work needs to be in the new system from the first day.
• Closed work orders: archive them as PDF or CSV. Keep them for compliance purposes, but do not import them.

Following these rules saves weeks of cleanup, and you give up nothing that crews or supervisors use in their daily work.

Getting people to change

The technical side of the migration is the easier part. The harder part is getting a technician who has used the spreadsheet for 12 years to use a new app instead. Three things help most:

1. Make the new system quicker for that technician than the old one. Let them record voice notes instead of typing, attach a photo instead of describing the problem, and change a status with one tap. It also needs to work offline when there is no signal.
2. Shut down the parallel system within four weeks. If the spreadsheet is still open at week 8, half the crew will still be using it. Pick a retirement date and stick to it.
3. Have the supervisor use it first. Crews follow the supervisor. If the supervisor keeps asking whether something was logged in the spreadsheet, that is where the crews will keep logging it.

Where you should be at month four

• All divisions are working in the platform.
• The shared spreadsheet has been archived and nobody edits it.
• Crews open and close work orders from the field.
• Residents submit requests through the portal and receive automatic status updates.
• The supervisor can pull the monthly council report in about five minutes.
• Nobody is asking to go back to the old way.

That timeline is realistic. It is slower than the fastest schedules some vendors promise and much faster than a multi-year implementation.

---

WorkmanIQ was built to be rolled out one division at a time, and qualifying agencies can run a pilot at no cost. See how it works →