Migrate from Getfly CRM to Nutshell

Discovery and field schema extraction

We audit the Getfly account via API (using the provided X-API-KEY) across Accounts, Deals, Pipeline stages, Products, Activities, Campaigns, and Users. We extract the full pipeline stage configuration, inspect custom field schemas by sampling records, and identify the PABX recording volume for timeline planning. We deliver a written scoping document that includes the object inventory, estimated record counts per object, and the Account-to-People/Company split rule based on the Getfly field schema. If the customer has not completed a field audit from Getfly's admin panel, we request one at this stage to reduce custom field miss rates.

Nutshell schema design and field mapping

We configure the destination Nutshell account: pipeline stages (mapped from Getfly stage names and order), custom fields on People and Companies (mapped from Getfly Account custom fields with type inference), Products (mapped from Getfly Products), and any required nutshells. We map Getfly Account records into the split model: organizations to Company, individuals to Person (optionally linked to a Company). Schema configuration happens in a Nutshell trial or sandbox environment first for validation.

Owner reconciliation and User provisioning

We extract every distinct Getfly User referenced on Account, Deal, and Activity records and match by email against the Nutshell destination's User table. Any Getfly owner without a matching Nutshell User goes to a reconciliation queue. The customer's Nutshell admin provisions any missing Users (active or inactive depending on whether the original Getfly user is still employed). Migration cannot proceed past this step because Activity and Deal ownership requires a valid Nutshell User reference.

Sample migration and mapping validation

We run a sample migration of up to 100 Getfly Accounts and their associated Deals and Activities into Nutshell, targeting the trial/sandbox environment. The customer's admin reviews the mapped records in Nutshell, checks field alignment, and signs off the mapping configuration. Any corrections to the Account split logic, custom field type mapping, or pipeline stage alignment happen here before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (validated from step 3), Companies (from Getfly organization Accounts), People (from Getfly individual Accounts with Company links resolved), Opportunities (from Getfly Deals with stage and owner resolved), Products (from Getfly Products with custom fields flattened), Activity history (Tasks, Meetings, Emails, Calls via batched API calls), and Campaigns (last). Call recording URLs are downloaded during the Activity phase and re-uploaded. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, delta sync, and automation handoff

We freeze Getfly writes during the cutover window, run a final delta migration of any records modified during the migration window, then set Nutshell as the system of record. We deliver the Workflow and Automation inventory document to the customer's admin team for rebuild in Nutshell's automation builder. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. Post-migration admin support, training, and workflow rebuild are separate engagements.