Migrate from Spiro to Nutshell

Spiro Companies map to Nutshell Companies with standard fields (name, domain, address, phone) migrated directly. If multiple Spiro Company records share the same legal entity or domain, we normalize them into a single Nutshell Company during transform. Custom Company fields from Spiro are extracted via CSM-assisted export and recreated as custom fields in Nutshell before the Company import phase begins.

Spiro Contacts map to Nutshell People with name, email, phone, title, and address preserved. Custom Contact fields migrate as custom properties on the Person object. We match by email address as the dedupe key during Nutshell import. Spiro contacts without an email address are imported with a generated placeholder and flagged for manual review.

Spiro Opportunities map to Nutshell Deals with deal value, close date, and owner preserved. Spiro stage names (e.g., Prospecting, Demo Scheduled, Proposal Sent) must map explicitly to Nutshell's default stage labels or to custom stages the customer defines in Nutshell before migration. We run stage mapping as a configuration step before any Deal records are inserted.

Spiro custom field definitions must be extracted from the Spiro UI or confirmed with a CSM because there is no documented public endpoint returning the full custom field schema. We request a field inventory export during discovery, recreate each field in Nutshell with the matching type (text, number, date, picklist, checkbox), and deploy the schema before data import begins. Custom fields exist on Companies, Contacts, and Opportunities in Spiro.

Spiro Activities (calls, emails, meetings, tasks) link to Contacts and Companies. We migrate activity history as Nutshell Activities with the original timestamp preserved for timeline ordering. Note that if Spiro's email integration was disconnected during certain periods, those activities were never logged and cannot be backfilled. We recommend exporting available activity logs from Spiro before the migration window opens to capture any records at risk.

Spiro User records map to Nutshell Users by email address match. Any Spiro Owner referenced on a Contact, Company, or Opportunity record without a matching Nutshell User is placed in a reconciliation queue. The customer's Nutshell admin provisions missing Users (active or inactive depending on whether the Spiro user is still employed) before the migration resumes. OwnerId must be resolvable for all imported records.

Spiro uses a single Opportunity pipeline per workspace. If the customer uses multiple logical pipelines (e.g., separate sales motions for SMB and Enterprise), these must be modeled in Nutshell as separate Pipelines with their own stage definitions before migration. Nutshell Growth and above support multiple independent pipelines; Foundation supports one. We configure Nutshell Pipelines during the schema design phase based on the customer's Spiro pipeline usage.

Spiro stores file attachments as linked URLs rather than embedded blobs. We verify each attachment URL is reachable before migration and re-link them in Nutshell. If the source Spiro workspace access is revoked post-migration, attachment links become orphaned. We strongly recommend customers download critical files before the migration window closes. This is a known limitation of Spiro's storage model and applies to all outbound migrations from the platform.