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 gift commitment records. This is because those records tend to persist over time, and:
Person Accounts match automatically using your Salesforce Duplicate Rules
Organisation Accounts match automatically matched using your Salesforce Duplicate Rules
Gift Transactions are rarely updated after they have been created
Map Campaign Records
Add the following to your campaign record in Salesforce:
Salesforce Field | Comment |
| ID of the page record in the source platform |
| Set |
Map Gift Commitment Records
Add the following to your gift commitment record in Salesforce:
Salesforce Field | Comment |
| ID of the recurring donation record in the source platform |
Map Gift Transaction Records
Add the following to your gift transaction record in Salesforce:
Salesforce Field | Comment |
| ID of the donation record in the source platform |
Map Person Account Records
Person Accounts can contain multiple identifiers (for example, if the same person account exists across multiple different source platforms). As such, identifiers for person account records are stored on the child object Account Platform Key movedata__Account_Platform_Key__c. To map person account, create the Account Platform Key record in Salesforce:
Salesforce Field | Comment |
| ID of the person account record in Salesforce |
| ID of the person account record in the source platform |
Map Organisation 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 |
| ID of the account record in Salesforce |
| ID of the account record in the source platform |
Notes: Map Organisation Account Records
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.
Map Opportunity Records
Add the following to your opportunity record in Salesforce:
Salesforce Field | Comment |
| ID of the sale record in the source platform |
Notes: Map Opportunity Records
NPC uses the Gift Transaction object to represent donations
Opportunities are only used for non-donation transactions, such as merchandise sales, paid event registrations, raffle ticket sales etc