Hi Adam! I respect your opinion, but definitely disagree. I can’t think of a single product that has ever kept every single legacy feature, and managed to stay afloat. I’m not suggesting that you gut your entire product and rip the rug out from under your customers. (That may have been unclear, I’ll definitely expand on this tonight to clarify some points.) My point was that you can’t keep such a death grip on every single one of your legacy features that your product gets frozen in time and it becomes irrelevant. I worked for a company that attempted the dual option scenario, and it’s a holy nightmare to manage. Every release you’re updating a code base for 2 different features, which requires double the coding, double the QA and double the support documentation, training and support. The key to removing legacy features is creating better solutions to take their place. It takes significant planning, research and usability testing to make the transition as painless as possible for your customer base.