Ask HN: Rewrite of Industry Leading Application

In a recent thread [1] a lot was said about rewriting a successful application. It's an interesting subject, one I'm experiencing now. My current employer has (had?) the industry leading application. We embarked on a rewrite last year, and this comment from Gibbon1 is being realized: >> Problem with rewrites is there is the terrible gap that opens up between the old stuff which goes stale quickly, and the new stuff which isn't ready for prime time. Cash-flow then dries up right as the amount of work needed is maximal. Death follows quickly. [2] Due to lava layers and architecture, the application couldn't scale to the largest customers, and the UI was showing it's age. So, rewrite! Sales dried up because customers are waiting on the new version. The new version is over due, lots of features are missing. And we're still supporting the old version, which is a massive time sink. Release is imminent, but major features are still being changed. Has anyone seen success from this scenario, or should I ready my resume? [1] https://news.ycombinator.com/item?id=9777829 [2] https://news.ycombinator.com/item?id=9782681