Skip to content

Legacy system replacement

Your planning tool was modern once, and now only one person can restart it. We build its replacement while it keeps running.

  • Free 30-minute call
  • No commitment
  • You own the code
Tools
Chosen per problem
Used in
Projects across all five problem families
Delivery
Documented source code, yours to keep

In short: Legacy planning software replacement means moving from an old, hard-to-maintain planning system to a new one without stopping operations. The new system runs alongside the old one on the company’s own data and takes over only once it has proven itself.

The problem

Your planning tool was modern once. Today only one person knows how to restart its server, and the source code may be gone. If that person is off sick in planning week, no plan gets made. That’s an operational risk. Replacing the tool feels even riskier, so it stays.

What changes

Today, your operation hangs on one person and one ageing server. With our solution, it runs on a system your team can run, understand and extend. You swap a single point of failure, one part that stops everything when it breaks, for something you control. Replacing the old tool is less disruptive than you think.

How it works

We migrate with shadow running. The new system runs in parallel with the old one before cutover, the day you switch for good. There’s no big-bang switch, where everything changes overnight, and no break in operations. We check that every function of the old tool is covered.

We migrate the data and validate it, so nothing is lost or changed on the way. We measure how fast the new system is and how good its plans are, compared with the old one. And we train your team. The switch happens only when the new system has proven itself against the old one on your own data.

What “proven itself” means, in writing

Software developers call the gradual route the strangler fig pattern. The name comes from an essay by the software author Martin Fowler. A strangler fig grows around an old tree, bit by bit, until it stands on its own. The new system takes over one function at a time, while the old one handles the rest. Fowler is blunt about the alternative, replacing everything at once: such full rewrites fail most of the time. An old advanced planning and scheduling (APS) system splits well this way, module by module.

Before the parallel run starts, we agree on the test with you. Both systems get the same input each planning cycle. We compare violated rules, cost, run time and how often you had to override each plan. For each criterion, we set the value the new system must reach, and in how many planning cycles. Then you decide from numbers when to switch the old system off.

The honest boundary: if the old tool still does its job and a second person can learn to run it, replacing it may not pay yet. Then we document it, help train the backup, and you revisit the question later.

When it isn’t the answer

The honest boundary: if the old tool still does its job and a second person can learn to run it, replacing it may not pay yet. Then we document it, help train the backup, and you revisit the question later.

Common questions.

Something else? Ask us directly.

Until the agreed criteria have been met for the agreed number of cycles. For a weekly plan, say four to eight weeks, including at least one difficult week. Month-end or holiday peaks belong in the test, because that’s where old tools hide their special cases. The length is written down before the run starts.

Then we learn its behaviour from the outside. We record what goes in and what comes out over many planning runs, and talk to the people who use it. Hidden rules show up as patterns in its plans. The parallel run then confirms that the new system reproduces the parts you want to keep.

Usually, yes, and it’s the safer route. Martin Fowler calls this the strangler fig pattern: the new system takes over one function at a time. Forecasting, scheduling and reporting can each move on their own date. Each step is small enough to roll back if it misbehaves.

Sometimes they can, and then we’ll say so. Standard tools are built for an average problem, though. With Legacy system replacement, we start from yours: its size, its rules and the exceptions nobody wrote down. That is why the plan fits your operation better.

You don’t need either to start. We build the model from the data you’ve got, messy or not, and cleaning it up is part of the job. You get a documented system your team can maintain, and we train them until they can run it long after we’ve left.

It starts with a free 30-minute call about your operation and the model that would fit it. Then we build a working prototype and run it on your numbers. You’ll see results before you commit to anything bigger.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go