Migrate from Spin CRM to Nutshell

Spin CRM Contacts map to Nutshell People. The email address on the Contact is the primary dedupe key during import. The company association from Spin CRM (Contact linked to a Company record) is resolved by matching the Company name in the Contact export against the Company name in the Nutshell Companies import, then the company_id reference is written at Person insert time. Nutshell People support custom fields on the Person tab, which we configure to match any Spin CRM custom contact fields before insert.

Spin CRM Companies map to Nutshell Organizations. Spin CRM Company records (name, address, industry, custom properties) insert first as the anchor object so that the relationship from People to Organization is satisfied when the People import runs. Organization is the first object we insert in every Spin CRM migration because all other object imports depend on it.

Spin CRM Leads map to Nutshell Leads. Both platforms use Lead as the unqualified-prospect container. Status, source, owner, and custom lead fields transfer directly. We recommend creating Nutshell custom lead fields to match any Spin CRM custom lead fields during the schema-design phase before any Lead records are inserted.

Spin CRM Deals map to Nutshell Deals. Each Deal is linked to a Person (the primary contact) and optionally to an Organization. The Deal's stage name from Spin CRM must exist in Nutshell's pipeline stage configuration before the import runs—we replicate the Spin CRM stage sequence and names in Nutshell as a pre-import configuration step. Deal value, expected close date, and owner all transfer directly.

Spin CRM's customizable pipeline stages map to Nutshell pipeline stages. Spin CRM allows fully customizable stage names and order; we extract the complete stage configuration (stage name, position, probability if set) during scoping and configure the corresponding stages in Nutshell before any Deal records are imported. On Foundation tier, Nutshell supports one pipeline; Pro and above support multiple pipelines.

Spin CRM Activities may be exportable via CSV but the export mechanism is not confirmed in documented sources. We attempt export of the activities object (tasks, notes, call logs) during discovery. If the CSV export produces a valid file, we import activities as Nutshell Activities linked to the corresponding Person or Deal via name-based lookup. If the export is unavailable or produces empty files, we flag this in the discovery report and note the limitation in the handoff documentation.

Spin CRM supports custom fields on Leads, Contacts, and Deals. Nutshell supports custom fields on People, Organizations, Leads, and Deals. We configure Nutshell custom fields to match the Spin CRM custom field names and data types (text, long text, currency, date, dropdown) during the schema-design phase before any records are imported. Custom field values are then included in the respective object imports. This step requires explicit validation of the Spin CRM CSV column headers against the customer's reported custom field list.

Spin CRM Owner references on Contacts, Companies, Deals, and Activities map to Nutshell Users. We extract all distinct owner email addresses from the exported records and match them against the Nutshell destination account's User list. Any owner without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before the record import proceeds. Unresolved owner references default to the importing admin user and are flagged in the post-migration reconciliation report.