Migrate from X2CRM to Nutshell

X2CRM Accounts map directly to Nutshell Companies. The account name becomes the Company name, industry classification maps to Nutshell's Industry dropdown, and lifetime value and employee count become Company-level custom fields. X2CRM's account-level tags migrate to Company-level tags in Nutshell. Accounts must be imported first because Contact records in X2CRM carry a foreign key reference to the associated account; this lookup must be resolved before Contact insert to avoid orphaned relationships.

X2CRM Contacts with a status indicating a qualified or active relationship (customer, sales-ready) map to Nutshell People and get linked to the corresponding Company record via the X2CRM account relationship. Contacts without an associated account or marked as early-stage leads map to Nutshell Leads. Any lead status or lifecycle indicator from X2CRM's contact record is preserved as a custom field (original_status__c) for audit and segmentation in Nutshell.

X2CRM Deals map to Nutshell Pipeline entries with the deal name as the Opportunity name, deal value as the Amount, stage mapping to a Nutshell Pipeline stage, and the probability percentage preserved as a custom field (original_probability__c). Deal owner maps to the Nutshell User by email resolution. X2CRM's deal-level notes and activity logs attached to the Deal record are linked as People activity entries under the associated Contact or Lead after parent-record lookup.

X2CRM custom fields vary by module and installation. We inspect the X2CRM field schema via API discovery during scoping, then map each custom field to a type-matched Nutshell custom field: Text fields map to Nutshell's Text type (225 character limit), long text to Long Text, currency values to Currency, dates to Date, and multi-value text fields to Multi-Select Picklist. Custom fields must be created in Nutshell before migration; we include field creation instructions in the pre-migration setup guide and validate the destination schema against the discovered X2CRM schema.

X2CRM Products (with SKU, price, and description) map to Nutshell's Product catalog. Product pricing, unit of measure, and active/inactive status migrate directly. Product associations to Deals are preserved by linking the Nutshell Product to the migrated Pipeline entry via the deal's line-item data, which we reconstruct during the Deal mapping phase.

X2CRM Activities (calls, meetings, tasks) carry a related record type and reference (contact, account, or deal). We map call engagements to Nutshell People activities with call disposition and duration stored in custom fields; meeting engagements map similarly with location and attendee information. Task engagements map as open or completed activities linked to the corresponding People or Company record. All timestamps are preserved so the Nutshell activity timeline reflects the original chronological order from X2CRM.

X2CRM Notes attached to Contacts or Accounts migrate as People Notes or Company Notes in Nutshell respectively. Note body text migrates as plain text; any rich content or attachments stored within the Note are extracted separately and reattached as file uploads to the Nutshell Note record. Note timestamps and author information (Owner) map to the Nutshell activity attribution fields.

X2CRM Services track recurring service contracts or subscriptions linked to Accounts. We migrate Services as Nutshell Products with a custom field (service_type__c) set to 'Service Contract' to distinguish them from product catalog items, or as a separate custom field group on the associated Company record with renewal date and status fields. The customer's preference is documented during scoping.

X2Flow stores automation logic as trigger-action pairs with drag-and-drop UI configurations that are not accessible via the X2CRM REST API in a portable format. We extract every X2Flow workflow during discovery: trigger type, condition criteria, action sequence, and associated module. We produce a Workflow Reconstruction Document that maps each X2Flow rule to an equivalent automation logic in Nutshell's automation rules or to a manual process note for the customer to implement post-migration. Workflows do not execute or transfer as code.