Skip to content
SF Ben Con 26: Early Bird Sign-Up
Salesforce Ben
  • Events
  • Career
  • AppAssessor
  • Salesforce News
  • Articles by Role
    • Admins
    • DevOps
    • Developers
    • Marketers
    • Consultants
    • Architects
    • Business Analysts
  • Resources
  • Where to Start
  • Salesforce Certification List
  • How to Get Certified
  • Free Salesforce Practice Exams
    • Admin Practice Exam
    • Platform App Builder Practice Exam
    • Platform Developer 1 Practice Exam
  • How to Get a Job in Salesforce

Find us on:

Salesforce Ben
  • Events
  • Career
  • AppAssessor
  • Salesforce News
  • Articles by Role

      Articles by role:

    • Admins
    • DevOps
    • Developers
    • Marketers
    • Consultants
    • Architects
    • Business Analysts
    • Featured

      The Great Salesforce Job Market Reset

      By Sasha Semjonova

      December 09, 2024
      How to Avoid Bad Salesforce Partners: The Three-Question Test

      By Jon Cline

      January 08, 2025
  • Resources
Email
LinkedIn
Facebook
Twitter
  • Newsletter
SF Ben Con 26: Early Bird Sign-Up
  • Newsletter
  • Events
  • Career
  • AppAssessor
  • Salesforce News
  • Articles by Role

      Articles by role:

    • Admins
    • DevOps
    • Developers
    • Marketers
    • Consultants
    • Architects
    • Business Analysts
    • Featured

      The Great Salesforce Job Market Reset

      By Sasha Semjonova

      December 09, 2024
      How to Avoid Bad Salesforce Partners: The Three-Question Test

      By Jon Cline

      January 08, 2025
  • Resources

What's trending

Salesforce to Hire 1,000 Grads and Interns, Defying AI Job-Killing Fears
Microsoft Blames Slack’s Growth on ‘Inferior Capabilities’ Amid Recent Lawsuit
Salesforce’s New AI Data Setting Sparks Debate Over What Customers Agreed To
Is Salesforce Flow Really at Risk of Getting Replaced by AI Vendors?
Top 8 Salesforce Summer ’26 Features for Developers

UPCOMING EVENTS

Tableau Conference 2026

05
May

San Diego, CA

Salesforce Official

What It Takes to Operationalize AI in Salesforce

07
May

Virtual

Webinar

Wir sind Ohana 2026

08
May

Berlin, Germany

Community

True North Dreamin’ 2026

11
May

Toronto, Canada

Community

Managing Salesforce Integrations in 2026

12
May

Virtual

SF Ben Webinar
See more
Share
Email
LinkedIn
Facebook
Twitter
Marketers / Account Engagement (Pardot)

Pardot Field Sync Behavior Change – What to Do Ahead of the Winter ’20 Release

By Lucy Mazalon

Published September 02, 2019
Updated March 25, 2025

There will be changes to Pardot Field Sync Behaviour between Salesforce and Pardot, taking effect on October 14, 2019, in line with the Salesforce Winter ’20 release.

You will have received an email last week, calling you to action: “ACTION MAY BE REQUIRED: Important update to Pardot field sync behavior on October 14, 2019”

Depending on how your Pardot fields are currently mapped to Salesforce, you may not need to take any action – but it’s worth checking, and not leaving it to chance!

I have had a few people ask me, what should I do? This post covers just that.

What is the Pardot Field Sync Behaviour Change?

This change is all to do with how Pardot and Salesforce fields behave when mapped together. When fields are mapped between the two tools, you have 3 options for field sync behaviour:

  • Choose Salesforce as the Master
  • Choose Pardot as the Master
  • Choose the most recently updated as the Master

This is great and easy to follow: whenever there’s a difference in the fields between SF and Pardot, you know which one will overrule the other.

However, blank fields are treated differently – known as ‘null value sync’. The fundamental rule to brandish into your mind is this: a field with a value will always trump a blank (null) field.

