Migrate from Salesflare to Nutshell

Discovery and API audit

We audit the source Salesflare portal via REST API across all tiers, capturing Accounts, Contacts, Opportunities, Pipelines, Activities, Tags, Custom Properties, and Users. We export pipeline definitions as metadata, pull the complete custom property map per object, and identify any enrichment data attached to Contact records from Salesflare's signature-scraping engine. We also document active sequences and their step configurations during discovery for the written handoff document, even though they are not migrated as data.

Schema design and Nutshell field mapping

We design the destination schema in Nutshell, provisioning custom fields on Company, Person, and Deal objects to receive Salesflare's custom properties. We configure Nutshell Pipelines matching the Salesflare pipeline definitions, including stage names, stage order, and win probability values. We identify any Salesflare custom objects that cannot map directly to a Nutshell standard object and propose a flattening strategy (custom fields on Person or Deal) during scoping. Schema is validated in a Nutshell sandbox if available before production.

Data export and transformation

We export Accounts first, then Contacts (with the Account-Contact junction preserved as a linked Persons list), then Opportunities (with AccountId and OwnerId resolved), then Activities (calls, emails, meetings, tasks with timestamps preserved). Tag assignments export as a join table per object type. We transform field data types where Salesflare types differ from Nutshell (e.g., multi-checkbox fields become Nutshell multi-select fields). The API pagination strategy handles large exports with exponential backoff on rate-limit responses.

Sandbox reconciliation

We run a full test migration into the customer's Nutshell destination org, importing a representative data slice (typically the 90-day pipeline plus 500 random Contacts). The customer reconciles record counts, spot-checks 25-50 records for field accuracy, and validates that pipeline stage assignments and the Account-Contact junction resolved correctly. Any field mapping corrections, missing custom fields, or picklist value gaps are addressed here before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (no dependencies), then Persons (with company_id resolved from the Companies import), then Deals (with owner_id and company_id resolved), then Activities (with Person and Company IDs resolved for the timeline links), then Tags. Each phase emits a row-count reconciliation report before the next phase begins. The migration user is granted the necessary Nutshell permissions before each phase.

Cutover, validation, and handoff

We freeze Salesflare writes during the cutover window, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the sequence and automation handoff document to the customer's admin team, along with the dashboard rebuild inventory listing every Salesflare custom dashboard that requires recreation in Nutshell. We support a one-week hypercare window for reconciliation issues. We do not rebuild Salesflare sequences as Nutshell Automation Rules inside the migration scope; that is a separate engagement or an internal admin task.