Migrate from Enrich-CRM to Nutshell

Enrich-CRM company records (firmographic data: industry, employee count, revenue, tech stack, and 100+ enrichment datapoints) export from the connected HubSpot portal and map to Nutshell Organization records. The HubSpot Company domain becomes the Organization website field and serves as the dedupe key. All enrichment output fields map to Nutshell custom fields on the Organization object. We create these custom fields during the pre-migration schema phase and preserve the original enrichment source tag for data provenance.

Enrich-CRM contact records (personal data: title, seniority, LinkedIn URL, location, 50 contact datapoints) map to Nutshell Person records. The HubSpot Contact email address is the primary dedupe key in Nutshell. Every enrichment output field becomes a Nutshell custom field on the Person object. We preserve the enrichment source and last-refreshed timestamp as custom properties so the customer can identify which records were enriched by Enrich-CRM versus updated manually in Nutshell.

HubSpot Deals enriched with Enrich-CRM data map to Nutshell Deals. The deal name, amount, stage, close date, and owner migrate directly. Pipeline assignments from HubSpot map to Nutshell pipeline fields. If the customer uses multiple HubSpot pipelines, we map each to a corresponding Nutshell pipeline during schema setup. Deals without an associated Organization or Person in the HubSpot source create orphan Deals in Nutshell that require manual association post-migration.

HubSpot Products used in Deals map to Nutshell Products via the Nutshell Product Importer. Product codes, names, descriptions, and pricing migrate. Nutshell's product management is available from the Pro plan upward, so plan eligibility is confirmed during scoping.

HubSpot email engagement records (sent, received, logged) migrate as Nutshell Activity records of type email. Email subject, body, timestamp, sender, and recipient migrate. The activity is linked to the corresponding Nutshell Person or Organization record via internal ID resolution during migration.

HubSpot call engagement records migrate as Nutshell Activity records with call type. Call duration, disposition, recording URL (if available via HubSpot API), and timestamp transfer. We set the activity owner by resolving the HubSpot owner email against the Nutshell user email.

HubSpot meeting engagements migrate as Nutshell Activity records with meeting type. Meeting title, date, location, attendees (linked to Person records), and description transfer. Attendee resolution uses email matching against migrated Nutshell Person records.

HubSpot Note engagements migrate as Nutshell Activity notes. HubSpot Task engagements migrate as Nutshell Activity tasks with status, priority, due date, and owner preserved. Completed tasks carry their completion timestamp from HubSpot.

Enrich-CRM job-change alerts are signal events, not traditional CRM records. We capture each alert as a dated Activity Note on the associated Nutshell Person record with a standardized label (e.g., 'Job Change Detected: [Old Title] → [New Title] at [New Company]'). The alert date becomes the Activity timestamp. This preserves the buyer-intent signal in the Person's timeline without requiring a custom object in Nutshell.

Custom lead scoring models and contact segments built inside Enrich-CRM are not accessible via public API and cannot be exported programmatically. During scoping, we capture scoring criteria through screen recordings and customer interviews, document the scoring logic in a written specification, and recommend rebuilding it using Nutshell custom fields (on Pro and Enterprise plans) or Nutshell's Power AI plan scoring features. This is a manual configuration step outside the data migration scope and must be budgeted as an admin task.

Automation paths triggered by Enrich-CRM enrichment signals (for example, 'enrichment complete → update CRM field → fire email sequence') are handled by Zapier, Make, or n8n in the source stack. These connections do not migrate to Nutshell. We deliver a written inventory of each automation with its trigger, conditions, actions, and recommended Nutshell automation rule equivalent. The customer's admin rebuilds the automations in Nutshell's native automation tool or re-connects via Zapier, Make, or n8n using Nutshell's documented API.

If a customer used the Enrich-CRM API to attach custom metadata to enrichment results (beyond standard enrichment output fields), we preserve those as JSON blobs stored in Nutshell custom text fields on the Person or Organization object. Nutshell's custom field limits are plan-dependent (Pro and above required for extended custom fields), which we confirm during scoping before mapping any custom enrichment metadata.