A pricing-tier sunset is not feature deprecation. It is the end of a revenue line, and it carries different stakes, different politics, and different communication. Killing a feature is a product decision. Killing a tier is a company decision that touches sales comp, customer relationships, and the org chart. Here is the operating practice for the sunset itself, the day the legacy tier ends.
The four-stage structure
The sunset spans 18 to 24 months. Less than 18 months and customer migration becomes a fire drill. More than 24 months and urgency dissolves while engineering drifts back to the legacy product. Four stages. Stage 1, internal preparation, months 0 to 6: build the coalition, rewrite comp, get internal alignment. Stage 2, strategic account migration, months 6 to 9: the Wave 1 cohort of your top 20 accounts. Stage 3, mid-market and long-tail migration, months 9 to 18: Waves 2 and 3. Stage 4, sunset day plus grace period plus post-sunset reorg, months 18 to 24.
The three communication waves
The waves are cohort-based, not uniform. Wave 1, months 6 to 9, is the top 20 strategic accounts, handled with individual CPO and CRO calls. Wave 2, months 9 to 12, is mid-market, handled with structured email plus a webinar plus self-service. Wave 3, months 12 to 18, is the long tail, handled with a public announcement and deadline-driven self-service. Treating cohorts uniformly when edge use cases need separate tracks is one of the patterns that kills a sunset.
The comp plan rewrite is the lever
Four changes. Legacy comp drops to 50% of historical, so sales thinks about the outcome alternative. Successor comp rises to 150% of equivalent ACV, so they get excited about the new motion. Legacy renewal accelerators are removed. Migration accelerators on the successor are introduced. The CRO will fight the 50%. The CEO has to hold the line. This is the lever that actually moves the migration.
The dispute mechanism and the reorg
The dispute mechanism that worked at 30 cases needs to work at 300. Hire dispute analysts ahead of need, test the unit definition at 10x projected volume, and publish the resolution timeline so customers know what to expect. After sunset, the maintenance team's roles end. Plan the reorg six months before sunset and communicate four months before. Most transition to bridge or successor roles, some take severance with full transition support, and a small team stays on for legacy data export and final billing. The fairness story is that every maintenance team member knew the runway from day one.
What to do this week
If you are 12 to 18 months from sunset, audit the five failure patterns. Have you committed to the comp asymmetry? Are Wave 1 calls scheduled with the CPO present, not delegated to account managers? Is the dispute mechanism stress-tested at scale? Is the post-sunset reorg planned? Are you watching for sales reps quietly negotiating extensions? Fix the ones you have not, starting with the comp asymmetry.