<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Datum Operations Blog</title>
    <link>https://www.datumoperations.com/blog</link>
    <description>Plain, practical CRM fixes for teams without a full-time admin. Duplicates, lifecycle stages, workflows and inherited setups, starting with HubSpot.</description>
    <language>en-us</language>
    <pubDate>Mon, 26 Oct 2026 18:50:24 GMT</pubDate>
    <dc:date>2026-10-26T18:50:24Z</dc:date>
    <dc:language>en-us</dc:language>
    <item>
      <title>HubSpot Lifecycle Stages Stuck or Wrong? Find What's Setting Them.</title>
      <link>https://www.datumoperations.com/blog/hubspot-lifecycle-stages-stuck-or-wrong</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/hubspot-lifecycle-stages-stuck-or-wrong" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/hubspot-lifecycle-stages-stuck-or-wrong-featured-v3-1.png" alt="Diagram of HubSpot lifecycle stages from subscriber to customer moving forward only, with a crossed-out return arrow, labeled Stages only move forward" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;When HubSpot tools set lifecycle stage, it only moves forward. Imports, forms, the API, integrations and workflows can't set an earlier stage unless the value is cleared first. That's why contacts get stuck at Opportunity after a lost deal, and why two automations writing the same field produce a funnel report nobody believes. The fix is in three parts: write down what each stage means, find everything that sets the field, and give each move one owner.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/hubspot-lifecycle-stages-stuck-or-wrong" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/hubspot-lifecycle-stages-stuck-or-wrong-featured-v3-1.png" alt="Diagram of HubSpot lifecycle stages from subscriber to customer moving forward only, with a crossed-out return arrow, labeled Stages only move forward" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;When HubSpot tools set lifecycle stage, it only moves forward. Imports, forms, the API, integrations and workflows can't set an earlier stage unless the value is cleared first. That's why contacts get stuck at Opportunity after a lost deal, and why two automations writing the same field produce a funnel report nobody believes. The fix is in three parts: write down what each stage means, find everything that sets the field, and give each move one owner.&lt;/p&gt;  
&lt;img src="https://track-na2.hubspot.com/__ptq.gif?a=246883608&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.datumoperations.com%2Fblog%2Fhubspot-lifecycle-stages-stuck-or-wrong&amp;amp;bu=https%253A%252F%252Fwww.datumoperations.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>CRM Data Quality</category>
      <category>CRM Fixes</category>
      <category>Lifecycle Stages</category>
      <pubDate>Thu, 22 Oct 2026 11:39:48 GMT</pubDate>
      <guid>https://www.datumoperations.com/blog/hubspot-lifecycle-stages-stuck-or-wrong</guid>
      <dc:date>2026-10-22T11:39:48Z</dc:date>
      <dc:creator>David Deutsch</dc:creator>
    </item>
    <item>
      <title>Why HubSpot Creates Duplicate Contacts (and How to Stop It)</title>
      <link>https://www.datumoperations.com/blog/hubspot-duplicate-contacts-causes</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/hubspot-duplicate-contacts-causes" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/hubspot-duplicate-contacts-causes-featured-v3.png" alt="Two overlapping contact cards with similar example email addresses merging into one record, labeled Two records, one person" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;HubSpot deduplicates contacts by email address and companies by domain name. Duplicates get through when something creates a record without giving HubSpot an email or a domain to match on, or goes around the check entirely. Common sources are imports without an email column, companies created through the API or a sync app, people with two email addresses, and records typed in by hand. Find which one is creating yours, fix that first, then merge. Merges can't be undone, so export before you start.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/hubspot-duplicate-contacts-causes" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/hubspot-duplicate-contacts-causes-featured-v3.png" alt="Two overlapping contact cards with similar example email addresses merging into one record, labeled Two records, one person" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;HubSpot deduplicates contacts by email address and companies by domain name. Duplicates get through when something creates a record without giving HubSpot an email or a domain to match on, or goes around the check entirely. Common sources are imports without an email column, companies created through the API or a sync app, people with two email addresses, and records typed in by hand. Find which one is creating yours, fix that first, then merge. Merges can't be undone, so export before you start.&lt;/p&gt;  
