There may be times when you want the integration to attach to existing records inside Salesforce. This is most common in "Go Live" scenarios where records from your source platforms might already exist in Salesforce, and you need the integration to attach to those existing records instead of creating new ones. This article details how to do this.
Important Notes
If you don't do this, the integration may be unable to identify existing Salesforce records and duplicate records could be created as a result
MoveData cannot perform this function for you. This is because we do not know what those records you have already created in Salesforce are.
This is a general article. It is to be read in conjunction with Map to Existing Records: Platform Key Syntax which provides specifics for the source platforms you are seeking to connect.
Minimum Approach
Many organisations will want MoveData to create all records from scratch and in this case you do not need to continue reading this article.
If your organisation does wish to map to existing records, then the minimum recommended approach is to map campaign and recurring donation records. This is because those records tend to persist over time, and:
Contacts match automatically using your Salesforce Duplicate Rules
Accounts match automatically matched using your Salesforce Duplicate Rules
Opportunities are rarely updated after they have been created
Map Campaign Records
Add the following to your campaign record in Salesforce:
Salesforce Field | Comment |
Platform Key
| Identifier for the fundraising page record in your source platform |
Protect Name
| Set |
Map Recurring Donation Records
Add the following to your recurring donation record in Salesforce:
Salesforce Field | Comment |
Platform Key
| Identifier for the recurring donation record in your source platform |
Map Opportunity Records
Add the following to your opportunity record in Salesforce:
Salesforce Field | Comment |
Platform Key
| Identifier for the transaction record in your source platform |
Map Contact Records
Contacts can contain multiple identifiers (for example, if the same contact exists across multiple different source platforms). As such, identifiers for contact records are stored on the child object Contact Platform Key movedata__Contact_Platform_Key__c. To map contact records, create the Contact Platform Key record in Salesforce:
Salesforce Field | Comment |
Contact
| Identifier for the contact record in Salesforce |
Platform Key
| Identifier for the contact record in your source platform |
Map Account Records
Accounts can contain multiple identifiers (for example, if the same account exists across multiple different source platforms). As such, identifiers for account records are stored on the child object Account Platform Key movedata__Account_Platform_Key__c. To map account records, create the Account Platform Key record in Salesforce:
Salesforce Field | Comment |
Account
| Identifier for the account record in Salesforce |
Platform Key
| Identifier for the account record in your source platform |
Notes: Map Account Records
The integration does not directly interface with Household Accounts. These are managed by NPSP when a contact is created or updated. The above applies to organisation accounts only.
Not all source platforms will provide an ID for the account. Often this is provided as metadata on the donation (for example, "Company Name") which the integration uses to find / create the account record. In that scenario, given no identifier is present for the account, the integration can only use your Salesforce Duplicate Rules.