Map MoveData to Existing Records | MoveData Help Center

If you need MoveData to "match" against existing records, then a mapping exercise must be undertaken to ensue the existing records have the necessary identifiers for MoveData to determine a match. Failure to do so may result in MoveData being unable to find a matched record and a duplicate record created as a result.

Contacts

Keys for contacts are stored on a child object called movedata__Contact_Platform_Key__c.

Salesforce Field	Comment
`movedata__Contact__c`	ID of the Contact Record
`movedata__Platform_Key__c`	ID of the Contact record in the source platform

MoveData uses your Salesforce Duplicate and Matching Rules

If a match based on platform key is not determined, MoveData will run your Duplicate and Matching rules. As such, mapping Contact records could be considered optional optional given your duplicate rules will otherwise handle contact matching.

Reference: Configure Duplicate Rules

Campaigns

Keys for campaigns are stored on the Campaign object.

Salesforce Field	Comment
`movedata__Platform_Key__c`	ID of the page record in the source platform
`movedata__Protect_Name__c`	Set `True` if you wish to protect the name of the mapped record in Salesforce (else, the integration may update to the name information issued by the source platform). In practice, only campaigns which represent the top level campaign in your source platform get protected.

Recurring Donations

Keys for campaigns are stored on the Recurring Donation object.

Salesforce Field	Comment
`md_npsp_pack__Platform_Key__c`	ID of the recurring donation record in the source platform

Opportunities

Keys for campaigns are stored on the Opportunity object.

Salesforce Field	Comment
`movedata__Platform_Key__c`	ID of the donation record in the source platform

Opportunity records are not commonly updated, so it is at your discretion if you choose to perform this step. The only practical scenario where Opportunity mapping comes into play is where:

A refund is issued for an Opportunity processed prior to MoveData (without mapping in place, the integration will be unable to find the record to refund and produce an error)
A change is made to an Opportunity record processed prior to MoveData (without mapping in place, the integration will create a new Opportunity record)

Platform-Specific Syntax

Because identifiers can repeat both within and across the source platforms you connect, MoveData will prefix your source platform IDs with additional information.

Facebook

PayPal Giving Fund

Sales (Raisely, Funraisin)

Raisely

All IDs are prefixed with raisely:

Object	Area	Example	Use
Contact	Person UUID	`6fe7fd90-100f-11ea-b92d-574a5da4fffc`	`raisely:6fe7fd90-100f-11ea-b92d-574a5da4fffc`
Campaign (Campaign Records)	Campaign Profile UUID	`aa88bd90-562c-11eb-bf24-6bd493dd10e5`	`raisely:aa88bd90-562c-11eb-bf24-6bd493dd10e5`
Campaign (Team and Fundraiser Profile records)	Profile UUID	`74a298b0-6cdc-11eb-b501-399fd2e468ed`	`raisely:74a298b0-6cdc-11eb-b501-399fd2e468ed`
Recurring Donation	Subscription UUID	`b6f623c0-2a74-11ec-91e7-b9ad139ed3a4`	`raisely:b6f623c0-2a74-11ec-91e7-b9ad139ed3a4`
Opportunity	Donation UUID	`55f1ef50-f15f-11ee-ad05-719b0288d1dc`	`raisely:55f1ef50-f15f-11ee-ad05-719b0288d1dc`

Funraisin'

Object	Area	Example	Use
Contact	Member ID	`5478`	`funraisin:5478`
Campaign (Event records)	Event ID	`1`	`funraisin:event:1`
Campaign (Event ID not provided)			`funraisin:funraisin`
Campaign (Team and Fundraiser records)	History ID	`2938`	`funraisin:history:2938`
Campaign (Page records)	Page ID	`49`	`funraisin:page:49`
Recurring Donation	Scheduled Donation ID	`29`	`funraisin:recurring:29`
Opportunity	Donation ID	`860`	`funraisin:8680`

Notes

Campaigns:
- If an Event ID is provided, MoveData will create an equivalent campaign which will parent Team and Fundraiser records like My Event → Joe Smith
- If an Event ID is not provided, MoveData will parent Team and Fundraiser records under the generic Funraisin' campaign like Funraisin' → Susie Wong's Bake Sale
Connecting Multiple Funraisin Sites:
- If you connect multiple Funraisin sites, you should ensure a unique prefix is added for each site
  - This is because Funraisin' issues sequential IDs on a per-site basis and thus IDs could overlap between sites
- MoveData will inject the unique prefix added into your values
- For example, if you add the unique prefix example MoveData will use:
  - Contact: funraisin:example:5478
  - Campaign (Event): funraisin:example:event:1
  - Campaign (Team or Fundraiser): funraisin:example:history:2938
  - Etc

JustGiving

With the exception of campaigns, all IDs are prefixed with justgiving:.

For campaigns:

Event IDs are prefixed with justiving:event:
Campaign IDs are prefixed with justgiving:campaign:
Page IDs are prefixed with justgiving:pages:

