The short answer
Keeping legacy software alive to placate a vocal minority of holdout accounts is a silent killer of product velocity and corporate margins. You cannot afford to maintain two parallel infrastructures simply because the commercial team is afraid of having difficult conversations with stubborn clients. You must firmly reject the demand to extend the sunset date and force the commercial organization to manage their accounts properly.
As the Vice President of Product, your mandate is to push the platform forward, allocate engineering capital to future revenue streams, and eliminate technical debt. The VP of Account Management is trying to avoid short-term customer friction by taxing your long-term engineering resources. You must expose the actual, unvarnished cost of maintaining the legacy platform and force the commercial team to pass that exact cost onto the holdout customers.
When customers realize that staying on obsolete software will cost them a massive premium, their refusal to migrate magically evaporates. You must change the incentive structure so that the commercial team and the clients feel the pain of delay, rather than your engineering department.
Why this question is a trap
The trap is the illusion of free maintenance. The VP of Account Management frames keeping the legacy platform alive as a simple flip of a switch that prevents churn and keeps revenue stable. They ignore the harsh reality that maintaining legacy code requires dedicated engineering headcount, constant security patching, redundant server costs, and fragmented product focus.
If you agree to keep the legacy platform alive, you permanently degrade the velocity of your core roadmap. Your best engineers will quit because they are stuck maintaining obsolete code instead of building new features. Furthermore, the commercial team will never actually force the migration because you removed the hard deadline. The legacy platform will become a permanent, expensive zombie that drains margin and blocks innovation.
By demanding that you carry the burden of their commercial timidity, the account management team avoids doing their job. They want you to subsidize their retention numbers with your engineering budget. You must reject this dynamic entirely and force them to do the hard work of migrating their book of business.
What most people say
Most product leaders try to plead for understanding and ask for favors. They say something like, "We really need to shut it down next quarter because it is taking up too much engineering time. Can you please push the clients harder to migrate so we can stick to the schedule?"
This response is weak, ineffective, and practically guarantees failure. Pleading with sales or account management never works because their incentives are misaligned with yours. They are incentivized to retain revenue with the least amount of friction possible. If you present the shutdown as a product preference rather than an immovable physical reality, they will continue to stall the migration. They will escalate to the CEO and claim that you are trying to force churn for the sake of your own convenience. You will lose the argument and the platform will live on forever.
What to say instead
"Maintaining the legacy platform costs us three full-time engineers and fifty thousand dollars a month in redundant infrastructure. The sunset date is hard-coded for next quarter. We have built automated migration tooling, but if these two hundred accounts refuse to move, we must implement a twenty percent legacy maintenance surcharge to fund the obsolete servers."
This script forces total commercial accountability. You start by quantifying the exact drain on resources in plain financial terms. By naming three engineers and fifty thousand dollars, you make the hidden costs visible to the commercial leader. You translate technical debt into a language they understand.
You establish the sunset date as an absolute reality, not an opening for negotiation. Then, you offer the commercial lever. You do not just tell them to deal with the angry clients. You introduce the legacy maintenance surcharge. This forces the VP of Account Management to go back to the clients and explain that staying on the old platform will cost them a massive premium. Almost instantly, customers decide that migration is not so difficult after all. You solve the problem by transferring the financial pain to the people refusing to move.
The phrase to anchor on
Implement a twenty percent legacy maintenance surcharge.
How to deliver it
Deliver this response with absolute operational finality and total emotional detachment. Lean forward slightly when you quantify the cost of the engineers and the servers. You are delivering a financial reality check, and your body language must reflect the seriousness of those numbers.
When you introduce the maintenance surcharge, your tone should remain completely matter-of-fact. It is not a punishment for bad behavior. It is simple economics. Maintain steady eye contact and do not blink when you state the twenty percent figure. Let the commercial leader process the fact that they have to sell a massive price increase to their most stubborn accounts. Do not apologize for the inconvenience.
Mistakes that cost you the room
The biggest mistake is offering a compromise timeline. If you say that you can give them three more months to get everyone moved over, you lose all credibility. In three months, they will return with the exact same excuse and ask for another extension. You must hold the original sunset date with absolute rigidity.
Another error is failing to provide adequate migration support. If you just shut the platform down without building automated tooling, exporting guides, or dedicated support documentation, you are being a negligent product leader. You must arm the commercial team with the tools to make migration easy, so they have no excuse for failure.
Finally, do not get dragged into a debate about specific account sizes or logos. The VP of Account Management will inevitably claim that one of the holdouts is a Fortune 500 company and you cannot risk losing them. It does not matter. If they are truly a massive enterprise, they can easily afford the maintenance surcharge to fund their own delay.
Practice plan
First, memorize the exact cost metrics of your legacy platform. You must be able to rattle off the infrastructure and headcount costs without looking at notes. You need these numbers as ammunition.
Second, practice introducing the surcharge concept naturally. It must sound like a standard corporate policy that has already been decided, not a threat you just invented on the spot to win an argument.
Finally, run the drill in the Talk Rightly studio. Focus on eliminating any defensive posturing. You are solving a complex business problem with a simple pricing lever. Project the confidence of an executive who knows exactly how to drive platform modernization.