Strangler pattern — phased decommissioning
The new system grows module by module alongside the old one. We place a routing layer in front of the old application so that we can redirect each individual part — the simple modules first, then the complex ones — to the new codebase as soon as it is ready. The old system keeps running for as long as it still contains parts that have not been replaced, and is switched off once the last flow has been taken over. This approach — described by Martin Fowler as the strangler fig pattern — works particularly well for large applications where a one-off rewrite is unfeasible or too risky.
In practice, this means your end users work with two screens for months (or, better, with a single screen that gradually switches over under the hood) while the old system is emptied step by step. That gives your organisation time to learn the new way of working, and there is never a moment when everything switches at once. No big bang, no weekend when operations grind to a halt, no all-or-nothing risk.