There's this classic article on the topic: https://www.joelonsoftware.com/2000/04/06/things-you-should-...
(I think this article should be the new classic.)
> My takeaway from these stories is this: Once you’ve learned enough that there’s a certain distance between the current version of your product and the best version of that product you can imagine, then the right approach is not to replace your software with a new version, but to build something new next to it — without throwing away what you have.
Trello isn’t a rewrite of FogBugz. It’s a brand new product.
I can’t believe FogBugz didn’t share any code with CityDesk.