{"id":90123,"date":"2026-01-08T21:52:51","date_gmt":"2026-01-09T05:52:51","guid":{"rendered":"https:\/\/rightwave.com\/rwi\/?p=90123"},"modified":"2026-01-08T22:07:41","modified_gmt":"2026-01-09T06:07:41","slug":"hubspot-salesforce-integrations-the-landmines-every-marketing-ops-team-should-avoid","status":"publish","type":"post","link":"https:\/\/rightwave.com\/rwi\/hubspot-salesforce-integrations-the-landmines-every-marketing-ops-team-should-avoid","title":{"rendered":"HubSpot + Salesforce Integrations: The Landmines Every Marketing Ops Team Should Avoid"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\n

<\/h2>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

If you\u2019ve ever heard someone say \u201cI don\u2019t trust the data in HubSpot\u201d<\/em> or \u201cSalesforce is creating a mess for marketing\u201d<\/em>, chances are the problem isn\u2019t the tools \u2014 it\u2019s how the integration was set up.<\/p>\n

A recent conversation in the MO Pros community perfectly captured the real-world pain<\/em> teams face when working with HubSpot<\/span><\/span><\/strong> and Salesforce<\/span><\/span><\/strong> together \u2014 especially when an organization migrates Sales from HubSpot CRM to Salesforce.<\/p>\n

From duplicate records to broken company data and uncontrolled syncs, these issues show up months later<\/em>, when fixing them becomes expensive and disruptive.<\/p>\n

From RightWave\u2019s perspective, here\u2019s what we\u2019ve learned \u2014 and what we strongly recommend setting up before<\/strong> data starts flowing.<\/p>\n

1. Always Use a Dedicated Integration User (This Is Non-Negotiable)<\/h2>\n

One of the most common mistakes we see:
The HubSpot\u2013Salesforce integration is authenticated using a real person\u2019s<\/em> Salesforce user.<\/p>\n

Why this backfires:<\/p>\n

    \n
  • \n

    Permission changes break syncs unexpectedly<\/p>\n<\/li>\n

  • \n

    Auditing becomes impossible<\/p>\n<\/li>\n

  • \n

    Troubleshooting turns into guesswork<\/p>\n<\/li>\n<\/ul>\n

    Best practice:<\/strong>
    Create a dedicated Salesforce integration user<\/strong> with:<\/p>\n

      \n
    • \n

      Its own profile<\/p>\n<\/li>\n

    • \n

      Its own role<\/p>\n<\/li>\n

    • \n

      Explicit permissions<\/p>\n<\/li>\n<\/ul>\n

      This user becomes the gatekeeper<\/em> of what data is even allowed to reach HubSpot.<\/p>\n

      \n

      If the integration user can\u2019t see a record in Salesforce, HubSpot won\u2019t sync it.
      That\u2019s not a limitation \u2014 that\u2019s a feature.<\/p>\n<\/blockquote>\n

      2. Selective Sync Isn\u2019t Optional \u2014 It\u2019s a Safety Net<\/h2>\n

      Many teams default to \u201csync everything and clean later.\u201d<\/em>
      That approach almost always leads to regret.<\/p>\n

      Selective Sync allows you to:<\/p>\n

        \n
      • \n

        Control which<\/strong> Salesforce records flow into HubSpot<\/p>\n<\/li>\n

      • \n

        Prevent junk, legacy, or partial data from polluting marketing<\/p>\n<\/li>\n

      • \n

        Reduce sync-related overwrites<\/p>\n<\/li>\n<\/ul>\n

        But there\u2019s a catch:<\/p>\n

          \n
        • \n

          It requires Salesforce Enterprise<\/strong><\/p>\n<\/li>\n

        • \n

          It requires deep Salesforce knowledge<\/strong><\/p>\n<\/li>\n

        • \n

          HubSpot support doesn\u2019t configure this for you<\/p>\n<\/li>\n<\/ul>\n

          That\u2019s why we recommend setting it up at day zero<\/strong>, not after damage is done.<\/p>\n

          3. Use an Inclusion List to Throttle Data Intelligently<\/h2>\n

          Selective Sync controls visibility<\/em>.
          Inclusion Lists control volume<\/em>.<\/p>\n

          Together, they let you answer critical questions:<\/p>\n

            \n
          • \n

            Should all leads sync immediately?<\/p>\n<\/li>\n

          • \n

            Should only MQLs or Sales-ready records flow back?<\/p>\n<\/li>\n

          • \n

            What data should never<\/em> touch HubSpot?<\/p>\n<\/li>\n<\/ul>\n

            Think of Inclusion Lists as your traffic controller<\/strong> \u2014 especially important in high-volume Salesforce orgs.<\/p>\n

            4. The \u201cCompanies\u201d Trap: One of HubSpot\u2019s Most Painful Gotchas<\/h2>\n

            This one surprises even experienced teams.<\/p>\n

            Once Companies<\/strong> start syncing from Salesforce<\/em>:<\/p>\n

              \n
            • \n

              HubSpot does not allow company merges<\/strong><\/p>\n<\/li>\n

            • \n

              Duplicate companies pile up fast<\/p>\n<\/li>\n

            • \n

              Marketing loses clean account-level reporting<\/p>\n<\/li>\n<\/ul>\n

              This usually happens because:<\/p>\n

                \n
              • \n

                Salesforce Accounts aren\u2019t deduplicated properly<\/p>\n<\/li>\n

              • \n

                Naming conventions aren\u2019t standardized<\/p>\n<\/li>\n

              • \n

                The integration is allowed to create companies freely<\/p>\n<\/li>\n<\/ul>\n

                Bottom line:<\/strong>
                Account hygiene in Salesforce directly determines sanity in HubSpot.<\/p>\n

                5. Duplicate Contacts: Email Is the Only Truth HubSpot Trusts<\/h2>\n

                HubSpot deduplicates contacts strictly by email address<\/strong>.<\/p>\n

                What this means in practice:<\/p>\n

                  \n
                • \n

                  Two Salesforce records with different emails = two HubSpot contacts<\/p>\n<\/li>\n

                • \n

                  Two Salesforce records with the same email = unpredictable overwrites<\/p>\n<\/li>\n

                • \n

                  HubSpot syncs to whichever Salesforce record was updated last<\/p>\n<\/li>\n<\/ul>\n

                  If duplicates already exist in Salesforce:<\/p>\n

                    \n
                  • \n

                    Clean them before<\/em> turning on sync<\/p>\n<\/li>\n

                  • \n

                    Identify which Salesforce record is actively syncing<\/p>\n<\/li>\n

                  • \n

                    Merge carefully \u2014 or risk breaking the integration<\/p>\n<\/li>\n<\/ul>\n

                    6. Leads vs Contacts: Choose Carefully (and Early)<\/h2>\n

                    If your Salesforce org uses Leads heavily<\/strong>, be cautious.<\/p>\n

                    We\u2019ve seen teams assume:<\/p>\n

                    \n

                    \u201cHubSpot \u2194 Salesforce is 1:1\u201d<\/p>\n<\/blockquote>\n

                    That\u2019s rarely true when Leads are involved.<\/p>\n

                    Without clear rules:<\/p>\n

                      \n
                    • \n

                      One HubSpot contact can bounce between Salesforce Leads and Contacts<\/p>\n<\/li>\n

                    • \n

                      Ownership, lifecycle stage, and attribution get messy<\/p>\n<\/li>\n

                    • \n

                      Reporting becomes unreliable<\/p>\n<\/li>\n<\/ul>\n

                      If you\u2019re unsure \u2014 simplify first, then scale.<\/p>\n

                      7. Think in Data Flow, Not Just Sync Settings<\/h2>\n

                      The most overlooked question in integrations:<\/p>\n

                      \n

                      When should data flow \u2014 and when shouldn\u2019t it?<\/em><\/p>\n<\/blockquote>\n

                      Ask upfront:<\/p>\n

                        \n
                      • \n

                        What data must always sync?<\/p>\n<\/li>\n

                      • \n

                        What data should sync only after qualification?<\/p>\n<\/li>\n

                      • \n

                        What data should never<\/strong> sync?<\/p>\n<\/li>\n<\/ul>\n

                        Good integrations aren\u2019t \u201calways on.\u201d
                        They\u2019re intentionally designed<\/strong>.<\/p>\n

                        RightWave\u2019s Take: Integrations Are Architecture, Not Checkboxes<\/h2>\n

                        We see HubSpot\u2013Salesforce integrations fail not because teams lacked tools \u2014 but because they lacked governance<\/strong>.<\/p>\n

                        At RightWave, we approach integrations like systems design:<\/p>\n

                          \n
                        • \n

                          Clear ownership<\/p>\n<\/li>\n

                        • \n

                          Controlled access<\/p>\n<\/li>\n

                        • \n

                          Intentional data flow<\/p>\n<\/li>\n

                        • \n

                          Long-term scalability<\/p>\n<\/li>\n<\/ul>\n

                          If you\u2019re stepping into a new role, inheriting an integration, or planning a CRM transition \u2014 it\u2019s worth slowing down before<\/strong> flipping the switch.<\/p>\n

                          Because fixing bad data later always costs more than setting it up right the first time.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

                          If you\u2019ve ever heard someone say \u201cI don\u2019t trust the data in HubSpot\u201d or \u201cSalesforce is creating a mess for marketing\u201d, chances are the problem isn\u2019t the tools \u2014 it\u2019s how the integration was set up. A recent conversation in the MO Pros community perfectly captured the real-world pain teams face when working with HubSpot…<\/p>\n","protected":false},"author":45,"featured_media":90128,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-90123","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-welcome"],"_links":{"self":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/posts\/90123","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/comments?post=90123"}],"version-history":[{"count":5,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/posts\/90123\/revisions"}],"predecessor-version":[{"id":90130,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/posts\/90123\/revisions\/90130"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/media\/90128"}],"wp:attachment":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/media?parent=90123"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/categories?post=90123"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/tags?post=90123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}