Migrate from Enrich-CRM to Twenty CRM

Enrich-CRM's enriched company records (industry, employee count, revenue, tech stack, domain, location) map directly to Twenty CRM's Company object. The HubSpot Company ID or the Enrich-CRM source record ID is preserved in a custom field for cross-reference. Firmographic fields like annual_revenue and employee_count map to their Twenty equivalents; any enrichment-specific fields without a direct Twenty counterpart are stored as custom fields in the Twenty workspace. Company deduplication uses domain as the primary key.

Enrich-CRM enriched contact records (name, title, seniority, LinkedIn URL, email, phone, location) map to Twenty CRM's Person object. The Person-Company relationship is preserved by resolving the enrichment source's company record to the corresponding Twenty Company record before Person import. Title, seniority, and job function map to Twenty's standard person fields; enriched fields without a direct counterpart are added as custom fields. Email is the primary deduplication key.

Enrich-CRM job-change alerts are not traditional CRM records but time-stamped events with a contact identifier and a new company signal. We capture these as Twenty Activity records with type = 'note' or a custom activity type, storing the alert content in the activity body and the detected new company name in a custom field. The activity is linked to the corresponding Person record in Twenty. If no Person record exists for the contact, the activity is held in a staging queue pending Person creation.

Since Enrich-CRM enriches records already in HubSpot, the source records for migration are HubSpot Companies and Contacts, not Enrich-CRM records directly. We export enriched Company records from HubSpot, preserving all Enrich-CRM-applied enrichment fields as HubSpot custom properties, then map them to Twenty Company. The migration reads HubSpot's API or CSV export with Enrich-CRM field values included.

Enriched Contact records are exported from HubSpot with Enrich-CRM field values intact. We map HubSpot contacts to Twenty Person records, resolve the company association by matching HubSpot's associated company domain against the Twenty Company domain key, and import in dependency order (Company first, then Person). Any enrichment fields that do not map to standard Twenty Person fields are added as custom workspace fields.

Custom lead scoring models and segmentation logic built inside Enrich-CRM are not accessible via public API. During scoping we capture the scoring criteria through screen recordings, documentation requests, and customer interviews. We deliver a written scoring specification that maps Enrich-CRM score ranges to Twenty CRM's custom scoring fields or a third-party scoring tool integrated via API. This step is manual and must be budgeted as a post-migration configuration task; it is not part of the automated data migration scope.

If a customer used Enrich-CRM's API to attach custom metadata to enrichment results, we preserve those as JSON blobs or custom fields in Twenty CRM depending on the workspace's field type flexibility. We document the field name, data type, and sample values during scoping and create the corresponding custom fields in Twenty's workspace schema before data import begins.

Automation paths triggered by Enrich-CRM signals (for example, 'enrichment complete → update CRM field → fire email sequence') do not migrate as code. We audit the connected Zapier, Make, or n8n workflows during scoping and deliver a written inventory listing each automation's trigger, steps, and destination equivalent in Twenty's automation tools or the customer's chosen workflow platform. The customer rebuilds these post-migration.

Credit consumption data is a billing artifact specific to Enrich-CRM's credit model and has no equivalent in Twenty CRM. We do not migrate credit history. We flag the customer's historical credit burn-rate during scoping so they can estimate the credit package needed if they choose to use Twenty's integrated enrichment tools or a third-party enrichment provider post-migration.

The native Enrich-CRM HubSpot Marketplace app configuration (automatic field mapping rules, workflow triggers, bulk enrichment settings) is Enrich-CRM-specific and does not transfer to Twenty CRM. We document the integration settings during scoping and deliver a written integration plan for reconnecting the customer's chosen enrichment provider to Twenty via its REST API.