Migrating recurring donations with the Salesforce Agentforce Nonprofit Cloud (NPC) integration

Recurring donations sync as Gift Commitment records in Salesforce Nonprofit Cloud (NPC) through our Salesforce Nonprofit Cloud integration. If you are migrating recurring plans via a Recurring Donation Migration (RDM), you will need to manage your Salesforce records differently based on whether you have a new or existing NPC instance.

New NPC instance

If you are setting up a new NPC instance when migrating recurring plans, we recommend letting the plans finish creating through the migration. Once the migration is complete, a Migration Specialist will provide a mapping file of your old recurring plan ID to the new GFM Pro Recurring Giving Plan ID.

As donations are made to the recurring plans, the Gift Commitment records will be created in NPC and linked to all future donations. Gift Commitment records will not be created until a successful transaction has occurred on the recurring plan. If the transaction count is 0 for the recurring plan, or the transaction fails, it will not be in Salesforce.

You can import any historical data for the plan to the appropriate Gift Commitment record based on the GFM Pro Recurring Giving Plan ID once the record is created.

Existing NPC instance

When using an existing NPC instance, we recommend letting the integration create the Gift Commitment record to ensure future data syncs successfully. This may result in expected duplicate records, but you can merge them later. There are 2 ways to merge duplicate Gift Commitment records:

1. Transfer all of the existing Gift Transactions to the Gift Commitment record created by the GoFundMe Pro integration, and then delete the old Gift Commitment record.
2. Match the records via contact information or donation amount.

FAQs

Do records merge automatically or is this something that will have to be completed manually?

You will have to manually merge your existing Gift Commitment records with the ones that the integration creates.