Migrate from Enrich-CRM to HubSpot

Enrich-CRM contacts already exist as HubSpot contacts. We map Enrich-CRM enrichment properties to HubSpot standard properties where names match and to HubSpot custom properties (snake_case) where no standard equivalent exists. Original Enrich-CRM scores preserved as custom number fields. These custom fields are labeled with the __c suffix to follow HubSpot naming conventions.

HubSpot has no native enrichment score field. We migrate score as a custom Number property (e.g., enrichment_score__c) so existing score-based segmentation and reports continue working. Breeze Intelligence will generate its own score post-migration. The custom property can be set to read-only after migration to prevent accidental overwrites by subsequent enrichment runs.

Enrich-CRM fires job change alerts when a contact's employer changes. HubSpot has no native job change detection — we preserve the last job change timestamp as last_job_change_detected__c and recommend rebuilding detection as a HubSpot workflow triggered by company-name or jobtitle field changes.

Enrich-CRM appends firmographic data (employees, revenue, industry, tech stack) to HubSpot company records. We map these to HubSpot standard company properties where names align and to custom properties (e.g., tech_stack__c) where HubSpot has no standard field. All custom fields follow HubSpot's naming conventions and are added to the company object for segmentation and reporting.

Enrich-CRM stores a confidence rating per enriched record. HubSpot has no native equivalent. We preserve this as enrichment_confidence_score__c on contacts for reporting continuity and to flag records that may need re-enrichment under Breeze Intelligence. The confidence score can be used in HubSpot workflows to prioritize outreach based on data reliability.

Tracks when each record was last enriched by Enrich-CRM. Preserved as last_enrichment_date__c so Breeze Intelligence can prioritize re-enrichment of stale records. HubSpot does not store enrichment timestamps natively. You can set up a HubSpot workflow to alert sales reps when a contact's enrichment date exceeds a defined threshold, prompting a refresh.

Records the enrichment provider used (e.g., 'Enrich-CRM'). Preserved as enrichment_source__c for audit trail. After migration, Breeze Intelligence updates this field to 'HubSpot Breeze' on subsequent enrichment runs. This audit trail helps compliance teams track data provenance and verify which enrichment engine populated each attribute over time.

HubSpot has no standard LinkedIn URL field on contacts. We map to linkedin_url__c custom property. HubSpot's native social integration can also surface LinkedIn data via its social cards but does not store the raw URL in a standard field. The custom field is available for segmentation and can be used in email templates.

Enrich-CRM detects technologies used by a company. HubSpot has no native tech stack field. We map to a custom multi-select property (tech_stack__c) that marketing and sales teams can use for segmentation and account-based targeting. This property supports multiple selections per company and can be filtered in HubSpot reports for targeted campaigns.

Enrich-CRM does not manage deal records — those live in HubSpot. We include deals in the migration scope for record continuity and to verify deal associations with enriched contacts remain intact during the enrichment-layer transition. Deal properties such as stage, amount, and owner are preserved and will be accessible in HubSpot after migration.

HubSpot engagement logs already exist in HubSpot. We verify they remain associated with the correct contacts post-migration. Enrich-CRM does not modify engagement records — this is a continuity check, not a data transformation. Any discrepancies in associations are flagged for manual review to ensure reporting accuracy.

Enrich-CRM's overwrite vs. fill-only enrichment behavior has no direct HubSpot equivalent. We configure Breeze Intelligence property mapping rules post-migration to replicate the fill-empty-fields-only behavior that Enrich-CRM customers relied on. This configuration ensures that existing data remains intact while new enrichment data fills only missing fields, preserving your data integrity.