Map to Existing Records: NPC
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 gift commitment records at a minimum. These records persist over time, and the other record types handle matching differently:
- Person Accounts match automatically through your Salesforce Duplicate Rules
- Organisation Accounts match automatically through your Salesforce Duplicate Rules
- Gift Transactions are rarely updated after creation
Map Campaign Records#
For each existing campaign record in Salesforce that should link to your source platform, set the following field values:
| Salesforce Field | API Name | Value |
|---|---|---|
| Platform Key | movedata__Platform_Key__c |
The platform key identifier for the campaign in your source platform. See Platform Key Syntax for the 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
If your Raisely campaign has Profile UUID aa88bd90-562c-11eb-bf24-6bd493dd10e5, set the Platform Key field on your Salesforce campaign record to:
raisely:aa88bd90-562c-11eb-bf24-6bd493dd10e5
See Platform Key Syntax for the full list of platform prefixes and identifier formats.
Map Gift Commitment Records#
For each existing gift commitment record in Salesforce that should link to your source platform, set the following field value:
| Salesforce Field | API Name | Value |
|---|---|---|
| Platform Key | md_npc_pack__Platform_Key__c |
The platform key identifier for the recurring donation in your source platform. See Platform Key Syntax for the format. |
Worked example
If your Raisely recurring donation has Subscription UUID b6f623c0-2a74-11ec-91e7-b9ad139ed3a4, set the Platform Key field on your Salesforce gift commitment record to:
raisely:b6f623c0-2a74-11ec-91e7-b9ad139ed3a4
See Platform Key Syntax for the full list of platform prefixes and identifier formats.
Map Gift Transaction Records#
For each existing gift transaction record in Salesforce that should link to your source platform, set the following field value:
| Salesforce Field | API Name | Value |
|---|---|---|
| Platform Key | md_npc_pack__Platform_Key__c |
The platform key identifier for the donation in your source platform. See Platform Key Syntax for the format. |
Worked example
If your Raisely donation has Donation UUID 55f1ef50-f15f-11ee-ad05-719b0288d1dc, set the Platform Key field on your Salesforce gift transaction record to:
raisely:55f1ef50-f15f-11ee-ad05-719b0288d1dc
See Platform Key Syntax for the full list of platform prefixes and identifier formats.
Map Person Account Records#
A single person account can have multiple identifiers. For example, the same person might exist across several source platforms. MoveData stores these identifiers on a child object called Account Platform Key (movedata__Account_Platform_Key__c).
To map a person account, create an Account Platform Key record in Salesforce and set the following field values:
| Salesforce Field | API Name | Value |
|---|---|---|
| Account | movedata__Account__c |
The person account record in Salesforce. |
| Platform Key | movedata__Platform_Key__c |
The platform key identifier for the person in your source platform. See Platform Key Syntax for the format. |
Worked example
If your Raisely supporter has Person UUID 6fe7fd90-100f-11ea-b92d-574a5da4fffc, set the Platform Key field on the Account Platform Key record to:
raisely:6fe7fd90-100f-11ea-b92d-574a5da4fffc
See Platform Key Syntax for the full list of platform prefixes and identifier formats.
Map Organisation Account Records#
Like person accounts, organisation accounts can have multiple identifiers across different source platforms. MoveData stores these on the same Account Platform Key child object (movedata__Account_Platform_Key__c).
To map an organisation account, create an Account Platform Key record and set the following field values:
| Salesforce Field | API Name | Value |
|---|---|---|
| Account | movedata__Account__c |
The account record in Salesforce. |
| Platform Key | movedata__Platform_Key__c |
The platform key identifier for the organisation in your source platform. See Platform Key Syntax for the 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.
Map Opportunity Records#
For each existing opportunity record in Salesforce that should link to your source platform, set the following field value:
| Salesforce Field | API Name | Value |
|---|---|---|
| Platform Key | movedata__Platform_Key__c |
The platform key identifier for the sale record in your source platform. See Platform Key Syntax for the format. |
Worked example
If your Raisely transaction has Donation UUID 55f1ef50-f15f-11ee-ad05-719b0288d1dc, set the Platform Key field on your Salesforce opportunity record to:
raisely:55f1ef50-f15f-11ee-ad05-719b0288d1dc
See Platform Key Syntax for the full list of platform prefixes and identifier formats.
When are opportunities used in NPC?
NPC uses the Gift Transaction object for donations. Opportunities are only used for non-donation transactions such as merchandise sales, paid event registrations, and raffle ticket sales.