Skip to main content

How to plan a legacy system replacement

Throwing your old screen into the sun doesn't replace your legacy system. Here's what does: audit, requirements, data migration, parallel running and change management.

1:01 Transcript below

Chapters

  1. 0:00 Into the sun
  2. 0:12 System audit
  3. 0:21 Requirements
  4. 0:29 Data migration
  5. 0:35 Parallel running
  6. 0:42 Change management
  7. 0:49 What comes next

Buying a new system doesn’t replace the old one on its own. This short film walks through what does, from the audit and the requirements to moving the data, running both side by side and getting the team using it.

For the full version, read our guide on how to plan a legacy system replacement, or see how we handle legacy modernisation for clients.

Transcript

If you hurl your old screen into the sun and stick a shiny new one on the desk, you've replaced your legacy system.

But the second you switch it on, nothing's changed.

So you do a system audit and write down everything the old one does.

Now you've got a list of three hundred things, and half of them everyone hated.

So you turn that list into requirements, keeping what works and dropping what doesn't.

Now there's twenty years of data stuck in the old one.

So you plan a data migration and test it on a copy first.

Now the whole office has to switch over in one go.

So you run the old and the new side by side, that's parallel running.

Now everyone's on a system nobody's shown them.

So you train the team on it with their own work before it goes live, that's change management.

Now nobody needs the old one.

Now you add a phone app, reports that send themselves and one login for everyone.

Congratulations, you've planned a legacy replacement.