Migrate from folk to Nutshell

Discovery and Group enumeration

We audit every Group in the folk workspace, extract the full field schema for each Group (field names, types, and options), and inventory the contact distribution across Groups. We identify Groups with pipeline views, Groups with no pipeline views, and Groups with overlapping field names. We also extract all tag vocabulary, note counts, reminder counts, and deal pipeline stage data. The discovery output is a written scope with a per-group field map, a conflict report for fields that appear in multiple Groups, and a list of any manually established person-to-company links.

Schema design and field normalization

We design the Nutshell destination schema using discovery data. We create global custom fields in Nutshell for all folk custom fields, normalized by name and type across Groups. We provision the Nutshell Pipeline (or Pipelines if multiple folk Groups contain deal pipelines) and configure the stage names to match the source pipeline view stages. We add a custom Person Type picklist field to preserve the folk subtype distinction between person and company contacts. Schema changes are validated in Nutshell's UI before any data import begins.

CSV extraction and reconciliation

We extract CSV files from each folk Group using the multi-step CSV export process. We reconcile field names and values against the discovery field map, validate required fields (name, email) are present, and flag records with missing required data. We resolve folk workspace user emails to Nutshell user emails for assignee mapping. We extract manually established person-to-company links and build a link registry for re-establishment in Nutshell.

Nutshell API import of contacts and companies

We import contacts and companies into Nutshell via the REST API, using CSV fallback where the API import path is constrained. Person-type folk contacts import as Nutshell People; company-type contacts import as Nutshell Companies. We apply the custom Person Type picklist value from the original folk subtype. After the initial import, we reconcile record counts against the source CSV totals and resolve any import errors (duplicate detection, required field violations).

Tag and note migration with parent resolution

We migrate tags by creating matching Nutshell Tag records and applying them to the corresponding Person records. Notes migrate as Nutshell Notes linked to the parent Person or Company. We resolve the parent record ID in Nutshell using the email or name dedupe key established during import. Any notes that reference a parent record not found in Nutshell are flagged for manual review.

Deal and pipeline migration

We create the Nutshell Pipeline and stage structure during schema design. We then migrate folk deal records as Nutshell Deals, linking each Deal to the associated Person or Company using the link registry from discovery. Stage history from folk's pipeline view migrates as custom Deal fields. We reconcile deal counts against the source pipeline data and flag any Deals that reference a Person or Company not found in the destination.

Cutover, validation, and automation handoff

We freeze writes in folk during cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We deliver a reconciliation report showing record counts, tag coverage, and any unresolved links. We provide a written inventory of any folk workflows or automations that require rebuild in Nutshell. We do not rebuild automations as code — that work belongs to the customer's admin team using Nutshell's automation tools. We offer a one-week post-migration support window for reconciliation issues raised during the first week of live use.