Technology

The System Went Live and Nobody Uses It: Change Management in Migrations

A migration can go live on time and still fail if people keep working the old way. Why it happens, what signals to watch and how to plan for adoption.

By Randall Cascante ValverdePublished 3 min read

The project finished on time. The new platform is live, the data was migrated, and the vendor delivered what was agreed. Three months later, half the team is still using the same old spreadsheet, reports are built by hand, and someone asks to “go back to the old system, at least for lookups.”

It’s one of the most expensive and least visible failures: technically the project went well, but the investment isn’t paying off. And it almost always has the same cause: the technology was planned, and adoption was taken for granted.

Why people don’t adopt

It’s rarely stubborn resistance. The most common causes are concrete:

1. Nobody explained why. People know there’s a new system, but not what problem it solves for them. Without a reason of their own, the change is just extra work.

2. The new system is slower for the everyday task. It may be better overall and worse for the person who uses it a hundred times a day. If testing didn’t catch that, it shows up in production as rejection.

3. Training was an event, not a process. A two-hour session before go-live isn’t enough. People learn when they use the system with their real cases and have someone to ask.

4. The old system is still available. As long as the familiar option exists, most people will use it. Running both for a while is reasonable; running both with no end date isn’t.

5. Leaders don’t use it. If leadership keeps asking for reports in the old format, the message to the team is clear: the new system is optional.

Early signs that adoption is going badly

There’s no need to wait three months. In the first few weeks you can already see:

  • Transaction volume in the new system grows more slowly than planned.
  • Help desk questions are always the same, and nobody turns them into fixes or guides.
  • Side files appear “to keep track” of what the system already does.
  • Project metrics talk about deliverables, but none talk about usage.

How to plan for adoption from the start

Change management isn’t an activity tacked onto the end of the schedule. It works when it’s part of the plan from day one:

  1. Define adoption in numbers. For example: 90% of users record their transactions in the new system 60 days after go-live. What isn’t measured isn’t managed.
  2. Identify whose work changes, and by how much. Not every group experiences the change the same way. An impact map by role lets you focus effort where it’s hardest.
  3. Involve real users in testing. Not just to find bugs, but to catch what will be slower or confusing day to day, while it can still be fixed.
  4. Name champions on every team. One person per area, trained early, who answers questions right next to their colleagues. It works better than any manual.
  5. Stay close after go-live. The first weeks in production matter most. Reserve project team time to be available, measure usage, and adjust.
  6. Set a shutdown date for the old system. And announce it well in advance. Running both indefinitely is the surest way for nothing to change.

Adoption is part of the result

A technology project doesn’t end when the system goes live, but when the organization works differently because of it. Measuring success only by the go-live date measures half of it.

If you’re about to start a migration or an implementation, or already have a platform that never quite took off, explore our technology transformation and adoption service line, or start with a two-week express assessment. You can also download our free go-live plan template.

Back to insights
Let's talk