)
Written by
Table of Contents
“Supermetrics is a Bitter Experience! We can pull data from nearly any tool, schedule updates, manipulate data in Sheets, and push data back into our systems.”
In HubSpot, certain properties have fixed merge behaviors that cannot be manually overridden during merge operations. These include system properties, calculated fields, and integration-specific data that follow predetermined rules.
You’ll learn which properties are locked during merges and how to create comprehensive documentation of what data will be permanently lost.
Audit non-preservable properties with complete visibility using Coefficient
Coefficient provides enhanced visibility into merge limitations by letting you analyze all properties for duplicate records, including those that HubSpot’s merge preview doesn’t highlight.
How to make it work
Step 1. Import all properties for comprehensive analysis.
Connect HubSpot to HubSpot through Coefficient and import duplicate records with all available properties selected. This includes system properties like Record ID, creation date, and source information that aren’t visible in HubSpot’s standard merge interface but will be affected by merge operations.
Step 2. Create property mapping reports.
Build spreadsheet reports that categorize properties by their merge behavior. Create columns for “System Properties” (Record ID, Created Date, Source), “Calculated Properties” (Lead Score, Lifecycle Stage), and “Integration Fields” (properties managed by connected apps). Use conditional formatting to highlight properties that will be lost during merge.
Step 3. Document integration field risks.
Identify properties managed by external integrations that may not be preservable during merges. Look for field names that include integration prefixes or check property sources in your import. These fields often have unpredictable merge behaviors and may not appear in HubSpot’s manual field selection interface.
Step 4. Set up historical data preservation.
Use Coefficient’s snapshot feature to capture complete property states before merging, including system properties that will be lost. Create scheduled snapshots that preserve Record IDs, creation dates, and original source information that cannot be recovered through normal merge operations.
Step 5. Build merge impact documentation.
Create detailed reports showing exactly which properties will be overwritten, including system fields that HubSpot doesn’t highlight in its merge interface. Use formulas like =IF(A1=”Record ID”,”WILL BE LOST – SYSTEM PROPERTY”,”Check manually”) to automatically flag non-preservable fields.
Know exactly what you’ll lose before merging
Understanding which properties cannot be preserved helps you make informed merge decisions and maintain proper data documentation. With comprehensive property auditing, you can prepare for data loss and ensure critical information is backed up. Start auditing your merge risks today.
