Will raising prices on existing customers cause churn?

Some, but far less than most founders fear if you give notice, apply the change at the next renewal rather than mid-cycle, and consider grandfathering your earliest or most loyal customers. The biggest avoidable churn comes from surprise mid-cycle charges and from canceling and re-subscribing people, not from the increase itself.

Should I grandfather existing customers?

Often yes for your earliest cohort or a small set of high-value accounts, as goodwill. You do not have to grandfather everyone. A common middle path is to raise prices for most existing customers at their next renewal while excluding a chosen group who keep their old rate.

How do I apply the new price to existing subscribers in Stripe?

Create a new price and move existing subscriptions onto it, scheduled for each subscriber's next renewal (or immediately with no proration). You never cancel and recreate the subscription. For many subscribers, a bulk tool does this in one pass with a preview and one-click reverse.

How to Raise SaaS Prices Without Losing Customers

The short version: Most of the churn people blame on a price increase actually comes from how it was rolled out, surprise mid-cycle charges, no warning, or canceling and re-subscribing customers. Give notice, apply the new price at each customer's next renewal, grandfather a chosen few if it helps, and make the change in Stripe without ever canceling a subscription. Done that way, a well-judged increase loses very few customers and lifts revenue immediately.

The increase is rarely the problem. The rollout is.

Founders delay raising prices for years because they picture a wave of cancellations. In practice, customers who get real value rarely leave over a fair, well-communicated increase. What actually drives people out is feeling ambushed: a charge they did not expect, a bigger number with no explanation, or being told to re-enter their card and sign up again. Fix the rollout and the increase itself is usually a non-event.

Decide who pays the new price

You do not have to treat everyone the same. The three common choices:

Everyone, at their next renewal. The simplest and most common. Existing customers move to the new price on their own billing date.
Everyone except a grandfathered group. Keep your earliest cohort or a handful of high-value accounts on their old rate as goodwill, and raise the rest. This buys loyalty where it matters most while still lifting overall revenue.
Only new customers. The safest and the slowest. Fine if you are nervous, but you leave money on the table from your existing base.

For most businesses the middle option is the sweet spot. (We go deeper in how to grandfather existing customers.)

Give notice, and frame it around value

Tell customers before it happens, ideally a billing cycle ahead. Keep it short and honest: what the new price is, when it takes effect (their next renewal), and a line on what they are getting for it. You do not need to over-apologize. People respect a business that prices with confidence. The goal of the email is no surprises, so the renewal charge matches what they were told.

Apply it at the next renewal, not mid-cycle

This is the single biggest lever for avoiding angry emails. When you change a subscription's price, you choose whether it bills immediately with a prorated charge, or simply takes effect at the next renewal. For an across-the-board increase, choose the next renewal (or apply it immediately with no proration). Either way, nobody gets a mid-cycle charge, they just see the new amount when they would have been billed anyway. (More on the mechanics in bulk-updating Stripe prices safely and scheduling a price increase.)

Never cancel and re-subscribe

Some guides suggest canceling subscriptions and having customers sign up again at the new price. Do not. It forces everyone to re-enter payment details, resets their billing history, and quietly loses every customer who does not bother to come back. Always re-price the existing subscription in place, same subscription, same billing date, no action required from the customer.

Doing it across your whole base

Changing one subscription in Stripe is easy. Changing hundreds by hand is not, and it is where mistakes (wrong proration, missed customers) creep in. PricePilot Migrate Pro applies the new price to your existing Stripe subscriptions in bulk: preview exactly who is affected and the MRR impact for free, exclude the customers you want to grandfather, choose next-cycle or immediate-no-proration timing, and reverse in one click if you change your mind. It works with plain Stripe subscriptions and the ones created by Paid Memberships Pro and MemberPress.

See your price increase before you run it

Connect your Stripe account and preview the affected customers and your MRR change for free. Test mode is free end to end.

Open Migrate Pro →

Frequently asked questions

Will I lose customers when I raise prices?

Far fewer than you expect if you give notice, bill the new price at the next renewal instead of mid-cycle, and grandfather a chosen few. Most avoidable churn comes from surprise charges and cancel-and-resubscribe, not the increase itself.

Do I have to grandfather anyone?

No, but it is a cheap goodwill move for your earliest or highest-value customers. A common path is to raise prices for most existing subscribers while excluding a small group who keep their old rate.

How do I apply it without canceling subscriptions?

Create a new price and move existing subscriptions onto it at each customer's next renewal. The subscription, billing date, and access stay intact. For many subscribers, a bulk tool does it in one pass with a preview and one-click reverse.