Data Migration Guidelines for GoCardless
Mandate Import by GoCardless
You will need to cancel the old mandates once you have gone live and the system is stable. It is advisable to keep these old mandates as a backup until a stable production state has been reached.
GoCardless will provide a CSV template you will need to populate by exporting your current mandate (Name, Bank, Sort, Address) details from your system
It is imperative that you provide a unique identifier in this spreadsheet that can be used later to match the mandate payment methods against the correct contact in Fonteva. If your contacts are already in Salesforce, then providing the 15-digit Salesforce ID is preferable here.
GoCardless will do the import for you and create new mandates under a new SUN for all your contacts.
GoCardless will inform you once all the mandates have been setup in GoCardless.
Mandate Export from GoCardless
You can then log in to manage.gocardless.com, and see a list of all mandates.
There is functionality (top right) to export this list as a csv file. This will export any metadata related to the mandates as well. This metadata will contain the unique identifier you included in the CSV file for import in step 1.
Export the mandates and save this to a local drive.
Payment Method Import
This requires a unique Contact ID (either 15-character SF ID or another identifier. If you use an alternative identifier, you will need to export a list of SF contacts with this identifier and use VLOOKUP to add the 15-character SF ID to your exported spreadsheet of GoCardless mandates)
Use SF data loader to upload your GoCardless payment methods to Fonteva. Note, these payment methods must contain the unique ID from GoCardless, and must be marked as DD.
Sales Orders and Scheduled Payments Migrations
If you are migrating sales orders that are part paid and still have outstanding payments, please bear in mind the following:
There is a possibility of creating duplicate scheduled payments if your sales orders are not posted.
DD renewals, where there is more than one payment in a year, work by creating just the first scheduled payment of the series on a Sales Order. Once this scheduled payment has been sent to GoCardless and the ePayment marked as paid out, then it goes back and posts the sales order and creates the rest of the scheduled payments in the series.
This means that if you have migrated all the Scheduled Payments in a series already, that the above functionality could result in you creating duplicate scheduled payments where your Sales Order was not posted.
To avoid this, ensure that all migrated DD Sales Orders are in a posted state (please make sure your triggers are turned off on the sales order if you are manually creating the scheduled payments)