Migrate from Enrich-CRM to Freshsales

Enrich-CRM contact enrichment data (title, seniority, LinkedIn URL, location, contact datapoints) maps to Freshsales Contact fields. The HubSpot contact record that received Enrich-CRM enrichment is the actual migration source; we export from HubSpot with Enrich-CRM field values included, then map to Freshsales Contact fields by field name. If Enrich-CRM was used via API outside HubSpot, we receive the enrichment JSON and map individual fields (first_name, last_name, title, linkedin_url, phone, location) to Freshsales Contact properties.

Enrich-CRM company firmographic data (industry, employee count, revenue, tech stack, funding data) maps to Freshsales Account fields. We map Enrich-CRM's 100+ company datapoints to Freshsales Account standard and custom fields, using Account Name and Website as the dedupe key during import. Tech stack detection data from Enrich-CRM maps to a Freshsales custom text field or multi-select picklist.

Enrich-CRM job-change alerts are signal events, not traditional CRM records. We capture them as Activity Notes on the Contact timeline with a standardized timestamp and signal type field, or as custom date fields (last_job_change_date__c) on the Contact record. The signal type is preserved so sales reps can see the context of when a contact changed roles. If the alert included the new employer, we update the Contact's associated Account accordingly.

HubSpot Owners who enriched and managed records map to Freshsales User accounts by email address match. We resolve owners by email during migration so that Contact and Account ownership reflects the original enrichment owner. Any HubSpot Owner without a matching Freshsales User is flagged for manual provisioning before record import completes.

Custom scoring models and contact segments built inside Enrich-CRM are not accessible via public API. During scoping we document the scoring criteria from screen captures and customer interviews, then produce a written Freddy AI scoring criteria guide that maps each Enrich-CRM scoring signal to a Freddy AI rule or weight. Rebuilding in Freshsales Freddy AI is a configuration task the customer's admin performs post-migration; we do not program the rules ourselves.

Enrichment credit consumption is a billing artifact, not user data. Credits do not migrate. We document the customer's monthly credit burn rate during scoping so they can estimate what Freshsales tier or third-party enrichment provider they need post-migration. If the customer moves to Freshsales Enterprise, they may use Freshsales' own auto-profile enrichment rather than a separate enrichment tool.

Automation paths triggered by Enrich-CRM enrichment signals (e.g., enrichment complete updates a HubSpot property and fires a Zapier automation) do not migrate as workflow code. We document every active Zapier, Make, or n8n path triggered by Enrich-CRM and produce a written recommendation for rebuilding equivalent logic in Freshsales Workflow Rules. If enrichment events were the trigger, the automation must be redesigned around Freshsales native events (Contact created, Deal stage changed, etc.).

If a customer used Enrich-CRM's API to attach custom metadata to enrichment results, we preserve those as Freshsales custom fields on the Contact or Account object. We assess the data type of each custom enrichment property during scoping and create matching Freshsales custom fields before import. JSON blob data is parsed and split into individual fields where possible; deeply nested JSON is preserved as a long-text field for admin reference.