Switching Nonprofit Processors Without Breaking Recurring Gifts

A processor switch puts every stored donor card in play.

Switching nonprofit processors starts with a written request: ask your current provider to export stored donor cards as a tokenized file. DonorPerfect, citing Double the Donation in 2023, said 94% of recurring donors preferred monthly gifts, so one missed cycle touches nearly all of them. Get that answer before any rate quote reaches your board.

Sustainers are the asset at stake. On the NPFX fundraising podcast in 2026, Dave Raley said organizations expect to lose 80% of new donors the following year, while the average sustainer is worth 5 to 10 times a single-gift donor in first-year value. Recurring donors, he added, are 6 times more likely to leave a planned gift.

The base keeps widening. In 2024, a study of more than 2,000 nonprofits reported that supporters choosing monthly gifts rose 127% over its five-year window, even as active supporters overall fell about 3.5%. In that 2024 study, five-year retention ran about 78% for recurring donors against about 36% for one-time givers.

That durability is what a migration puts in play. The first question I'd put to any incoming processor is whether it has boarded a recurring donation flow shaped like yours before, because a processor prices the shape of the payment flow, not the logo on the application. Its answer tells you whether your schedules, gift amounts and stored cards arrive intact. Card gifts move first. ACH schedules follow on the same timeline, and the contract terms you sign today decide whether the next switch is any easier.

Why is switching processors the riskiest moment for a recurring gift program?

Changing processors moves every stored donor card at once. If those credentials do not transfer intact, monthly gifts stop, and each lapsed sustainer has to be won back by hand.

Before you sign with a new provider, answer four questions in this order:

1. Who holds our donors' stored card credentials today, and will they release them in writing?
2. Can the new processor import those credentials without asking a single donor to re-enter a card?
3. Will the new account keep cards current automatically when banks reissue or expire them?
4. What does the new processor need to see before it will underwrite our recurring billing?

The 2026 M+R Benchmarks study, as summarized by MentisSoft, found that monthly giving made up 27% of online revenue among participating nonprofits in 2025. The share rose with size: 22% for smaller nonprofits and 37% for extra-large organizations. MentisSoft pairs those figures with a blunt warning. Recurring contributions should not be treated as guaranteed revenue, because donors cancel, payments fail, and processing fees reduce what actually arrives.

A processor switch stacks all three of those risks into one cutover. That is the real exposure.

The card rail is where the exposure concentrates. One fundraising platform vendor claims that 91% of recurring donors give by credit card, with 8% paying through ACH and 1% through PayPal. Buyer guides for nonprofit processing, meanwhile, list automatic updating of expired card details as a donor-retention feature rather than a default. Put together, those claims describe a program that lives almost entirely on stored cards, kept alive by tooling that not every provider includes.

The common assumption is that changing processors is a pricing decision. I'd push back on that framing hard. The rate is the visible part of the decision and usually the easiest to negotiate; the stored cards are the part that can quietly cost a nonprofit its most loyal donors.

Our underwriting team describes the same principle from the processor's side of the table. A processor does not price the label on an application; it prices the shape of the payment flow, and the qualifying question is whether it has already boarded that shape. For a nonprofit, the shape is stored cards billed on a monthly schedule, plus a sustainer file that has to arrive complete.

That is why I'd evaluate merchant services built for recurring billing on migration capability first and on rate second. A low quoted rate is worth little if a meaningful share of your monthly donors never make it across.

Combining 4 sources points to one conclusion: the sustainer file, not the rate card, is the asset a nonprofit is really moving. Protect it first.

And that file only moves if somebody, somewhere, agrees to export the credentials inside it.

What happens when your current processor will not release donor card tokens?

Your sustainers stall. Without a tokenized export, every monthly donor must re-enter card details, and a nonprofit that never held card data has almost no leverage to force the release.

A card-on-file token is a stand-in for a donor's card number that the processor stores so it can charge the next gift. Nonprofits are right to keep raw card numbers off their own systems, because holding them would pull the organization deep into PCI compliance, the card industry's data security standard. The trade-off is dependence. The processor holds the tokens, so only the processor can hand them over.

A 2023 thread on the r/nonprofit forum shows how that dependence plays out. An organization moving its sustainers from Frontstream to Stripe was told by Stripe and its new CRM that the procedure was "fairly straightforward": Frontstream would generate a tokenized report, and the sustainers would be set up "so there is no break in their payments." Frontstream refused, calling the release a security risk. The poster added that the same processor had earlier told the old CRM it could change processors "not unless you pay us a quarter of a million dollars."

The fallback is manual re-enrollment. It costs twice.

