<?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/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Data Integrity in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171764#M12999</link>
    <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/111325"&gt;@karstenkoehler&lt;/a&gt;.&amp;nbsp;Was hoping for a magic bullet but didn't think it existed. I might at the Ideas. We did have the exact disussion you mentioned, looking at when updated...but as you said it gets complicated quickly.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 01 Jul 2025 15:45:58 GMT</pubDate>
    <dc:creator>Longhorn</dc:creator>
    <dc:date>2025-07-01T15:45:58Z</dc:date>
    <item>
      <title>Data Integrity</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171320#M12980</link>
      <description>&lt;P&gt;Wondering what peoples best practices for importing new data but also keeping the "good" data protected when it comes to contact info.&amp;nbsp; Example: Contact info has been collected via forms and other tools. Reps work through it and constantly updating with when they get a better number, email, etc. Then we come back from a show and thinking that some of this data is more accurate than other don't check don't overwrite. Some is better but other is not.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to "mark verified data" or some how keep that from being updated but unverified data overwrite? Wondering what others have done around these types of things.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We use Enterprise.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 18:29:10 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171320#M12980</guid>
      <dc:creator>Longhorn</dc:creator>
      <dc:date>2025-06-30T18:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: Data Integrity</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171322#M12981</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/928675"&gt;@Longhorn&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think this will always be a trade-off and there can't possibly be a perfect solution that scales well. Unless you want to verify every single field on every single record, you'll have to make decisions that could mean that correct data are overwritten with incorrect ones.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HubSpot does not have any features to mark field values as verified or lock them at this point. (This would however be a great feature to have which you could request in the HubSpot Ideas section of the community.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The best solution for now and compromise, without overcomplicating things, is, I think, is to check "Don't overwrite" during the import.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you'd like to complicate things, you could build a list of contacts in HubSpot where you're not confident the information is correct, export the record IDs, and then break your import in two: Overwrite the bad ones, don't overwrite the good ones. This however requires coming up with a logic as to who is bad and who is good. One option could be filtering by create date, assuming that old records are potentially out of date. Records that have been created or modified very recently would be assumed correct.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 18:36:07 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171322#M12981</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2025-06-30T18:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Data Integrity</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171764#M12999</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/111325"&gt;@karstenkoehler&lt;/a&gt;.&amp;nbsp;Was hoping for a magic bullet but didn't think it existed. I might at the Ideas. We did have the exact disussion you mentioned, looking at when updated...but as you said it gets complicated quickly.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 15:45:58 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Data-Integrity/m-p/1171764#M12999</guid>
      <dc:creator>Longhorn</dc:creator>
      <dc:date>2025-07-01T15:45:58Z</dc:date>
    </item>
  </channel>
</rss>

