Every "rewrite from scratch" proposal I have seen has the same shape: eighteen months of work, a cutover weekend, and a list of behaviours nobody knew the old system had. The old system carried years of corner cases in code nobody remembers writing.
The pattern I keep recommending is the strangler approach, named after the vine that slowly replaces its host tree:
- Put a thin layer in front of the old system (a proxy, a router, an API gateway). All traffic goes through it, and at first it just passes everything on.
- Pick one slice of functionality, small enough to finish in weeks. Build it in the new system.
- Route that slice to the new code. Keep the old path available as a fallback for a while.
- Compare: run both and diff the results (shadow mode) before you flip the switch. The differences are the unknown behaviours.
- Retire the old slice and move to the next.
What makes it work: the system is always in a shippable state, each step can be undone, and you learn the real behaviour gradually instead of all at once.
What goes wrong: the shared database. If old and new both write the same tables, you need a clear rule about who owns what, otherwise the "strangling" turns into a long argument about which system is right.
And remember that the goal is not a new system. The goal is to switch off the old one. If the old one is still running two years later "just in case", you built a second system and kept the first.