What This Template Is For
Changing your pricing is the easy part. Migrating existing customers to the new pricing without destroying trust, spiking churn, or creating a PR crisis is the hard part. Every SaaS company that has been in business for more than two years faces this problem: the pricing that got you to this point is not the pricing that gets you to the next stage.
This template walks you through the full migration lifecycle: deciding which customers get grandfathered, how long legacy pricing persists, what the communication sequence looks like, how to handle objections, and what your rollback plan is if churn spikes. It is designed for B2B SaaS companies, but the communication and grandfathering frameworks apply to any subscription business.
The Product Strategy Handbook covers how pricing changes fit into broader strategic pivots and product repositioning. For modeling the revenue impact of different migration scenarios, the ROI Calculator can project net revenue under optimistic, base, and pessimistic assumptions. The net revenue retention glossary entry explains why migration-driven churn must be tracked separately from organic churn. If you are also redesigning your tier structure, use the Feature Packaging Template alongside this one.
How to Use This Template
- Start with the Migration Impact Assessment. Quantify how many customers are affected, by how much, and in which direction (price increase, price decrease, or lateral move).
- Define your grandfathering policy. Decide who keeps their old pricing, for how long, and under what conditions.
- Build the communication plan. Map every touchpoint from internal announcement through customer migration and post-migration follow-up.
- Prepare the objection playbook. Anticipate the top 5 objections and arm CS and sales with responses.
- Define rollback criteria. Decide in advance what churn threshold triggers a pause or rollback.
- Execute and monitor. Track migration completion, churn, and sentiment weekly for the first 90 days.
The Template
Migration Impact Assessment
New pricing summary:
| Plan | Old Price | New Price | Change | Direction |
|---|---|---|---|---|
| [Plan 1] | $[X]/mo | $[X]/mo | [+/-X]% | [Increase / Decrease / Lateral] |
| [Plan 2] | $[X]/mo | $[X]/mo | [+/-X]% | [Increase / Decrease / Lateral] |
| [Plan 3] | $[X]/mo | $[X]/mo | [+/-X]% | [Increase / Decrease / Lateral] |
| Enterprise | Custom | Custom | Varies | [Case-by-case] |
Customer impact by segment:
| Segment | Count | Avg Price Change | Total ARR Impact | Risk Level |
|---|---|---|---|---|
| [Plan 1, monthly] | [N] | [+/-$X]/mo | [+/-$X]K ARR | [High/Medium/Low] |
| [Plan 1, annual] | [N] | [+/-$X]/mo | [+/-$X]K ARR | [High/Medium/Low] |
| [Plan 2, monthly] | [N] | [+/-$X]/mo | [+/-$X]K ARR | [High/Medium/Low] |
| [Plan 2, annual] | [N] | [+/-$X]/mo | [+/-$X]K ARR | [High/Medium/Low] |
| [Enterprise] | [N] | Varies | [+/-$X]K ARR | [High/Medium/Low] |
| Total | [N] | - | [+/-$X]K ARR | - |
Customers receiving a price decrease: [N] ([X]% of total)
Customers receiving a price increase: [N] ([X]% of total)
Customers with no change (lateral): [N] ([X]% of total)
Grandfathering Policy
| Customer Segment | Policy | Duration | Conditions |
|---|---|---|---|
| Annual contract (active) | Grandfathered at current price until contract renewal | Until renewal date | Auto-renews at new pricing unless negotiated |
| Monthly customers (<12 months) | Grace period at current price | [X] months from announcement | Must choose new plan before grace period ends |
| Monthly customers (>12 months) | Extended grace period (loyalty recognition) | [X] months from announcement | Must choose new plan before grace period ends |
| Enterprise / custom contracts | Individual negotiation | Until contract renewal | Account manager reviews each account |
| Customers on promotional pricing | Honor promotional rate for original term | Until promo end date | Reverts to new standard pricing after promo |
| Customers who prepaid annually | Full credit for remaining prepaid period at new rate | Prorated credit applied | No penalty for mid-term migration |
Grandfathering exceptions:
- Customers who expand (add seats, upgrade tier) lose grandfathered pricing on the new plan
- Customers who contract (remove seats, downgrade) move to new pricing immediately
- Customers who cancel and resubscribe within [X] days get new pricing (no grandfathering on re-sign)
Communication Plan
Phase 1: Internal Preparation (Weeks -4 to -2)
| Date | Action | Audience | Owner |
|---|---|---|---|
| Week -4 | Pricing change briefing document shared | Executive team | Product/Pricing |
| Week -3 | Sales team training: new pricing, talk track, FAQ | Sales | Revenue Ops |
| Week -3 | CS team training: migration playbook, objection handling | CS | CS Manager |
| Week -2 | Support team training: FAQ, escalation paths | Support | Support Manager |
| Week -2 | Finance models updated with migration scenarios | Finance | Finance |
| Week -2 | Billing system configured for new plans + grandfathering | Engineering | Engineering |
| Week -1 | Dry run: test migration emails, billing changes, pricing page | All | Project Manager |
Phase 2: Customer Communication (Weeks 0 to +2)
| Day | Channel | Audience | Message | Owner |
|---|---|---|---|---|
| Day 0 | Email (personal from CEO/CPO) | All affected customers | Announce change, explain why, link to details page | Marketing |
| Day 0 | In-app banner | All active users | "Important pricing update. Learn more." | Product |
| Day 0 | Blog post | Public | Transparent explanation of changes and rationale | Marketing |
| Day 0 | Pricing page update | Public | New pricing live with old/new comparison | Marketing |
| Day 1-3 | Personal email | Top 50 accounts by ARR | CSM/AE personal outreach with account-specific impact | CS/Sales |
| Day 3 | Help center article | All | Detailed FAQ, migration timeline, self-serve plan change | Support |
| Week 1 | Webinar/AMA | Interested customers | Live Q&A about changes | Product + CS |
| Week 2 | Follow-up email | Customers who have not responded | Reminder of timeline + link to choose new plan | Marketing |
Phase 3: Migration Execution (Weeks +2 to +12)
| Milestone | Action | Audience | Owner |
|---|---|---|---|
| Week 2 | Self-serve migration tool goes live | Monthly customers | Product |
| Week 4 | First reminder: 30 days until grace period ends | Monthly customers in grace period | Marketing |
| Week 6 | CSM check-in with all Orange/Red health score accounts | At-risk accounts | CS |
| Week 8 | Second reminder: 14 days until grace period ends | Non-migrated monthly customers | Marketing |
| Week 10 | Final reminder: 3 days until grace period ends | Non-migrated monthly customers | Marketing |
| Week 10 | Auto-migration for non-responsive customers | Remaining monthly customers | Billing system |
| Week 12 | Migration complete. Close project. | Internal | Project Manager |
Phase 4: Post-Migration Monitoring (Weeks +12 to +24)
| Metric | Frequency | Alert Threshold | Owner |
|---|---|---|---|
| Churn rate (migration-related) | Weekly | >[X]% above baseline | CS Manager |
| Support ticket volume (pricing-related) | Daily (first 30 days) | >[X] tickets/day | Support Manager |
| NPS / CSAT change | Monthly | Drop >[X] points | CS Manager |
| Revenue impact vs. projection | Monthly | >15% below base case | Finance |
| Save offer usage | Weekly | >[X]% of at-risk accounts using saves | CS Manager |
Objection Playbook
| Objection | Response Framework | Escalation |
|---|---|---|
| "My price went up 30%. That is too much." | Acknowledge the increase. Show the additional value (features, limits, support) included in the new plan. Offer annual commitment for lower effective rate. If needed, offer [X]-month transitional pricing. | CSM to CS Manager if discount >15% requested |
| "I signed up because of the old price. This feels like bait-and-switch." | Acknowledge the frustration. Explain the grandfathering period and the business rationale (investment in product, new features, infrastructure). Emphasize they have [X] months at the old rate. | CS Manager if customer threatens public complaint |
| "I want to stay on my current plan forever." | Explain that legacy plans will not receive new features or priority support. Offer a migration incentive (X% off new plan for 6 months). Show what they gain by moving. | VP CS if customer is top-50 account |
| "My budget was approved for the old price." | Offer to align migration with their next budget cycle. Extend grandfathering to match their fiscal year. Provide a budget justification document they can share internally. | AE if enterprise account |
| "I am going to switch to [competitor]." | Do not panic-discount. Ask what specifically they would lose by switching. Share a competitive comparison. If they are serious, engage the retention team with a structured save offer. | VP CS + VP Sales for accounts >$[X]K ARR |
Rollback Criteria
| Trigger | Threshold | Action |
|---|---|---|
| Churn spike | Migration-related churn exceeds [X]% in any 30-day window | Pause migrations. Extend all grace periods by 30 days. Review pricing. |
| NPS collapse | NPS drops >[X] points vs. pre-announcement baseline | Pause migrations. Survey affected customers. Adjust communication. |
| Revenue miss | Realized revenue is >[X]% below base case at Week 8 | Executive review. Consider partial rollback or adjusted pricing. |
| PR crisis | Negative press coverage or viral social media complaint | Immediate executive response. Consider public adjustment or extended grandfathering. |
Rollback process (if triggered):
- Freeze all pending migrations immediately
- Extend all grace periods by [X] days
- Executive team reviews data within 48 hours
- Communicate updated timeline to all affected customers within 72 hours
- Decide: adjust pricing, extend grandfathering, or revert entirely
Filled Example: B2B SaaS Design Collaboration Tool
Migration Context
The company is moving from per-seat pricing ($12/seat/mo Starter, $22/seat/mo Pro) to a team-based model (Team $99/mo for up to 10 users, Business $249/mo for up to 25 users, Enterprise custom). The change is driven by customer feedback that per-seat pricing discourages adding designers and stakeholders.
Migration Impact
| Segment | Count | Old Monthly | New Monthly | Change | Risk |
|---|---|---|---|---|---|
| Starter, 1-3 seats | 420 | $12-36 | $99 (Team) | +175% to +725% | High |
| Starter, 4-10 seats | 280 | $48-120 | $99 (Team) | -17% to +106% | Medium |
| Pro, 1-5 seats | 150 | $22-110 | $249 (Business) | +126% to +1032% | Very High |
| Pro, 6-15 seats | 190 | $132-330 | $249 (Business) | -24% to +89% | Low |
| Pro, 16-25 seats | 85 | $352-550 | $249 (Business) | -55% to -29% | Low (price decrease) |
| Enterprise | 35 | Custom | Custom | Varies | Low |
The problem: 420 accounts with 1-3 seats face massive price increases (up to 725%). These are mostly freelancers and solo designers. If all 420 churn, the company loses $120K ARR but gains far more from the 555 accounts that stay and expand.
The solution: Create a new Solo tier ($29/mo, 1 user) that did not exist in the original plan. This gives solo users a fair price while preserving the team-based model for multi-user accounts. The Solo tier includes core design features but not collaboration features (which solo users do not need anyway).
Communication Highlights
CEO email (Day 0): "We heard you. Per-seat pricing was punishing teams that wanted to collaborate. Starting [date], we are moving to team-based pricing so you can invite your entire team without worrying about the bill. Here is what this means for your account."
Account-specific email (Day 1-3): Each email included a table showing the customer's specific old price, new price, and what additional value they receive. Accounts receiving a price decrease got a "You are saving money" callout. Accounts receiving an increase got the grandfathering timeline and migration incentive.
Migration incentive: 20% off the new plan for the first 6 months for any customer who self-migrates within 30 days of announcement.
Results (90 days post-migration)
- 380 of 420 solo accounts migrated to the new Solo tier ($29/mo). 40 churned. Churn rate: 9.5% (below the 15% threshold).
- 92% of multi-seat accounts migrated within the 60-day grace period.
- Net revenue impact: +$340K ARR (expansion from previously seat-constrained teams more than offset the solo account price reductions).
- NPS dropped 8 points at Week 2, recovered to baseline by Week 10.
Common Mistakes to Avoid
- Announcing before internal teams are ready. If a customer calls support on Day 1 and the support rep cannot explain the change, you have failed. Budget 2-3 weeks for internal training before any external communication. Every customer-facing person needs the FAQ, talk track, and escalation path memorized.
- Auto-migrating without warning. Billing customers at a new rate without explicit notice is a trust violation. Even if it is technically allowed by your terms of service, the perception damage is not worth it. Always give 30-60 days of explicit notice with multiple reminders.
- Treating all customers the same. A solo user paying $12/mo and an enterprise paying $12,000/mo need fundamentally different migration experiences. Segment your communication and your grandfathering policy by account value and risk level.
- Not having a rollback plan. If churn spikes to 3x your baseline in the first month, you need to know exactly what you will do. Define the rollback criteria before launch, not during a crisis. The risk assessment glossary entry covers frameworks for pre-defining trigger thresholds.
- Burying the price increase behind feature announcements. Customers see through this. Lead with honesty: "We are changing our pricing. Here is why, here is what it means for you, and here is how we are making the transition fair." Transparency builds trust even when the news is unwelcome.
Key Takeaways
- Quantify the impact on every customer segment before announcing any pricing change
- Grandfathering should be generous but time-limited. 6-12 months is the standard window
- Budget 2-3 weeks for internal training before any external communication
- Personal outreach for top accounts. Self-serve migration for the rest
- Define rollback criteria before launch. Know your churn threshold and your response plan
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use