Legacy platform redesign without losing users
Legacy platform redesign lessons: phased rollouts, power users and change comms that keep everyone onside.

Legacy platforms are often ugly, slow and full of quirks, but they work, and people rely on them. Redesigning them is less about new screens and more about managing change.
These lessons apply whether the users are customers, members, staff or partners.
Lesson 1: learn how people really use it
- Watch power users do their daily tasks
- Map workarounds and unofficial processes
- Review support tickets and training materials
- Identify the few features used most of the time
- Find what users would hate to lose
Lesson 2: release in phases
Replace the platform section by section, starting with the areas where the biggest problems and lowest risk overlap. Run old and new side by side where possible, so users can switch back while they adjust.
- User risk
- Speed
- Learning
Our view, scored out of 5 (higher user risk is worse).
Lesson 3: protect muscle memory
- Keep key workflows and shortcuts where possible
- Move gradually rather than reorganising everything
- Keep familiar labels unless they cause confusion
- Offer a “what’s changed” guide inside the product
Lesson 4: communicate early and often
- Explain why it’s changing and what users gain
- Share a timeline and preview
- Invite power users into testing
- Provide training, videos and in-app tips
- Have support ready for launch week
Lesson 5: measure the transition
- 200
- 3
- 15%
- 3
- $50
- Hours lost during transition
- 1,350
- Cost of the dip
- $67,500
Good training and phasing shrink both the dip and how long it lasts. Budget for it.
How this looks in your industry
Illustrative examples
Closest to you
B2B
A 15-year-old ordering portal
The problem: Trade customers relied on keyboard shortcuts.
What changed: Kept shortcuts and key workflows in the new design.
Result: Power users adopted it quickly.
Closest to you
Education
A student management system
The problem: Staff feared losing familiar screens.
What changed: Released section by section with training.
Result: A smooth transition with fewer support calls.
Closest to you
Health
A clinic scheduling tool
The problem: A big-bang launch was planned.
What changed: Switched to an opt-in beta first.
Result: Issues were fixed before everyone moved.
Common mistakes
- Redesigning from screenshots, not observation
- Removing features power users depend on
- A surprise launch
- No way back if something breaks
- Ignoring the productivity dip
Key takeaways
- Observe real use first
- Phase the release
- Protect familiar workflows
- Communicate and train
Frequently asked questions
How do we handle users who resist change?
Involve them early, show what they gain, and keep what they value. Resistance often drops once people help shape the change.
Should we migrate data all at once?
Usually in stages, with careful testing, aligned to the phased release.
How long should old and new run together?
Long enough for most users to switch — often weeks to a few months.
Your next step
Modernise without losing your users
We redesign legacy platforms in phases, with research, testing and change support built in.
Explore platform redesign