When adopting Konect, it is likely that a need will exist to migrate single and regular donors to Konect and Stripe, including payment methods such as Credit Cards. This article outlines the migration process from an existing payment gateway(s) to a single consolidated Stripe payment gateway. We have illustrated the various steps involved and anticipated responsibilities alongside indicative timelines.
Detailed Migration Process
The following table further details each step of the process. Konect allows you to work with any Salesforce implementation partner; we recommend Vertic in Australia.
Step | Name | Responsibility | Description |
1 | Export Contacts | Client Team | The initial step is to export all required Contact records from the existing fundraising solution; this export must include the Ids relating a specific contact to the existing payment gateway details. |
2 | Export Recurring Gifts | Client Team | The initial step is to export all required Recurring Gift records from the existing fundraising solution; this export must include the Ids relating a specific contact to the Recurring Gift. |
3 | Import Contacts | Partner | This step imports the exported Contacts from the existing fundraising solution into Salesforce, including the Ids exported in Step 1, as these will be used to match Contacts in Salesforce to the newly tokenised payment methods. |
4 | Import Recurring Gifts | Partner | This step imports the exported Recurring Gifts from the existing fundraising solution into Salesforce, including the Ids exported in Step 2, as these will be used to match Contacts to Recurring Gifts. |
5 | Export Payment Methods | Existing Gateway | The extraction of all relevant existing payment methods must include the same Id (Token) used in Step 1, as this is the same Id used to match the newly tokenised payment methods. This involves a process of producing a sample file to verify the format of the eventual full export file. |
6 | Tokenise Payment Method | Stripe | The Stripe payment gateway will accept the exported payment method file (to an agreed format) and tokenise the submitted payment methods; further details on this can be found here. |
7 | Register Payment Information | Stripe | Once the existing payment methods have been tokenised within the Stripe payment gateway, they are registered within this gateway for future use. |
8 | Produce Import File | Stripe | This step produces the required import file for loading into Salesforce, containing the new Stripe payment methods token as well as the Ids exported in Step 1, as this is how we will match Contacts in Salesforce to Stripe payment methods. |
9 | Import Tokens | Partner | Partner will load the newly tokenised payment methods into Salesforce and use the Ids exported in Step 1 to match these to Contacts imported in Step 3. It must be noted that there is potential loss of payment methods via a number of issues, such as incorrect details, expired cards, import issues, etc. The aim is to maximise success but accept some level of loss. |
10 | Match Contacts | Partner | Partner will use the Ids exported in Step 1 to match Contacts in Salesforce to the newly tokenised Stripe payment methods. |
11 | Create Subscriptions | Partner | Partner will create Stripe subscriptions to sync the newly imported Recurring Gifts in Step 4 with Stripe to enable payment processing. |
Additional Information