Migrate from FowCRM to Nutshell

FowCRM Account records map directly to Nutshell Company records. The account name, industry, website, address fields, and any custom properties attached to the Account model migrate as-is. We create Companies first in the migration sequence because every Contact record references an account_id that must resolve at insert time. Account is the migration anchor; no other object can be imported until all Accounts are present in Nutshell.

FowCRM Contact records map to Nutshell People records. We preserve the link to the parent Company by resolving the FowCRM account_id against the Company records inserted earlier, writing the Nutshell Company ID into the People.Company field. FowCRM lifecycle stage and contact status fields migrate as custom fields on People since Nutshell uses a single People object rather than separate Contact and Lead objects. Any FowCRM Contact without an account_id is flagged for the customer to assign a Company manually before migration or to set as a lead in Nutshell.

FowCRM Deal records map to Nutshell Deal records. The deal name, amount, expected close date, stage, and pipeline assignment migrate directly. We map FowCRM deal stage values to Nutshell stage values during the scoping phase, flagging any closed-won or closed-lost deals that may carry historical revenue recognition data. Owner assignment migrates by email match against the User mapping. Deals without a resolved Company or People reference are held in a reconciliation queue.

FowCRM Pipelines with configurable stages and probability percentages map to Nutshell Pipeline records. We export each Pipeline's stage definitions, stage order, and probability values and create matching Pipelines in Nutshell before Deal import begins. Stage names that differ between FowCRM and Nutshell are resolved via a mapping table created during scoping. Probability percentages migrate as integer values on the Nutshell stage definition.

FowCRM Cases (requests and complaints) are tier-gated on Professional and Enterprise plans only. If the customer's FowCRM plan exposes the Cases module via API, we migrate Case records as custom fields on the related Nutshell People record, with Case status mapped to a custom picklist field and priority mapped to a custom priority field. If the customer's plan is Standard, the Cases endpoint returns 403 and we skip the export gracefully. We check plan tier during discovery and include Case migration only when the API confirms the module is active.

FowCRM Survey definitions and response data are tier-gated on Professional and Enterprise plans. Survey questions and answers are exported as structured JSON and mapped to Nutshell custom fields on the relevant People or Company record. Survey response dates migrate as custom date fields. We treat Survey data as a mapping exercise because Nutshell has no native survey object; the customer reviews the resulting field structure in Nutshell post-migration.

FowCRM Activity records (calls, emails, meetings, and tasks) linked to Contacts or Accounts migrate to Nutshell Activity records linked to the corresponding People or Company. We categorize activities by type during the FowCRM export and create matching Nutshell activity records, preserving the activity timestamp, subject, description, and owner assignment. Activities without a resolvable parent People or Company reference are flagged for manual assignment in Nutshell post-migration.

FowCRM Custom Fields are defined per Model and require a two-step discovery process: enumerate all Models first, then fetch Field definitions for each Model. We run the Model enumeration step before any field data export, building a complete model-to-field index that prevents the empty-result issue that occurs when querying Fields directly. Each discovered custom field is typed (picklist, text, date, number) and matched to the equivalent Nutshell custom field type on People, Company, or Deal. We pre-create Nutshell custom fields via the API before data import begins.