Migrate from Spotler CRM to Nutshell

Spotler Contact records map 1:1 to Nutshell Person records. Email address serves as the dedupe key for Person import. We preserve the Spotler Contact's name fields, phone, address, and custom properties, creating Nutshell Person custom fields with identical API-compatible names before import. The Contact-to-Company relationship resolves to Nutshell's Person-accountId reference once Accounts are loaded.

Spotler Company records map directly to Nutshell Account. Industry, size, address, and website migrate as standard fields. The company_id is preserved internally but does not surface as an API field in Nutshell's entity model; we use Account name and domain as the dedupe criteria. Account records must load before Person records so that the accountId lookup resolves correctly during Person insert.

Spotler Opportunity records map to Nutshell Deal. We collect the source pipeline stage names during scoping and map them to Nutshell Deal statuses (New, Qualified, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Won, Lost). Deal value, expected close date, and owner resolve by email matching to the Nutshell User table during import. Closed-won and closed-lost reasons from Spotler custom fields migrate as Nutshell Deal notes.

Spotler stores all engagement types within a single Activity object distinguished by a type field. We split on type: Spotler tasks map to Nutshell Task, calls map to Nutshell Task with a call-subtype indicator, meetings map to Nutshell Event, and notes map to Nutshell Note. Each activity's related record ID (Contact or Company) resolves to a Nutshell Person or Account ID before insert. The original Spotler timestamp becomes ActivityDate so that the Nutshell timeline preserves chronological order.

Spotler allows free-form custom field creation with dropdown lists stored as separate reference IDs in settings. We export the field definition table alongside data and pre-create all custom fields in Nutshell before any record values load. Dropdown list values require explicit one-to-one mapping because Spotler stores list values as internal IDs while Nutshell stores them as plain-text labels. We run a validation pass comparing Spotler dropdown labels to Nutshell dropdown labels after field creation to catch any silent mapping gaps.

Spotler Quotations (Professional and Enterprise) carry line items, pricing, and status. Nutshell offers a Quoting add-on on Pro and above. We export quotation records and line items as separate tables, then reconstruct them in Nutshell using the Quoting module if the customer has the add-on, or as Deal-linked custom fields and notes if not. We confirm the customer's Nutshell plan and add-on status during scoping to determine the correct target.

Spotler Users (name, email, role, group membership) export from the user table. We match by email against the Nutshell destination User records. Any Spotler Owner or User without a matching Nutshell User goes to a reconciliation queue for the customer admin to provision before record import resumes. Roles (Admin, Standard, Read-only) map to the closest Nutshell permission tier.

Spotler stores both static list membership and per-record tags. We export tag names per Contact and recreate them in Nutshell as multi-select picklist values on the Person custom fields section. List membership is preserved as a comma-separated tag string. The customer chooses whether tags map to a single multi-select field or split across multiple categorical fields during scoping.