Map to Existing Records: NPSP
When you go live with MoveData, your source platform may already have records that exist in Salesforce. You need the integration to link to those existing records rather than creating duplicates. This article shows you how.
Before you start
- If you skip this step, MoveData may not find your existing Salesforce records. This could lead to duplicate records.
- MoveData cannot do this for you because we do not know which records you have already created in Salesforce.
- Read this article alongside Platform key syntax, which explains the identifiers for each source platform.
Minimum Approach#
Many organisations want MoveData to create all records from scratch. If that describes your situation, you can stop here.
If you want to map to existing records, we recommend mapping campaign and recurring donation records at a minimum. These records persist over time, and the other record types handle matching differently:
- Contacts match automatically through your Salesforce Duplicate Rules
- Accounts match automatically through your Salesforce Duplicate Rules
- Opportunities are rarely updated after creation
Map Campaign Records#
To map an existing Salesforce campaign to a record in your source platform, populate the following fields on the campaign record in Salesforce. The Platform Key value tells MoveData which source platform record this campaign corresponds to, so the integration updates the existing campaign rather than creating a new one.
| Salesforce Field | API Name | Description |
|---|---|---|
| Platform Key | movedata__Platform_Key__c |
Set this to the identifier for the fundraising page record in your source platform. See Platform key syntax for the correct format. |
| Protect Name | movedata__Protect_Name__c |
Set to True to keep the existing campaign name in Salesforce. Otherwise, the integration may overwrite it with the name from your source platform. |
Worked example
For example, if your Raisely campaign has a Profile UUID of aa88bd90-562c-11eb-bf24-6bd493dd10e5, set the Platform Key field to raisely:aa88bd90-562c-11eb-bf24-6bd493dd10e5.
See Platform key syntax for the full list of identifiers for each source platform.
Map Recurring Donation Records#
To map an existing Salesforce recurring donation to a record in your source platform, populate the following field on the recurring donation record in Salesforce. The Platform Key value tells MoveData which source platform record this recurring donation corresponds to, so the integration updates the existing record rather than creating a new one.
| Salesforce Field | API Name | Description |
|---|---|---|
| Platform Key | md_npsp_pack__Platform_Key__c |
Set this to the identifier for the recurring donation record in your source platform. See Platform key syntax for the correct format. |
Worked example
For example, if your Raisely subscription has a UUID of b6f623c0-2a74-11ec-91e7-b9ad139ed3a4, set the Platform Key field to raisely:b6f623c0-2a74-11ec-91e7-b9ad139ed3a4.
See Platform key syntax for the full list of identifiers for each source platform.
Map Opportunity Records#
To map an existing Salesforce opportunity to a transaction in your source platform, populate the following field on the opportunity record in Salesforce. The Platform Key value tells MoveData which source platform transaction this opportunity corresponds to, so the integration updates the existing record rather than creating a new one.
| Salesforce Field | API Name | Description |
|---|---|---|
| Platform Key | movedata__Platform_Key__c |
Set this to the identifier for the transaction record in your source platform. See Platform key syntax for the correct format. |
Worked example
For example, if your Raisely donation has a UUID of 55f1ef50-f15f-11ee-ad05-719b0288d1dc, set the Platform Key field to raisely:55f1ef50-f15f-11ee-ad05-719b0288d1dc.
See Platform key syntax for the full list of identifiers for each source platform.
Map Contact Records#
A single contact can have multiple identifiers. For example, the same person might exist across several source platforms. MoveData stores these identifiers on a child object called Contact Platform Key (movedata__Contact_Platform_Key__c).
To map a contact, create a Contact Platform Key record in Salesforce and populate the following fields. The Platform Key value tells MoveData which source platform contact this Salesforce contact corresponds to, so the integration updates the existing record rather than creating a new one.
| Salesforce Field | API Name | Description |
|---|---|---|
| Contact | movedata__Contact__c |
The contact record in Salesforce. |
| Platform Key | movedata__Platform_Key__c |
Set this to the identifier for the contact record in your source platform. See Platform key syntax for the correct format. |
Worked example
For example, if your Raisely contact has a Person UUID of 6fe7fd90-100f-11ea-b92d-574a5da4fffc, set the Platform Key field to raisely:6fe7fd90-100f-11ea-b92d-574a5da4fffc.
See Platform key syntax for the full list of identifiers for each source platform.
Map Account Records#
Like contacts, accounts can have multiple identifiers across different source platforms. MoveData stores these on a child object called Account Platform Key (movedata__Account_Platform_Key__c).
To map an account, create an Account Platform Key record in Salesforce and populate the following fields. The Platform Key value tells MoveData which source platform account this Salesforce account corresponds to, so the integration updates the existing record rather than creating a new one.
| Salesforce Field | API Name | Description |
|---|---|---|
| Account | movedata__Account__c |
The account record in Salesforce. |
| Platform Key | movedata__Platform_Key__c |
Set this to the identifier for the account record in your source platform. See Platform key syntax for the correct format. |
Account mapping in practice
Most source platforms do not provide their own identifiers for organisation accounts. Account information typically arrives as text (for example, "Company Name") rather than a unique ID. In these cases, platform key matching does not apply — MoveData uses your Salesforce Duplicate Rules to find or create the account record instead.
Household Accounts
The integration does not work directly with Household Accounts. NPSP manages these when a contact is created or updated. The steps above apply to organisation accounts only.