--- title: "The Field Mapping Guide: Stopping Data Loss Between Marketing (HubSpot) and Sales (Salesforce)" date: 2025-12-29 author: "Vincent DeCastro" categories: - name: "Uncategorized" url: "/category/uncategorized.md" --- # The Field Mapping Guide: Stopping Data Loss Between Marketing (HubSpot) and Sales (Salesforce) **Executive Summary:** You cannot run a high-precision Account-Based Marketing (ABM) campaign on a “dirty” database. The most common failure point we see isn’t the creative or the strategy—it’s the **Integration Settings**. If your **HubSpot** (or Marketo) isn’t speaking the exact same language as your **Salesforce** instance, your ABM signals are falling into a black hole. **The ABM Agency** acts as your technical “plumber.” We fix the leaks in your revenue pipe so that when Marketing generates a lead, Sales actually sees it—with all the context intact. --- ## **The Core Problem: The “Sync Black Hole”** In a perfect world, data flows seamlessly. In reality, you likely battle: - **Duplicates:** The same lead exists three times, splitting the activity history. - **Orphaned Records:** Leads that don’t belong to an Account, meaning 6sense/Demandbase can’t score them. - **Overwrite Wars:** HubSpot updates a field, then Salesforce overwrites it back 5 minutes later with old data. Here are the three specific “Fixes” we implement to stabilize your stack for ABM. --- ## **Fix #1: The “Domain Normalization” Protocol** *Why it kills ABM:* ABM tools like **6sense** and **Demandbase** rely on the **Website Domain** (e.g., `dow.com`) to match people to companies. If Salesforce lists a website as `https://www.dow.com/en-us` and HubSpot lists it as `dow.com`, the match fails. Your ABM platform thinks they are two different companies. **The “Hands-on” Fix:** 1. **The Audit:** We export your Account domains and scan for inconsistencies (http vs https, trailing slashes, subdomains). 2. **The Automation:** We implement a **Workflow in HubSpot** (Operations Hub) to strip prefixes (`www.`, `https://`) before the data syncs to Salesforce. 3. **The Result:** 100% clean domain matching, allowing your ABM platform to correctly associate every lead with its Target Account. --- ## **Fix #2: The “Lead Source” Truth Table** *Why it kills ABM:* Sales needs to know *where* a lead came from. Marketing needs to know *what* influenced them. The “Lead Source” field is often a mess of “Trade Show,” “Web,” and “Import 2022.” **The “Hands-on” Fix:** 1. **Stop the Overwrite:** We configure the Salesforce Connector settings to “Block” updates to the original `Lead Source` field once it is populated. 2. **Create “Most Recent Source”:** We map a custom HubSpot property `Latest Source` to a custom Salesforce field. This allows `Lead Source` to remain “Original” (First Touch) while `Latest Source` updates with every new ABM campaign interaction (Last Touch). 3. **Drill-Down Fields:** We map `Lead Source Detail` to capture the granular UTM parameters (e.g., `linkedin-abm-q3-campaign`). --- ## **Fix #3: The “Ghost Contact” Enrichment (ZoomInfo)** *Why it kills ABM:* A prospect fills out a form with just an email: `john.doe@company.com`. Sales ignores it because it lacks a Job Title, Phone Number, or State. It sits in “MQL Purgatory.” **The “Hands-on” Fix:** 1. **The Middleware:** We set up **ZoomInfo FormComplete** or a backend enrichment webhook. 2. **The Mapping:** Before the lead is pushed to Salesforce, we ping ZoomInfo. - *Input:* `john.doe@company.com` - *Output:* Job Title, Seniority Level, Direct Phone, HQ Location. 3. **The Routing:** Now that we know John Doe is the “VP of Engineering” in “Texas,” we can use **Salesforce Assignment Rules** to route him to the correct Enterprise Rep for that region. --- ## **Frequently Asked Questions (FAQ)** ### **Why are my HubSpot leads creating duplicates in Salesforce?** This usually happens because the **“Deduplication Rule”** in Salesforce is too strict or doesn’t match the HubSpot identifier. If HubSpot tries to sync a lead, and Salesforce blocks it due to a strict rule, HubSpot might try to force-create a new one, or the sync fails entirely. We adjust the “Matching Rule” in Salesforce to use *Email Address* as the unique identifier to prevent this. ### **Should we use the Salesforce “Lead” object or just “Contacts”?** For ABM, we strongly recommend a **“Lead-to-Account Matching”** strategy. While Salesforce defaults to keeping Leads separate from Accounts, ABM requires you to view *everyone* in the context of the Account. We use tools (or custom flows) to automatically convert Leads to Contacts and attach them to the Account object as soon as the domain matches. ### **Can you fix my messy picklist values?** Yes. “State/Country” picklists are a nightmare (e.g., “US” vs. “USA” vs. “United States”). We implement **State and Country/Territory Picklists** in Salesforce and map them strictly to HubSpot to prevent sync errors caused by validation rule failures. --- ### **Next Step: The “Sync Health” Check** Do you have thousands of “Sync Errors” sitting in your HubSpot or Marketo integration log? Is Sales complaining that “Marketing leads have no phone numbers”? **The ABM Agency** can perform a **Connector Audit**. We log into your integration settings, review your field mappings, and produce a “Red/Yellow/Green” report on your data health.