The following steps are in preview for CiviPlus version 4 and not in place for all sites, please contact your account manager before proceeding.
Introduction
If you are already taking Donation Direct Debits using GoCardless this is the guide for you!
Steps: Within CiviPlus
The following steps need to be taken from within CiviPlus site:
The steps for this are slightly different depending on whether you are migrating from an existing CiviCRM site or coming in from a completely different CRM or platform.
a) If migrating from another CiviCRM site using the CiviPlus migrator:
CiviPlus uses a slightly different GoCardless integration to some other CiviCRM's (which includes a lot of additional functionality!) and so to continue using GoCardless with CiviPlus after your migration you need to perform a few simple steps.
Before you start ensure that your CiviPlus site is setup and connected to GoCardless correctly.
You will have existing recurring contributions in CiviCRM and you will need to update them to use the new GoCardless payment processor.
You can do this using the report screen found at Administer > CiviContribute > GoCardless Recurring Donation Batch Update
Use the search report to filter the relevant recurring contributions that you want to move to the new payment processor.
The recurring contributions must have the GoCardless "Subscription ID" in the recurring contribution "Payment Processor ID" field. If this is not the case you should import these details into CiviPlus using the API importer and Recurring Contribution API.
Select all the relevant recurring contributions to be updated
Select Actions > Update Recurring Contributions
Select the field "Payment Processor" and set this to "GoCardless"
Click "Update Recurring Contributions"
This process will update the recurring contributions to connect the to the new GoCardless payment processor and any future payments on those subscriptions will be connected to your new CiviPlus.
b) If migrating from a completely different CRM or platform:
If migrating from a completely different CRM or platform site to CiviPlus but are already taking donation direct debits the steps are as follows:
Before you start ensure that your CiviPlus site is setup and connected to GoCardless correctly.
Confirm that your existing system is using GoCardless "Subscriptions" to take recurring donations. You can do this by checking in the GoCardless platform. If not please contact the CiviPlus team for assistance.
In advance of the final payment date that you will be using your old system for you will need to prepare an import sheet with your donors on it.
Please find a sample sheet here <please contact CiviPlus team for a copy of this sheet>
You will need to export the relevant data from your existing CRM or platform.
Make sure you populate the "external_id" with a unique ID that matches to the ID that the customer has in GoCardless.
Once populated you can import this into CiviPlus using the API CSV importer and using the "recurring contributions API".
Once it all works you're ready for go live! Keep in mind you'll need to add any new donors to your import sheet before you perform your final import.
Note: For customers with a managed service if you would like to perform a test import please see details on how you can do this below.
When you perform the import, CiviPlus will import the relevant data and connect it to GoCardless for you, hooking everything up and your next donations should be taken seamlessly! Great job!
CiviCRM Test import: For customers who have a managed migration
You may want to test importing your CiviPlus import file before doing it for real on your day of go live/switch.
For customers who have a managed migration with us please let us know when you are ready to test.
We can then setup a clone of your site in "non production mode". You can then connect this clone site to a "sandbox" GoCardless account and test the import of your file, without making messy copies of your data.
When you are ready simply submit a helpdesk ticket or basecamp message referencing this article and asking for a "clone site to be setup in non production mode".