First, there is the labor: the poster faced recruiting volunteers to contact 600 sustaining donors one by one and explain why they had to sign up again. Second, there is attrition. A commenter in the same 2023 thread who had run into lock-in "a few times" warned that organizations forced to start fresh "lose 20-25% of them." Treat that as a field estimate rather than a benchmark; no published study in this space measures sustainer loss during processor changes. Re-enrollment also depends on cancelling every old recurring schedule cleanly, or donors get billed twice for the same gift.

Replacing lost sustainers is not cheap either. One fundraising software vendor claims it can cost up to $1.50 to raise a single dollar from a new donor, against $0.20 or less when soliciting existing donors. Losing a loyal monthly donor and then paying to acquire a stranger is one of the worst trades a development team can make.

None of this was hidden. Candid's 2022 guide to choosing a nonprofit processor told buyers to examine data portability and hold period policies, warned that some providers charge contract closure and early termination fees, and noted that processors built for for-profit businesses may not handle migrating donor data to a nonprofit CRM. The same guide separated aggregators, which place many organizations on one shared merchant account, from dedicated processors that open an account for each organization.

In my judgment, a processor that will not put token release in writing is a processor you cannot leave. Portability is a contract term. It is not a courtesy.

Some organizations reduce their exposure by offering bank-funded monthly gifts through online ACH payment options as a secondary choice, though cards remain the rail most sustainers pick. That still leaves the harder question: once tokens do move, what keeps the cards behind them current?

How do you move recurring gifts to a new processor without missing a month?

Sequence it. Secure the token file in writing, map every schedule, cut over away from peak giving season, cancel old schedules immediately, and watch declines closely afterward.

1. Inventory the sustainer file. List every active recurring donor with name, gift amount, frequency, next billing date, and donor ID.
2. Get the token release in writing. Confirm the outgoing processor will export the tokenized file and the new processor can import it.
3. Map billing dates one to one. Each donor should be charged on the same day of the month after the move, never twice and never skipped.
4. Choose a quiet cutover window. Keep the switch well clear of Giving Tuesday and the December appeal season.
5. Cancel old schedules at cutover. Shut off recurring billing on the old account the moment the new schedules go live.
6. Reconcile the first full cycle. Compare expected charges with actual charges and contact every donor whose card declined.

The detail in steps one and two matters more than it looks. One donation software vendor describes its own migration process as encrypting and exporting historical transaction data, confirming the new processor can import and decrypt it, supplying additional recurring-donation data, and then confirming that subscriptions synced. For the recurring piece, that vendor asks for donors' names, gift amounts, frequencies, and ID numbers, and it concedes that organizations without full in-house tech teams may not be able to handle the process safely on their own. Vendors ranking donation platforms list complex initial setup and extra training among their own products' drawbacks, too.

Timing is the lesson from 2023. Facebook's notice to nonprofits that year moved charity donations to PayPal Giving Fund and stated that any monthly giving would be discontinued after October 31, 2023, with PayPal charging 1.99% + $0.49 on each donation. The deadline landed just before Giving Tuesday and the year-end appeal season. A forced migration gives you no say over timing. A planned one does, so use it.

Keep donors' options intact on the other side, too. MayeCreate, citing Nonprofit Learning Lab, reported in 2024 that roughly 20% of donors reconsider giving when their preferred payment option is missing. A new donation form that quietly drops a wallet or bank option can undo a clean token transfer. Card processing should carry the sustainer file; for donors who prefer bank-funded gifts, a secondary rail such as Seamless ACH for recurring bank payments keeps that choice available.

The same MayeCreate piece reported that monthly giving revenue rose 6% in 2023 and made up 31% of all online nonprofit revenue that year. Contrary to the belief that monthly giving only compounds, the 2025 share cited earlier sits below that mark. My strong preference, given that slippage, is to treat every sustainer as harder to replace than the last one.

Which brings the contract back into focus, because none of these six steps works if the outgoing processor can simply say no.

What should a nonprofit settle before it signs with a new processor?

Settle who owns the sustainer file, how card-on-file tokens leave the old processor, and how churn will be measured across the cutover. Those answers decide whether gifts survive.

Ownership comes first. On Nonprofit Hub Radio in 2025, a recurring giving consultant warned that "if everybody's responsible for recurring giving, then nobody's responsible for recurring giving." A processor migration magnifies that gap. Nobody notices a sustainer who quietly stops being charged.

Measurement comes next. The same guest said the "nonprofit industry does not use churn," even though subscription businesses live and die by it. My bet is that this blind spot explains why no published figure exists for donor loss during processor changes, or for how often token migrations succeed. Track monthly sustainer churn before and after your cutover, and you will hold numbers the field does not yet have.

Recurring donors keep gaining ground, so the next switch will put more revenue on the stored card than the last one did. Get the token export promised in writing before you sign, and name the one person who will watch every declined renewal the week the new credit card processing goes live.