&lt;img src="https://track-na2.hubspot.com/__ptq.gif?a=246883608&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.datumoperations.com%2Fblog%2Fhubspot-duplicate-contacts-causes&amp;amp;bu=https%253A%252F%252Fwww.datumoperations.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>CRM Data Quality</category>
      <category>CRM Fixes</category>
      <pubDate>Thu, 22 Oct 2026 11:37:04 GMT</pubDate>
      <guid>https://www.datumoperations.com/blog/hubspot-duplicate-contacts-causes</guid>
      <dc:date>2026-10-22T11:37:04Z</dc:date>
      <dc:creator>David Deutsch</dc:creator>
    </item>
    <item>
      <title>HubSpot Workflow Re-enrollment: Why Contacts Don't Come Back (or Come Back Too Often)</title>
      <link>https://www.datumoperations.com/blog/hubspot-workflow-re-enrollment</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/hubspot-workflow-re-enrollment" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/hubspot-workflow-re-enrollment-featured-v3.png" alt="Workflow diagram from trigger to actions to exit with a dashed loop back for re-enrollment, labeled When contacts come back" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A HubSpot workflow enrolls each record once, the first time it meets the trigger. If you want a returning lead to go through again, you have to turn re-enrollment on and pick which triggers count. If the opposite is happening and people keep getting the same emails, re-enrollment is on and one of those triggers fires more often than you think. Both problems live in the same place: the workflow's enrollment trigger settings. Its enrollment history shows you which one it is.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/hubspot-workflow-re-enrollment" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/hubspot-workflow-re-enrollment-featured-v3.png" alt="Workflow diagram from trigger to actions to exit with a dashed loop back for re-enrollment, labeled When contacts come back" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A HubSpot workflow enrolls each record once, the first time it meets the trigger. If you want a returning lead to go through again, you have to turn re-enrollment on and pick which triggers count. If the opposite is happening and people keep getting the same emails, re-enrollment is on and one of those triggers fires more often than you think. Both problems live in the same place: the workflow's enrollment trigger settings. Its enrollment history shows you which one it is.&lt;/p&gt;  
&lt;img src="https://track-na2.hubspot.com/__ptq.gif?a=246883608&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.datumoperations.com%2Fblog%2Fhubspot-workflow-re-enrollment&amp;amp;bu=https%253A%252F%252Fwww.datumoperations.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>CRM Fixes</category>
      <category>Workflows and Automation</category>
      <pubDate>Thu, 22 Oct 2026 11:32:24 GMT</pubDate>
      <guid>https://www.datumoperations.com/blog/hubspot-workflow-re-enrollment</guid>
      <dc:date>2026-10-22T11:32:24Z</dc:date>
      <dc:creator>David Deutsch</dc:creator>
    </item>
    <item>
      <title>Inherited a Messy HubSpot Portal? Where to Start</title>
      <link>https://www.datumoperations.com/blog/inherited-messy-hubspot-portal-where-to-start</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/inherited-messy-hubspot-portal-where-to-start" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/inherited-messy-hubspot-portal-where-to-start-featured-v3.png" alt="Numbered triage list of who owns what, what's running, what's broken and then clean, with start here marked on step one, labeled Where to start" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Start read-only. Export your data, then check four things in this order: who's on a paid seat, which records have no owner (or an owner who's left), which workflows and sequences still run, and where your duplicates come from. Fix what's silently breaking things first. Only then touch properties, lifecycle stages and reports.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.datumoperations.com/blog/inherited-messy-hubspot-portal-where-to-start" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.datumoperations.com/hubfs/inherited-messy-hubspot-portal-where-to-start-featured-v3.png" alt="Numbered triage list of who owns what, what's running, what's broken and then clean, with start here marked on step one, labeled Where to start" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Start read-only. Export your data, then check four things in this order: who's on a paid seat, which records have no owner (or an owner who's left), which workflows and sequences still run, and where your duplicates come from. Fix what's silently breaking things first. Only then touch properties, lifecycle stages and reports.&lt;/p&gt;  
&lt;img src="https://track-na2.hubspot.com/__ptq.gif?a=246883608&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.datumoperations.com%2Fblog%2Finherited-messy-hubspot-portal-where-to-start&amp;amp;bu=https%253A%252F%252Fwww.datumoperations.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Mon, 19 Oct 2026 16:05:27 GMT</pubDate>
      <guid>https://www.datumoperations.com/blog/inherited-messy-hubspot-portal-where-to-start</guid>
      <dc:date>2026-10-19T16:05:27Z</dc:date>
      <dc:creator>David Deutsch</dc:creator>
    </item>
  </channel>
</rss>
