⚠️Important:
The move from GoCardless to RPI is not an automated process. We strongly recommend that you understand how RPIs work in Donorfy and test thoroughly before migrating live data.
Incorrect start dates can result in duplicate collections or missed payments. Always test before migrating in bulk.
Understand the Purpose of Migration
If you already collect recurring donations via GoCardless Subscription Plans or another provider, you can migrate these into Donorfy RPIs so Donorfy controls the collection schedule.
Benefits include:
A complete view of supporter giving.
Easier upgrades and changes.
Reduced manual administration.
Improved reporting.
Centralised constituent management.
Payments are still collected by GoCardless. Donorfy controls when collections are initiated.
Understand What You Need Before Starting
Before migrating, ensure you understand:
How Recurring Payment Instructions work in Donorfy.
How Donorfy and GoCardless integrate.
GoCardless’s own guidance on migrating subscriptions( see this article)
Make sure you understand how:
Recurring Payment Instructions work in Donorfy - these articles provide more information, this one is a good starting point.
GoCardless and Donorfy work together - these articles describe that.
GoCardless has a knowledge base article here that explains the steps they recommend. The purpose of this article is to add some further details to those steps to help with the process.
Collate Your Data
You must gather and prepare all required data before uploading anything to Donorfy.
Prepare Constituent Data
Every recurring donor must already exist as an active constituent in Donorfy.
Download customer data from GoCardless, here.
Ensure each customer exists as an active, non-archived constituent in Donorfy.
At minimum, constituents must have a name and email address.
Prepare RPI Data
Next, download recurring payment details.
From GoCardless Subscription Plans
Download Active subscription plans from GoCardless, (see this article from GoCardless).
Ensure mandates are fully set up and not pending.
Pending mandates are excluded and must be handled separately.
From Another Provider
Export recurring payment data from your existing provider.
Configure Donorfy for Migration
Create a temporary collection method to prevent immediate billing.
Create a Temporary Collection Method
Go to Settings, then Configuration.
Create a new Collection Method, for example RPI Migrate.
This prevents Donorfy from triggering GoCardless collections during setup.
Upload Data into Donorfy
Data must be uploaded in the correct order.
Upload Constituent Information
Upload constituent data using the standard constituent upload process.
Confirm all recurring donors exist and are active.
Upload RPI Data
Upload Recurring Payment Instructions using the RPI upload template.
Set the following required fields:
RPI Core Fields
Type: Recurring Donation.
Status: Active.
Frequency: Month, Quarter, Half Year, or Year.
Collection Method: Temporary method (for example, RPI Migrate).
Collection Day: Usually 3 days before the customer debit date.
Start Month: Month the RPI will go live in Donorfy.
Collection Ref1: GoCardless Mandate ID.
Payment Details
Amount: Donation amount.
Starting: Correct go-live date.
Ending: Open Ended.
Allocation
Amount Due: Donation amount.
Include the donor’s email address so Donorfy can match the RPI to the correct constituent.
Set Correct Start Dates
The Start Date is critical.
⚠️ Important: The Start Date is not the original setup date. It is the date Donorfy begins collecting payments.
If no Start Date is set, Donorfy assumes Next Collection, which can cause duplicate or missed payments.
Example Start Date Scenarios
Assume today is 01/05/2020 and migration date is 01/06/2020.
Next Payment Date | RPI Start Date | Collection Day |
01/06/2020 | 01/07/2020 | 01 |
07/06/2020 | 01/07/2020 | 07 |
10/06/2020 | 01/07/2020 | 10 |
15/06/2020 | 01/06/2020 | 15 |
Annual 01/08/2020 | 01/08/2020 | 01 |
Quarterly 07/07/2020 | 01/07/2020 | 07 |
Verify Uploaded RPI Data
Before proceeding:
Create a Recurring Payment Instruction List.
Verify amounts, dates, collection methods, and mandate IDs.
Fix any issues before connecting GoCardless.
Connect Donorfy to GoCardless
If not already connected:
Connect Donorfy to GoCardless.
📌 Note: Skip this step if GoCardless is already connected for Web Widgets.
Test the Migration Process
Always test with a single RPI before migrating everything.
Run a Test Migration
Select one existing GoCardless customer.
Identify the final payment date from the existing subscription.
Cancel the GoCardless subscription in the GoCardless dashboard.
📌 Note: This sends a notification unless silently closed.
Change the RPI Collection Method in Donorfy from RPI Migrate to GoCardless.
Confirm Donorfy collects the payment on the correct date.
Confirm no duplicate notifications or payments occurred.
If the test fails, adjust and repeat before continuing.
Prepare for Full Migration
Once testing is successful:
Update RPIs as required using the File Updater.
Double-check start dates, mandate IDs, and constituent matches.
Start the Full Migration
Only proceed once testing is complete.
Cancel GoCardless Subscription Plans
Contact GoCardless Support.
Request a silent close of all subscription plans.
⚠️ Important:
Silent close prevents supporter notifications.
Failure to do this results in duplicate collections.
Close RPIs from Other Providers
If migrating from another source:
Close recurring payments in the source system.
Migrate in batches if required.
Update Cancelled RPIs
Manually update Donorfy for any subscriptions or mandates that were recently cancelled to avoid failed collections.
Switch Collection Methods to GoCardless
Once ready:
Update the RPI Collection Method from RPI Migrate to GoCardless.
Use the File Updater for bulk changes.
⚠️ Important: Donorfy will immediately attempt to collect any RPIs due in the current month.
Monitor RPI Collections
After migration:
Go to Financial, then Recurring Income.
Review the History tab for collections, failures, and missed payments.
You can also check Last Payment Received using an RPI list.
Manage Notifications
By default, GoCardless sends payment notifications for each collection.
You may reduce notifications by:
Creating a New Direct Debit notification.
Informing supporters that Donorfy now manages collections.
Further notifications only occur if the RPI changes.
When Is the Best Time to Migrate?
Timing matters.
If payments fall within 10 days of migration, delay Donorfy collection until the next cycle.
Ensure Start Dates avoid overlapping collections.
Add Any Missing Transactions
After migration:
Identify any payments collected during the transition.
Add missing transactions manually to Donorfy.
