Migrate from Populate to Nutshell

Populate Person records map 1:1 to Nutshell People records. The Person's inline company name must be resolved: if a matching Nutshell Company exists, link via CompanyId; if not, create the Company first, then link. Nutshell People records require a Name field (full name or first+last).

Populate Company records map directly to Nutshell Company records. Nutshell Companies have standard fields for name, domain/website, address, phone, and industry, plus optional fields such as employee count and annual revenue. Parent-company hierarchies in Populate map to Nutshell's parent_company relationship if present. All fields are written via Nutshell's JSON-RPC API, and any missing optional fields default to empty without causing import errors.

Populate records with a lead/prospect status map to Nutshell Leads. Nutshell Leads have their own custom field support separate from People. If Populate stores leads as People with a status flag, the split into Nutshell Lead vs People happens during migration based on the status value.

Populate Deal records map to Nutshell Deals. Each Deal requires a linked CompanyId and optionally a linked PeopleId. Nutshell Deal stages are configurable per pipeline — stage names from Populate map to Nutshell stage values value-by-value. Deal amount, close date, and owner map directly.

Populate pipeline configuration maps to Nutshell Pipeline configuration. If Populate supports multiple pipelines, each becomes a separate Nutshell Pipeline. Pipeline stage names in Populate must map to Nutshell stage values within each Pipeline — this requires a value-mapping table per pipeline.

Populate activity records split into Nutshell Activities (calls, emails, meetings with timestamps and owners) and Notes (text content). Nutshell stores activities as part of the record timeline; Notes are separate objects linked to People, Companies, or Deals. Original timestamps and owner assignments are preserved.

Populate custom fields on Person records require pre-creation in Nutshell as custom fields on the People object before migration. Field types (text, number, date, pick-list) must match Nutshell's supported types. Once created in Nutshell, data migrates directly into the custom field.

Populate custom fields on Company records migrate to Nutshell Company custom fields. These must be created in Nutshell before data loads. Nutshell's field type constraints apply — pick-list fields in Populate map to Nutshell 'choices' type with the same options listed.

Populate custom fields on Lead records migrate to Nutshell Lead custom fields. Lead-specific fields (e.g., source, qualification status) map to custom fields in Nutshell. All custom fields on Leads must exist in Nutshell before the migration batch runs. If any custom fields are missing, FlitStack AI will pause and prompt the admin to create them prior to the run.

Populate owner/user records resolve by email match to Nutshell Users. If a Populate owner email matches an existing Nutshell User email, the Deal or Person owner maps to that User. Unmatched owners are flagged before migration — teams either invite them to Nutshell or assign records to a fallback owner.

Populate file attachments on records (People, Company, Deal) are downloaded and re-uploaded to Nutshell as Files linked to the parent record. Nutshell stores files with name, content type, and size. Large files may be subject to Nutshell's file size limits.