Migrate from Enrich-CRM to Salesforce Sales Cloud

Enrich-CRM appends firmographic datapoints (industry, employee count, revenue range, tech stack, funding stage) to Company records in the connected HubSpot instance. We extract those HubSpot Company records and map them to Salesforce Account. Every Enrich-CRM field (company_size, annual_revenue, industry, technology_stack, etc.) is created as a typed Salesforce custom field on Account before migration. The Company domain becomes the Account Website field and is used as the dedupe key.

Enrich-CRM appends contact datapoints (title, seniority level, LinkedIn URL, location, phone validation status) to Contact records in HubSpot. We extract those HubSpot Contacts and map them to Salesforce Contact. All Enrich-CRM contact fields (contact_title, seniority, linkedin_url, location, phone_status) migrate to custom Contact fields. Each Contact is linked to its parent Account via the AccountId lookup resolved from the Company-to-Account mapping.

Each enriched record carries a last-enrichment timestamp indicating when the data was last refreshed. We preserve this as a custom date field on Account and Contact (Last_Enrichment_Date__c) so that reps can see which records are stale and may need re-enrichment in Salesforce. This field also powers a Salesforce Report or List View that flags records not enriched within the last 90 days.

Enrich-CRM detects job transitions and generates alerts. These are not CRM-native records; we capture each alert as a Salesforce Task with a Note body describing the change (old company, new company, change date) linked to the Contact. We also create a custom date field Job_Change_Date__c on Contact so that filters and reports can surface contacts with recent job changes. The activity timeline in Salesforce shows the job-change history without requiring reps to open a separate enrichment tool.

Enrich-CRM scoring logic (point values assigned to properties like company size, seniority, tech stack, engagement signals) is not accessible via API. During scoping we capture the scoring model through screen recordings and customer interviews, document the point-weight matrix, and deliver a written scoring rebuild plan for Salesforce native Lead Scoring or a scoring middleware (e.g., LeanData, Clearbit). The customer or their Salesforce admin implements the scoring logic post-migration. We do not write the scoring logic as code during migration.

Enrich-CRM segments (e.g., 'Enterprise Prospects', 'Mid-Market Active', 'SMB Churned') do not export via API. We document the segment membership criteria during scoping, map each segment to either a Salesforce Campaign with the relevant Contacts added as CampaignMembers or a custom multi-select picklist on Contact. The customer's admin assigns contacts to the appropriate segment in Salesforce after migration using a list view or Data Loader.

Enrich-CRM enriches data through its native HubSpot Marketplace app, which writes enriched fields directly into HubSpot Company and Contact records. We extract the enriched records from HubSpot via the HubSpot API before migrating them to Salesforce. The extraction point is HubSpot, not Enrich-CRM directly, because Enrich-CRM does not maintain an independent record store. We use the HubSpot CRM Lists API to export all enriched Companies and Contacts with their custom enrichment properties included.

Automation paths triggered by Enrich-CRM signals (e.g., 'enrichment complete → update HubSpot contact field → fire Zapier email sequence') are external to both Enrich-CRM and Salesforce. We document each Zapier/Make/n8n workflow during scoping with its trigger, conditions, and actions, and deliver a written Flow recommendation for each. The customer rebuilds these in Salesforce Flow post-migration. We do not write Zapier/Make/n8n export/import configs as part of the migration scope.

If the customer used Enrich-CRM's API to attach custom metadata to enrichment results (e.g., a sales-rep tag, internal account tier, or campaign source flag), we preserve that as either typed custom fields on Account/Contact or as a long-text JSON field (Enrichment_Metadata__c) depending on the target CRM's schema flexibility. During scoping we audit all API-attached custom properties and agree on the target field strategy with the customer.

HubSpot Owners referenced on enriched Company and Contact records are resolved by email match against the Salesforce destination org's User table. Any HubSpot Owner without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references on Account and Contact must be resolved before migration to avoid orphaned records.

Credit consumption data is a billing artifact in Enrich-CRM and does not migrate to Salesforce. During scoping we extract the credit burn-rate report from Enrich-CRM (accessible via the CRM Connector dashboard) and use it to estimate what credit package the customer needs in their chosen Salesforce enrichment tool (e.g., Apollo, ZoomInfo, Cognism, Clearbit). We deliver this as a written credit estimation document, not as migrated Salesforce records.

If the connected HubSpot instance contains Deals linked to enriched Contacts, we extract the Deal records alongside the Contact records. HubSpot Deal maps to Salesforce Opportunity with pipeline and stage mapped to Salesforce Sales Process and Record Type. Deal custom properties (e.g., closed-won reason, product line) migrate as custom Opportunity fields. This object mapping only applies if the customer is also migrating their HubSpot CRM data, which is a separate migration scope from the Enrich-CRM overlay extraction.