)
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.”
During HubSpot merges, custom field data follows the same problematic precedence rules as standard properties. When the primary record has blank custom fields, these blanks will overwrite populated custom field values from the secondary record, resulting in permanent data loss.
You’ll learn how to protect custom field data through comprehensive auditing, specialized backup workflows, and recovery processes designed specifically for custom properties.
Protect custom field data with comprehensive auditing using Coefficient
Coefficient provides specialized protection for custom fields during merges through systematic backup and validation processes that HubSpot cannot provide natively.
How to make it work
Step 1. Audit all custom properties for merge risks.
Import all custom properties for duplicate records from HubSpot to HubSpot to identify which fields contain valuable data that could be lost. Create a custom field inventory using formulas like =IF(LEFT(A1,7)=”custom_”,”Custom Field: “&A1,”Standard Field”) to categorize your properties. Build detailed reports showing custom field completeness across duplicate pairs.
Step 2. Set up custom field backup automation.
Use Coefficient’s snapshot feature to capture complete custom field states before merges. Configure snapshots to specifically focus on your custom properties by filtering your imports to include only custom fields. This creates specialized recovery points for custom field data that HubSpot doesn’t preserve in its activity history.
Step 3. Identify integration-managed custom fields.
Create analysis to identify custom fields managed by external integrations that may not be preservable during merges. Look for field naming patterns that indicate integration ownership (like “salesforce_” or “marketo_” prefixes). Build reports showing potential data loss from integration-specific custom properties that might not appear in HubSpot’s merge interface.
Step 4. Build custom field merge validation.
Create spreadsheet logic that specifically flags merges where valuable custom field data would be overwritten with blanks. Use formulas like =COUNTIFS(custom_fields_range,”<>“,primary_record_range,””) to count custom fields that would be lost. Set up alerts when custom field data loss exceeds your acceptable threshold.
Step 5. Implement custom field recovery workflows.
If merges result in custom field data loss, use pre-merge snapshots to identify lost custom field values and restore them. Create comparison analysis between your custom field snapshots and current data, then use Coefficient’s UPDATE export functionality to restore only the custom fields that were incorrectly overwritten, preserving other merge benefits.
Keep your custom data safe during merges
Custom fields often contain your most valuable business-specific data, making their protection during merges critical. With specialized custom field auditing and recovery workflows, you can ensure these important properties survive merge operations intact. Start protecting your custom field data today.
