Deckard
Contact
Contact

One piece at a time

Legacy modernization

The old order system keeps running while its work moves to new software, with a way back at every step. The new software takes on what the old one never could, such as online ordering.

Start a conversationSee it step by step
Order entry on the new serviceOld path warm
Order-entry requestsNew service100%Order system0%

Order-entry requests answered by the new service, over all order-entry requests.

Steps
Differences0
Rollback switchArmed

The new system takes over in steps

Legacy modernization over four phases: order traffic moves from the order system to a new service, 30% then 70% then all of it, and the order system is switched off when nothing calls it A timeline from today through August 18, September 1 and September 15. Two ribbons show where order traffic goes: the grey ribbon, the order system, carries all of it today, then 70%, then 30%, and ends at a switch-off; the blue ribbon, the new service, starts at 30% on August 18, grows to 70% on September 1 and carries all of it from September 15. Each move is marked as reversible. The order system is switched off on October 15.
  1. A bigger share at each step30% of orders, then 70%, then all of them, and each move can be undone.
  2. The old system stays readyThe order system keeps serving until each new service matches its numbers.
  3. Switched off when nothing uses itThe last system using it moves over, then the order system goes.

Order entry moves to the new service

TodayOrder entry on a green screen

Kept running, changed only in emergencies

01Map
Screens mapped14
RequestsRerouted, unchanged
BaselineA week of orders
02Run side by side
Requests compared41,200
Order dataChecked nightly
MismatchesAlert the owner
03Move
MovesAug 18, Sep 1, Sep 15
Undo rehearsedSep 10
Change windowTue 06:00
OutMoved overRetires Oct 15
Next to moveMonth-end exports
Its first stepOct 6
ArchiveKept for reporting

How the order system gets retired

Requests are routed by Envoy, changes copied by Debezium, and the new software runs on PostgreSQL.

  1. 01An assessment of what the system does, undocumented parts included
  2. 02A switch that sends each request to the old system or the new
  3. 03Data moved over and checked line by line
  4. 04Old and new run side by side until the numbers agree
  5. 05The old system switched off, with its history archived
  6. 06A log of what moved and when
Yours at the end

order-cutover/

plan/7 parts and the order they move in

services/New order‑entry and invoicing services

parity/Rules for comparing old and new

archive/History export and its format

See it work

Where each part stands

By industry

Payables, claims and a plant scheduler, moved over in steps

Payables cutoverParallel run
Wrap the old payables screens
Calls proxied, nothing rewritten
Post invoices to both systems
412 vendor balances agree
3Aging differs on 3 vendors
Old package ages from receipt
4Move payables to the new service
Old package kept read-only

Nothing moves until both ledgers agree.

Accounting and finance

Loss intake cutoverPhone next
Notices mirrored to both cores
Clean for 3 weeksParity
Web and agent intake moved
Phone intake still on the old screens2 of 3
One claim number sequence
No duplicates across old and newShared
Print batch on old tables
Must be rewritten firstBlocking

Every channel can be sent back until nothing uses the old system.

Insurance

New scheduler, Plant 24 of 6 lines
Lines 1 to 4 moved
On the new scheduler64% of orders
Lines 5 and 6 not moved
Changeover rules being portedNext
One routing for both
No work order released twice0 doubles

Work orders released from the new scheduler, over all released.

Manufacturing and industrial

Related services

Three services order entry relies on

Every system that places orders uses one shared connection.

System integration and APIs

Changes to the new service go live only after review.

Cloud architecture and DevOps

Past orders copied over and checked row by row.

Data engineering and pipelines

All solutions

How it goes live

  1. 01 · Optional

    Map of the old system

    Everything the order system does today

  2. 02 · Optional

    Proof on one piece

    One part copied and tested; no real orders move yet

  3. 03 · Legacy modernization

    Moving it over

    Each part moved and checked, with a way back ready

  4. 04 · After the move

    Switch-off

    The order system switched off on its retirement date

Start with the system you want to replace

You get a map of what it does and the first piece to move.

Start a conversation