How to Migrate Recurring Donations Without Losing a Single Donor

You can migrate recurring donations without asking donors to re-enter their payment details. Your old payment processor securely transfers saved card and bank data to your new processor through a PCI-compliant process, you recreate each recurring schedule in the new system, and you switch charging over on a single planned date. Done this way, donors notice nothing. Done badly, they're charged twice or not at all, and many quietly lapse.

Recurring gifts are worth the effort. Monthly donors deliver about 27% of online revenue for the average nonprofit, per M+R's 2026 Benchmarks, and they are your most loyal supporters.

Why recurring gifts are the riskiest part of a migration

Every other part of a migration is historical data. Recurring gifts are live money. If the transfer fails, the cost is immediate, and donors who are asked to "please re-enter your card" often don't.

The main failure points:

• Payment tokens left behind at the old processor.
• Schedules recreated with the wrong amount, date or fund.
• Both systems charging in the same month.
• No one watching failed payments after the switch.

Step 1: Find out where the payment data actually lives

Your fundraising CRM usually doesn't hold card numbers. A payment processor does (Stripe, Blackbaud Merchant Services, Authorize.Net, PayPal and so on). Ask your current vendor:

• Which processor holds our saved cards and bank accounts?
• Is the merchant account in our name or the vendor's?
• What is the process and timeline to export payment data to a new processor?

If the merchant account is in the vendor's name, the transfer depends on their cooperation. Raise it early, and check your contract for data portability terms.

Step 2: Request a secure processor-to-processor transfer

Card numbers are never exported to a spreadsheet. Processors transfer them directly to each other over encrypted channels.

If you are moving to Stripe, its Data Migrations team imports card and bank data from your previous processor via a secure file transfer, reviews it and sends you a validation summary to approve (Stripe documentation). Stripe notes that its data import doesn't recreate subscriptions; schedules are rebuilt separately. Plan for the import to take one to two weeks once the old processor sends valid data.

If you already use Stripe and are simply changing fundraising software, your saved payment methods may be able to stay in place or be copied between Stripe accounts, which is much simpler.

Step 3: Map every schedule before cut-over

For each recurring gift, export and verify:

Keep a crosswalk file of old IDs to new IDs and payment method references. You'll need it for reconciliation.

Step 4: Choose a clean cut-over date

Pick one date. Before it, every charge runs in the old system; after it, every charge runs in the new one.

• Choose a date just after a charge cycle, so you have nearly a full month to verify.
• Stop all recurring schedules in the old system the day before cut-over.
• Activate them in the new system with next-charge dates carried over exactly.

Step 5: Tell donors (briefly) or not at all

If donors' experience doesn't change, a short note is optional. Send one if the charge descriptor on their statement changes, so they don't dispute an unfamiliar name. Something like: "We've upgraded our giving system. Your monthly gift continues as usual; on your statement it will now appear as [descriptor]."

Step 6: Watch the first two cycles closely

• Reconcile the first cycle: expected charges vs. successful charges vs. failures.
• Contact every failure within 48 hours.
• Compare monthly recurring revenue before and after the migration. It should match within normal churn.

Recurring gift migration checklist

• Identify the processor and merchant account owner.
• Request the payment data transfer at least six weeks before cut-over.
• Export and verify every active schedule.
• Build the old-to-new ID crosswalk.
• Pick the cut-over date and freeze the old schedules.
• Activate schedules in the new system.
• Notify donors if the statement descriptor changes.
• Reconcile the first two charge cycles.

How Evolve Fundraising handles recurring gifts

Evolve Fundraising processes payments through Stripe, including saved cards, ACH and autopay, so organizations moving from another processor can use Stripe's secure payment data import. Recurring schedules are imported with their amounts, dates and fund designations and attached to each donor's single record. Every charge posts to the general ledger by fund and reconciles to Stripe deposits, which makes the post-migration check a report, not a project.