{"id":89914,"date":"2025-11-12T08:22:03","date_gmt":"2025-11-12T16:22:03","guid":{"rendered":"https:\/\/rightwave.com\/rwi\/?p=89914"},"modified":"2025-11-12T08:42:30","modified_gmt":"2025-11-12T16:42:30","slug":"one-record-or-two-the-great-hubspot-dilemma-when-contacts-change-jobs","status":"publish","type":"post","link":"https:\/\/rightwave.com\/rwi\/one-record-or-two-the-great-hubspot-dilemma-when-contacts-change-jobs","title":{"rendered":"One Record or Two? The Great HubSpot Dilemma When Contacts Change Jobs"},"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 managed contact data in HubSpot, you\u2019ve probably run into this question:<\/p>\n

\n

\u201cWhen a contact changes companies, should I keep one record and update it \u2014 or create a new record for their new role?\u201d<\/p>\n<\/blockquote>\n

It sounds like a small decision, but the impact runs deep \u2014 influencing your reporting accuracy, attribution, sales context, and even AI-driven workflows.<\/p>\n

Recently, we came across an engaging industry conversation where several Marketing Operations professionals shared how they handle this exact dilemma. Their insights reveal just how nuanced the issue really is.<\/p>\n

Option 1: One Record \u2014 When Context Matters More Than Company<\/h3>\n

Many operations teams prefer to maintain a single contact record<\/strong> even when someone moves to a new company.<\/p>\n

Here\u2019s the logic behind that choice:<\/p>\n

    \n
  • \n

    Continuous relationship tracking:<\/strong> Keeping one record lets you view the person\u2019s full journey \u2014 all past engagements, communications, and preferences \u2014 in one place.<\/p>\n<\/li>\n

  • \n

    Clean user experience:<\/strong> When HubSpot is your primary CRM, duplicate records can confuse sales teams who rely on quick searches.<\/p>\n<\/li>\n

  • \n

    Contextual relevance:<\/strong> If someone has interacted positively with your brand before, that context can be highly valuable when they reappear in a new role.<\/p>\n<\/li>\n<\/ul>\n

    Some marketing and sales teams also highlight a practical benefit \u2014 if your product is sold to individuals with transferable licenses, credentials, or personal influence (like consultants or advisors), one record allows you to \u201cpick up where you left off.\u201d<\/p>\n

    However, this approach does require clear operational discipline. Fields such as company name, title, and email address must be updated consistently. Some teams store the previous email under \u201cAlternate Email\u201d and log the company change as a note or association label.<\/p>\n

    Option 2: Two Records \u2014 When Accuracy and Attribution Come First<\/h3>\n

    On the other hand, there\u2019s a strong case for maintaining two separate records<\/strong> \u2014 one for each employment period.<\/p>\n

    This approach emphasizes data integrity and analytical accuracy<\/strong>:<\/p>\n

      \n
    • \n

      Each record reflects a specific business context<\/strong> \u2014 keeping engagement history and lifecycle stages tied to the right company.<\/p>\n<\/li>\n

    • \n

      Attribution clarity:<\/strong> Campaign performance, MQLs, and pipeline attribution stay aligned with the correct employer.<\/p>\n<\/li>\n

    • \n

      Cleaner automation:<\/strong> AI and workflow tools often perform better when they\u2019re not dealing with overlapping or outdated company associations.<\/p>\n<\/li>\n<\/ul>\n

      In short: the \u201ctwo-record\u201d model is about creating a historical truth<\/em> \u2014 one that mirrors the relationship between company and contact at the time of engagement.<\/p>\n

      The Operational Challenge: Updating Is Easy, Operationalizing Is Hard<\/h3>\n

      Whether you go with one record or two, the real challenge isn\u2019t data entry \u2014 it\u2019s orchestrating change across systems and teams<\/strong>.<\/p>\n

      Marketing Ops leaders often struggle with:<\/p>\n

        \n
      • \n

        Multiple enrichment sources (ZoomInfo, LinkedIn, UserGems, Clay) providing overlapping updates.<\/p>\n<\/li>\n

      • \n

        Determining which system\u2019s data \u201cwins\u201d when job change information conflicts.<\/p>\n<\/li>\n

      • \n

        Notifying Sales when a decision-maker in an open opportunity leaves.<\/p>\n<\/li>\n

      • \n

        Ensuring marketing doesn\u2019t continue nurturing contacts tied to former employers.<\/p>\n<\/li>\n<\/ul>\n

        Some teams automate this process with deduplication and merge workflows, while others rely on enrichment tools or manual reviews. The problem? Even with the best automation, clarity on ownership, logic, and data flow is essential.<\/p>\n

        RightWave\u2019s Perspective: Let Your Data Governance Drive the Decision<\/h3>\n

        At RightWave<\/strong>, we\u2019ve seen both models work well \u2014 when implemented within a governed data framework<\/strong>.<\/p>\n

        The key is to align the approach with your GTM structure and data maturity:<\/p>\n

        \n
        \n\n\n\n\n\n\n\n\n
        Scenario<\/th>\nRecommended Approach<\/th>\nWhy It Works<\/th>\n<\/tr>\n<\/thead>\n
        HubSpot used as both CRM and MAP<\/td>\nSingle Record<\/strong><\/td>\nReduces confusion for sales and service users who depend on one source of truth.<\/td>\n<\/tr>\n
        HubSpot integrated with external enrichment tools or data warehouses<\/td>\nDual Records<\/strong><\/td>\nMaintains integrity for AI\/ML models, reporting, and historical attribution.<\/td>\n<\/tr>\n
        Early-stage organizations with limited automation resources<\/td>\nSingle Record<\/strong><\/td>\nEasier to manage manually, less technical overhead.<\/td>\n<\/tr>\n
        Mature data governance programs with strong deduplication workflows<\/td>\nDual Records<\/strong><\/td>\nEnables precise historical tracking without human confusion.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

        Ultimately, your Data Quality Governance (DQG)<\/strong> processes \u2014 not your CRM structure \u2014 should drive the decision. A clear taxonomy for contacts, companies, and associations ensures that whichever path you choose, your data remains actionable, accurate, and aligned.<\/p>\n

        The Bigger Picture<\/h3>\n

        Job changes are one of the most valuable buying signals in B2B. They can indicate both risk (customer churn) and opportunity (a champion moving to a new company).<\/p>\n

        What matters most isn\u2019t whether you maintain one record or two \u2014 it\u2019s whether your systems, processes, and people can act on that change intelligently.<\/strong><\/p>\n

        At RightWave, we help organizations design HubSpot, Marketo, and Salesforce environments where these nuances are automated, auditable, and aligned with business goals. Because in modern Marketing Operations, data quality is not just hygiene \u2014 it\u2019s strategy.<\/strong><\/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 managed contact data in HubSpot, you\u2019ve probably run into this question: \u201cWhen a contact changes companies, should I keep one record and update it \u2014 or create a new record for their new role?\u201d It sounds like a small decision, but the impact runs deep \u2014 influencing your reporting accuracy, attribution, sales…<\/p>\n","protected":false},"author":45,"featured_media":89926,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-89914","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\/89914","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=89914"}],"version-history":[{"count":10,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/posts\/89914\/revisions"}],"predecessor-version":[{"id":89924,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/posts\/89914\/revisions\/89924"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/media\/89926"}],"wp:attachment":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/media?parent=89914"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/categories?post=89914"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/tags?post=89914"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}