Migrate from crmConnect to Nutshell

crmConnect Contact records map directly to Nutshell People. Standard fields (name, email, phone, address) transfer without transformation. Custom contact properties in crmConnect require field-by-field discovery during export and custom field creation in Nutshell before import. We preserve any contact tag associations as Nutshell tag records and apply them during the People import phase. Owner email is used as the match key for Nutshell user assignment.

crmConnect Company records map to Nutshell Accounts. The Company domain and industry fields map to Nutshell Account fields. We resolve the Account before People import so that the People-Account association is satisfied at the moment of insert. If crmConnect contact records do not have a Company link, we create a placeholder Account named after the contact for continuity.

crmConnect pipeline definitions (stage names, transition rules) transfer as Nutshell Pipeline definitions. crmConnect Standard limits to 1 pipeline with up to 5 opportunities; Nutshell supports unlimited pipelines at all paid tiers. We create the pipeline structure in Nutshell before Opportunity import so that stage assignments resolve correctly during migration.

crmConnect Opportunities map to Nutshell Deals. Deal amount, stage assignment, expected close date, and owner transfer directly. We resolve the parent People and Account references at migration time. Closed-won and closed-lost outcomes preserve their source status in a custom field for reporting continuity.

Contact tags in crmConnect export as tag-to-contact mappings across multiple CSV files. We deduplicate across files, build a unified tag set, and apply tag associations during People import. Segments (list-based groupings) export as Nutshell tag records with the segment name prepended for identification.

crmConnect custom contact and opportunity properties are discovered during the export phase by analyzing field headers across all CSV files. We deliver a custom field definition list with field name, type (text, number, date, picklist), and source values. The customer's Nutshell admin creates these custom fields before the import phase; we map source values to Nutshell custom field values during import.

crmConnect calendar records with event times, attendees, and linked contact associations map to Nutshell Activities. Meeting and task events preserve their original timestamp for timeline continuity. If the calendar export includes attendee email lists, we link the Activity to the corresponding Nutshell People records by email match.

crmConnect automations use a drag-and-drop builder with no documented export format. We capture automation screenshots, trigger definitions, and action sequences from the UI and deliver a written inventory with recommended Nutshell Workflow equivalents. The customer's admin rebuilds automations in Nutshell's native workflow tool post-migration. This is document-only scope, not code migration.

crmConnect membership portals and course enrollments are treated as separate record types. We export membership status, enrollment dates, and student-contact associations as structured Note records in Nutshell linked to the corresponding People record. For teams requiring a full custom object, we document the schema for the admin to create a Nutshell custom object and remap.

crmConnect email campaign templates and SMS sequence definitions export as metadata and text. We preserve template structure, contact association lists, and send history as Nutshell Campaign records (Pro tier) and Note records. Automation sequences tied to sends are documented separately for rebuild in Nutshell's workflow or an external email marketing tool. Native SMS capability requires an AppConnect add-on in Nutshell.