Note: this information is from 2018 and was applicable to the v1 Pardot Connector. The new v2 connector mapping is likely different.
Here are some notes about the initial sync that occurs between Pardot and Salesforce (SFDC).
When you first enable and validate the Salesforce Connector in Pardot, a synch will begin automatically. You will not have a chance to define how fields sync between Pardot and Salesforce, and how data overrides work – you are at the mercy of the default mapping that’s been preset for you.
Don’t like how the default sync is set up? Want to have total control of the initial mapping between Pardot and Salesforce?I recommend that you do 3 things:
- Configure the connector so that Salesforce is prevented from creating new Pardot Prospect records (at least initially).
- Ensure that the Salesforce user who’s been set up as the Pardot Connector User is blind to all Leads and Contacts. Your Salesforce administrator will have to set this up prior to verifying and enabling the Pardot Connector.
- If you have any assigned Prospects in your Pardot instance, mark them as “Do Not Sync With CRM” using an automation rule. Anyone who’s assigned will be automatically created as a Lead in Salesforce when you verify the Connector (this will happen because step #2 ensures that Pardot will never find an existing Lead for an Assigned prospect – they’re all hidden. So it will attempt to create a new Lead).
These setting will ensure that no Prospects are synched initially. This gives you time to configure the kind of integration mapping that you desire.
Remember that you can do a “practice integration” by connecting Pardot to a Salesforce Sandbox, and even by getting a free Pardot Training Environment to protect your main Pardot during integration testing.
In addition, here is a table that shows field IDs for the default mapping for our organization. Some of these field types might depend on our specific Salesforce setup:
| Pardot field name | Pardot field ID | salesforce.com Field Name | Type | In case of conflicting values: |
|---|---|---|---|---|
| Years In Business | years_in_business | Text | ||
| Website | website | Website | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Territory | territory | Text | ||
| Source | source | LeadSource | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Scoring Category Last Scored At | last_scored_at | pi__Pardot_Last_Scored_At__c | Date | If Pardot and Salesforce values differ when data sync occurs: Use Pardot’s value |
| Salutation | salutation | Salutation | Dropdown | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Province | state | MailingState | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Postal Code | zip | MailingPostalCode | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Phone | phone | Phone | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Pardot Hard Bounced | pardot_hard_bounced | pi__pardot_hard_bounced__c | Checkbox | Pardot is the master. Map this lead field to the contact field so the contact record pulls in the data. This field is hidden until a hard bounce. Even if the Do Not Email and Opted Out fields are cleared, the bounce history is retained on the prospect record and the Pardot Hard Bounced, Email Bounced Reason and Email Bounced Date fields are not cleared. If the hard bounce was the result of an invalid email address, adding a valid email address clears the Pardot Hard Bounced field. |
| Opted Out | opted_out | HasOptedOutOfEmail | Checkbox | More about Opt-Out synch behaviour |
| Last Name | last_name | LastName | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Job Title | job_title | Title | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Industry | industry | Industry | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| First Name | first_name | FirstName | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Fax | fax | Fax | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Employees | employees | NumberOfEmployees | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Email Bounced Reason | email_bounced_reason | EmailBouncedReason | Text | More details in the official field mapping docs |
| Email Bounced Date | email_bounced_date | EmailBouncedDate | Text | More details in the official field mapping docs |
| Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value
| |||
| Do Not Email | is_do_not_email | Checkbox | ||
| Do Not Call | is_do_not_call | Checkbox | ||
| Department | department | Department | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Country | country | MailingCountry | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Company | company | Company | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Comments | comments | Textarea | ||
| City | city | MailingCity | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Annual Revenue | annual_revenue | AnnualRevenue | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Address Two | address_two | MailingStreet | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
| Address One | address_one | Street | Text | If Pardot and Salesforce values differ when data sync occurs: Use Salesforce’s value |
The Pardot documentation has more information about standard sync behaviours.
And, this document shows how to change the sync behaviour for a particular pair of fields. Keep in mind that data priorities between Pardot and Salesforce cannot be changed for certain fields (For example, the “Opted Out” field – although that field can be remapped). These special rules are explained in the official field mapping documentation.
Finally, you should be aware that – regardless of the sync behaviour you’ve set up – Pardot will never use a blank value to overwrite an existing field value. The nuances of how Pardot acts on blank values are explained in this post from The Spot for Pardot.