Currently, if Pardot is the master for a field, and it’s blank, it will retain an empty value – even if the associated lead has a value in that field. After October, any syncing Salesforce fields with ‘non-NULL’ values (basically, Salesforce lead or contact fields that aren’t blank) will be able to overwrite empty Prospect fields.

Reasons to Pay Attention

Aside from automatically populating prospect fields you want to keep blank, the change in sync behavior could have other consequences:

  • Could expose information on forms to prospects.
  • Your organisation may leave this field blank in Pardot to capture this data from prospects on forms.

What Should You Do?

There is some advice provided by Pardot:

“If fields containing empty strings in your Pardot prospects are intentional, replace those empty strings with a value that better reflects what you are attempting to indicate with the empty string (for example, NULL, None, N/A, etc.).”

What I have done is outlined this as a 3-step process:

Step 1: Identify Prospect Fields where Pardot is the Master

Find out which fields are using Pardot as the master. There is (currently) no efficient way to do this – for instance, you cannot export all Pardot fields at once to report on.

On the Pardot Settings tab, under ‘Prospect Fields’, first look at which fields have a reference in the “SALESFORCE.COM FIELD NAME” column.

By clicking into each field, you can see which side (Salesforce or Pardot) is the master.

Record the fields in a spreadsheet, with their field type, especially marking which fields have Pardot defined as the master.

You can make this part of a wider field audit/custom field clean up/Data Inventory project.

Note: don’t forget the default and custom fields are split out in separate sections!

Note 2: you will only need to do this for Prospect fields; Prospect Account/Opportunity/Custom Object fields are all read-only.

Step 2: Consider each field

Consider how each field works, asking yourself the question:

→ Is there a reason we are keeping this field blank in Pardot? (refer back to the “Reasons to Pay Attention” section for a couple of ideas).

Step 3: Update Data via Import

Be careful! Do not do any mass data updates unless you are entirely sure about what you’re doing! Once you have exported your prospect database, always copy and maintain an export of the current data, just in case.

As Pardot suggest, fill in placeholder values for the records that have blank values (eg. NULL, None, N/A), then reimport.

Also be careful of different Field Types involved…

Text fields are simple to work with. For Picklists, you may have to add a new picklist option in Salesforce called ‘[blank]’ or similar – but this is can cause havoc with formulas, automation, and reporting on the Salesforce side.

Remember to monitor sync errors for a few days following any big changes to syncing records.

Summary

I recommend you closely evaluate which Pardot fields you truly want to keep blank. When taking action and you are unsure of anything, seek help from a Pardot expert.

The Author

Lucy Mazalon

Lucy is the Finance Director at Salesforce Ben. She is a 10x certified Marketing Champion and founder of The DRIP.

More like this:

Marketers

How to Drive Your Marketing Cloud Engagement Use Case to Its Destination

By Alina Makarova

May 01, 2026
Marketers

How Salesforce Marketers Can Introduce AI into Their Data Strategy

By Timo Kovala

March 18, 2026
Marketers

How Salesforce Is Rebuilding Marketing Cloud for the Age of AI

By Charmy Gajera

March 09, 2026

Leave a Reply Cancel reply

Newsletter:

By signing up you agree to our Terms of Use and Privacy Policy.

Find us on:

Salesforce Ben

Salesforce Ben
Unit G.01
189-190 Shoreditch High Street
London
United Kingdom
E1 6HU

  • Where to Start
  • Salesforce Certification List
  • How to Get Certified
  • Free Salesforce Practice Exams
    • Admin Practice Exam
    • Platform App Builder Practice Exam
    • Platform Developer 1 Practice Exam
  • How to Get a Job in Salesforce
  • Events
  • Career
  • AppAssessor
  • Salesforce News
  • Articles by Role
  • Resources
  • Admins
  • DevOps
  • Developers
  • Marketers
  • Consultants
  • Architects
  • Business Analysts
  • About Us
  • Contact Us
  • Write For Us
  • Influencer Program
  • Advertise With Us
  • Pledge 1%
  • Privacy Policy
  • Change Cookie Preferences

© 2014-2026 SalesforceBen.com