Move recurring gifts from Bloomerang Payments
Updated 4 days ago
Move your Bloomerang recurring gifts to Gratona with their existing amounts and schedule. Start by identifying the Bloomerang payment service holding your saved methods, because each one has its own transfer team and procedure.
Before you begin
This guide covers what is specific to Bloomerang. The shared steps are in the migration overview; have these in place first:
Onboarding path chosen. Growth plans and above require guided or white-glove onboarding. “Migration coordinator” below means your organization’s lead or the Gratona owner named in your onboarding plan; use their email in the samples.
Stripe connected to Gratona and its account ID noted, as in Prepare payments for your migration.
Donor emails paused with the email pause instructions, before any records are imported.
Your account holder authorizes the provider release. Existing collections keep running until the approved switch.
1. Identify the payment service
Check the processor used for your recurring gifts. Bloomerang CRM, Bloomerang Payments and Bloomerang Fundraising can involve different transfer teams and procedures.
Bloomerang Payments: Bloomerang support, routed to Payments Migration. An export of the payment methods it holds and a report linking recurring donations to payment methods. Continue with step 2.
A separate processor: Whoever holds the payment methods. For the same Stripe account, use the existing connection. For different Stripe accounts, follow Stripe’s account-copy process. A non-Stripe processor such as Authorize.net handles its export to Stripe. The recurring-donation mapping report from Bloomerang, in each case.
Bloomerang Fundraising: Bloomerang Fundraising support. Its recurring-donor transfer process, which requires a receiving technical contact, PCI compliance review and an agreed transfer date. Tell support to leave the account and schedules active. See “For Bloomerang Fundraising” in step 2.
2. Request the payment-method copy
The authorized account holder opens a support case and copies the migration coordinator. Include the source account, organization name and verified destination Stripe account ID. Use the account ID beginning with acct_, not an API key.
Message to Bloomerang support
Subject: Copy saved payment methods to our Stripe account
Hello,
Please transfer a copy of our saved payment methods from Bloomerang Payments to our organization’s Stripe account.
Organization: [organization name]
Bloomerang account: [account ID]
Destination Stripe account: [acct_ ID]
Migration contact: [migration contact email]If this can be handled as a Stripe-to-Stripe copy, please coordinate the copy and destination mapping with our migration contact. If a processor export is required, please encrypt the payment-data export with Stripe’s current public PGP key and upload it using the SFTP credentials supplied by Stripe for this migration. Please send Stripe your public PGP key so Stripe can encrypt the SFTP credentials for your export team. Confirm the upload date, record count and any excluded records on the support case.
Please send the authorization wording, current export quote and available transfer dates. Please also send the sample report linking our recurring donations to their payment methods so we can review it before we schedule the transfer.
Please keep our account and existing recurring donations active. Please copy [migration contact email] on your reply.
Thank you,
[authorized account holder]
You can identify Gratona as the receiving CRM and Stripe as the receiving processor when support asks.
For Bloomerang Fundraising
Address the request to Bloomerang Fundraising support and identify Gratona as the receiving system and Stripe as the receiving processor. Provide [migration contact email] as the technical contact. The Fundraising team reviews the receiving processor’s PCI compliance and offers transfer dates before securely delivering the file. Request a copy while retaining the existing account and schedules until your agreed switch. Its published transfer procedure describes its own extraction charge and requirements.
3. Review the report and approve the quoted service
Get the quote. Budget for a paid export, usually a separately quoted service. Ask for the total charge and whether another export would incur a new fee; the Payments Migration team has charged separately for repeat exports. Bloomerang Fundraising publishes its own extraction fee, so use the quote for your product and account rather than assuming the two services cost the same.
Review the sample report before authorizing the charge. Compare it against your required donor, schedule and allocation fields. If Gratona is preparing your import, share it with your coordinator. In a completed Bloomerang Payments transfer, support said it could not add columns to its standard report, so export any missing sponsorship allocations or other required information separately.
Authorize. Bloomerang’s Payments Migration authorization has requested the organization’s EIN, receiving CRM, payment processor, destination Stripe account and explicit consent to charge the payment method on file. Your authorized account holder completes the wording support supplies after reviewing the fee.
Authorization reply after the fee is approved
Please proceed with the payment-method export to Stripe. I authorize the quoted [amount and currency] charge to the payment method on file for this export.
Organization: [organization name]
EIN: [EIN]
Receiving CRM: Gratona
Receiving processor: Stripe
Destination Stripe account: [acct_ ID]Existing recurring donations should remain active. Please send the available export dates and copy [migration contact email].
4. Schedule the export with Gratona and Stripe
Your migration coordinator coordinates receiving-account readiness with Stripe and the source provider. For a processor import, use Stripe’s payment-data import process. If the payment methods already reside in Stripe, the teams determine the appropriate account-copy route.
Submit the Stripe request for a processor import
Follow the Stripe intake and approval steps in Prepare payments for your migration; you do not need to wait for an export date. Use the receiving account connected to Gratona and keep the acknowledgment with this provider case. The key exchange and upload follow the shared secure upload step.
Scheduling reply
[Date] works for us. Our Stripe account is ready. Please confirm when the export is scheduled and when the files are uploaded. Existing recurring donations should remain active.
Send this once your migration coordinator has agreed the date with both providers. Record the export’s cutoff time and track any new donors, changed payment methods or schedule edits after that cutoff. Resolve those changes before launch; a repeat export may cost extra.
What the export stage has looked like. In one completed Bloomerang Payments transfer, authorization was sent August 31, 2026. On September 1, Bloomerang offered an export date two business days later; it confirmed the export on September 3. That is an example of the export stage after approval, not a promised turnaround for the complete migration. Allow additional time for report review, any compliance review, Stripe processing, donor matching and collection setup.
5. Collect both the payment-method transfer and the mapping report
These are separate deliverables. Payment credentials go directly through the providers’ secure transfer process. Your team receives only the report needed to connect recurring donations to donor and payment records, and only that report belongs in ordinary email or your Gratona Space.
A completed Bloomerang Payments export supplied a file named Recurring Schedules in Bloomerang.csv with these columns:
Purpose | Columns supplied |
|---|---|
Donor matching | Name; Account Number; Primary Email Address |
Recurring gift | Date; Amount; Type; Frequency; Schedule Transaction Number; Schedule Next Installment Date |
Designation | Fund; Campaign; Appeal |
Payment matching | Credit Card Last Four Digits; EFT Last Four Digits; PaymentMethodToken; Customer Token |
Read the columns this way:
Keep the column names and identifiers intact.
Account Number is a source matching identifier, not a bank credential. EFT Last Four Digits is only a masked suffix.
Review the meaning of Date before using it as a sponsorship start date.
A blank email does not by itself prevent a donor match when reliable IDs are available.
A token in the source report is not proof that the same identifier is usable in the destination account.
Your migration coordinator reconciles the report against the destination payment methods, including any source-to-destination ID mapping returned by Stripe. Compare record counts and resolve missing methods, unmatched donors and multiple schedules before enabling collections.
For Bloomerang Fundraising, the provider describes a different secure export based on its Recurring Payments download, with payment credentials delivered to the receiving provider. That file is not a substitute for an ordinary donor-import spreadsheet.
6. Follow up on the same support case
If support has not given a response date, we recommend following up after two business days. This is a follow-up cadence, not a provider response guarantee. If the agreed export date passes without confirmation, follow up the next business day.
Before the export
Hi [name],
I’m following up on our payment-method transfer to Stripe, case [number]. Do you have everything needed to schedule the export? Please send the expected transfer date and let us know if anything is still needed from our team or Gratona.
Thanks,
[name]
After the scheduled export date
Hi [name],
Please send the export confirmation and recurring-donation mapping report for the transfer scheduled on [date] to [acct_ ID]. Were any records excluded?
Existing recurring donations should remain active.
Thanks,
[name]
7. Agree the collection switch
Exporting payment methods does not stop existing gifts or recreate their schedules in Gratona. Bloomerang confirmed in our Payments Migration case that recurring donations continue until the processor is disconnected from the CRM or the schedules receive end dates. Keep the processor connected during preparation, and coordinate any change with your migration lead.
When a group is ready, follow Launch and hand over your migration. It sets the order: collection readiness is confirmed, with Gratona’s confirmation for any historical imports; the Bloomerang schedules for that group are ended; then the Gratona schedules are activated. Include source retries and charges pending around the switch so a gift is neither collected twice nor missed.
Payment-method transfer, historical-gift import and account closure are separate actions.
Continue in Gratona
Complete the switch above, then check the first actual collections and resolve exceptions.
Use the receipt instructions to review and activate only the approved messages.
Keep the provider’s upload confirmation, mapping report and stopped-schedule confirmation in your migration record.