Object	Area	Example	Use
Contact	User ID	`77540128`	`justgiving:77540128`
Campaign (Event records)	Event ID	`6202476`	`justgiving:event:6202476`
Campaign (Campaign records)	Campaign ID	`fb1f8570-39e3-4253-9e0a-c2c2a16a20f9`	`justgiving:campaign:fb1f8570-39e3-4253-9e0a-c2c2a16a20f9`
Campaign (Neither Campaign nor Event ID provided)			`justgiving:justgiving`
Campaign (Team and Fundraiser records)	Page ID	`15337999`	`justgiving:pages:15337999`
Recurring Donation	User ID and Recurring Mandate Creation Date		`justgiving:53187580_20140909`
Opportunity	Donation ID	`299921264`	`justgiving:299921264`

Notes

Campaigns:
- If an Event ID or Campaign ID is provided, MoveData will create an equivalent campaign which will parent Team and Fundraiser records like London Marathon → Joe Smith Runs London
- If an Event ID or Campaign ID is not provided, MoveData will parent Team and Fundraiser records under the generic JustGiving campaign like JustGiving → Susie Wong's Bake Sale
Recurring Donations:
- JustGiving does not provide an ID thus the value must be derived
- Derive the date value from Recurring Mandate Creation Date in YYYYMMDD format like 20140909
- Combine User ID and your YYYYMMDD value with an underscore (_) like 53187580_20140909

Enthuse

All IDs are prefixed with enthuse:

Object	Area	Example	Use
Contact	Supporter ID	`883591`	`enthuse:883591`
Campaign (Enthuse Created Event)	Company ID	`363`	`enthuse:363`
Campaign (Charity Created Event)	Event Page ID	`20178`	`enthuse:20178`
Campaign (Neither Campaign nor Event record provided)			`enthuse:enthuse`
Campaign (Team and Fundraiser records)	PF ID	`731863`	`enthuse:731863`
Recurring Donation	Schedule ID	`109375`	`enthuse:109375`
Opportunity	Payment Transaction GUID	`db71c8d5-c5a8-448c-9aee-d7d72c3fcf61`	`enthuse:db71c8d5-c5a8-448c-9aee-d7d72c3fcf61`

Notes

If an Event Page ID or Company ID is provided, MoveData will create an equivalent campaign which will parent Team and Fundraiser records like London Marathon → Joe Smith Runs London
If an Event Page ID or Company ID is not provided, MoveData will parent Team and Fundraiser records under the generic Enthuse campaign like Enthuse → Susie Wong's Bake Sale
List of Company IDs: https://docs.google.com/spreadsheets/d/1amx23I_8kkepA5s0yPNdCnEHQfj8PzXCUBKslcNtnWM/edit#gid=1139107291 (published by Enthuse)

Grassrootz

With the exception of campaigns, all IDs are prefixed with grassrootz:.

For campaigns:

Campaign IDs are prefixed with grassrootz:campaign:
Team IDs are prefixed with grassrootz:team:
Fundraiser IDs are prefixed with grassrootz:fundraiser:

Object	Area	Example	Use
Contact	AccountId	`469822`	`grassrootz:469822`
Campaign (Campaign Records)	Campaign ID	`5531`	`grassrootz:campaign:5531`
Campaign (Team records)	Team ID	`13042`	`grassrootz:team:13042`
Campaign (Fundraiser records)	Fundraiser ID	`123948`	`grassrootz:fundraiser:123948`
Recurring Donation	Subscription ID	`1749`	`grassrootz:1749`
Opportunity	Donation ID	`1501852`	`grassrootz:1501852`

TapRaise

All IDs are prefixed with tapraise:

Object	Area	Example	Use
Contact	Person UUID	`a6adb3e4-9dfb-41ba-9af2-4a8326a53f84`	`tapraise:a6adb3e4-9dfb-41ba-9af2-4a8326a53f84`
Agreement	Transaction Origin UUID	`9eac2a84-8564-4be8-9c6d-2cee145c4e5f`	`tapraise:9eac2a84-8564-4be8-9c6d-2cee145c4e5f`
Payment	Transaction UUID	`ff5d091a-a37a-4ea2-a704-f0c1157e4501`	`tapraise:ff5d091a-a37a-4ea2-a704-f0c1157e4501`

Good2Give

All IDs are prefixed with g2g:

Object	Area	Example	Use
Contact
Account
Campaign (Good2Give Parent)			`g2g:good2give`
Campaign (Employer Campaign Enabled)	Employer Name	`google`	`g2g:google`
Campaign (Charity Project Campaigns Enabled)	Charity Project Name	`special-needs`	`g2g:special-needs`
Campaign (Employer Campaigns and Charity Project Campaigns Enabled)	Employer Name and Charity Project Name	`google` and `special-needs`	`g2g:google-special-needs`
Opportunity

Notes

When deriving values from Employer Name and Charity Project Name, ensure you convert to lowercase and replace spaces with hyphens (-)
If you have Employer Campaigns and Charity Project Campaigns enabled you can derive value by combining the Employer Name and Charity Project Name with a hyphen (- where [Employer Name]-[Charity Project Name] like google-special-needs)

DoGooder

All IDs are prefixed with dogooder:

Object	Area	Example	Use
Contact	DoGooder does not have the concept of a Contact ID
Campaign	Campaign ID	`612`	`dogooder:612`
Action	Action ID	`7305`	`dogooder:7305`