Moving off spreadsheets: a migration sequence that keeps managers on side

Nobody defends the spreadsheet-based performance process, but plenty of people quietly depend on it: the version they control, the formula only they understand, the flexibility to fudge a deadline. A migration that ignores this fails on adoption even when the tooling is better in every measurable way. This guide sequences the move to minimise resistance — one workflow at a time, each one paying for the next.

Why big-bang migrations stall

Switching goals, reviews, probation and feedback simultaneously multiplies change on every manager at once, and the first cycle in the new system carries every teething problem at maximum visibility. One bad experience becomes the story of the platform. Sequenced migrations produce the opposite dynamic: a small win, then a constituency asking for the next piece.

Phase 1: Probation (weeks 1–4)

Start with probation. The volume is small — only new joiners — so few managers are affected at once. The pain is real and acknowledged: everyone has a story about a lapsed confirmation. The deadlines are legally meaningful, which makes the case self-evident. And the workflow is contained enough to configure in days. When the system catches its first would-have-lapsed confirmation, you have your proof point, and it travels by word of mouth.

Phase 2: One review cycle, one population (weeks 5–16)

Run the next scheduled review cycle in the platform for one department — ideally one whose leader wants to go first; enthusiasm at the pilot stage is worth more than representativeness. Replicate the existing criteria and process as closely as the platform allows, resisting the urge to redesign everything at once: migrating and redesigning simultaneously doubles the change and halves the ability to tell which problems came from which. Capture the before/after numbers that matter to managers — hours spent chasing forms, days from cycle open to close, completion rate.

Phase 3: Goals and feedback (the following quarter)

With a cycle completed, add the connective tissue. Goals entered at the start of the period flow into the next review automatically — this is the moment managers see why the platform beats the spreadsheet, because the review pre-populates with evidence instead of starting blank. Continuous feedback follows naturally once people see comments resurface in reviews. This phase converts managers from complying to preferring.

Phase 4: Everyone, and the deeper modules (quarter three)

Roll the proven cycle out to remaining departments, using pilot managers as references — their numbers and war stories, not HR's slides. Only then add calibration views, analytics and talent modules. These reward accumulated data, so sequencing them last means they arrive with something to show.

Handling the holdouts

Every migration has a manager who keeps a shadow spreadsheet. Do not fight it in month one; the shadow copy dies on its own the first time the platform answers a question the spreadsheet cannot — who has not completed reviews, what did we tell this employee at their 60-day check-in, how does this team's distribution compare. Pick those moments deliberately: answer a leadership question from the platform, in the meeting, in seconds. That demonstration converts more holdouts than any mandate.

What to keep from the spreadsheet era

Export and archive the historical files, but do not bulk-import years of inconsistent scores — bad data poisons trend views. Import the current state: active goals, open probations, last cycle's final scores. History stays queryable in the archive; the platform starts clean and trustworthy. Within two cycles it will hold more usable history than the spreadsheets ever did.