Migrate from Kinabase to Nutshell

Kinabase Collections that store individual contact records (people, clients, contacts) map to Nutshell People. The Collection's Fields map to Nutshell standard fields (name, email, phone, address) or custom fields on People. We create any custom People fields in Nutshell before migration begins and validate field types for compatibility (text, number, date, dropdown). Multi-select dropdowns in Kinabase map to Nutshell multi-select custom fields.

Kinabase Collections that store company or organisation records map to Nutshell Company. Fields such as company name, domain, industry, and address map to Nutshell's standard Company fields. Additional Fields on the Collection become custom Company fields in Nutshell. Company records are created before People records so that the People-Company association can be established via the nutshel_person_accounts relationship.

Kinabase Collections that represent sales or project deals map to Nutshell Deals. The Collection's stage field (e.g., Draft, Proposal, Won, Lost) maps to a Nutshell Deal status or custom pipeline field. Value or amount Fields map to the Deal's monetary fields. We configure Nutshell's pipeline stage values to match the source Collection's stage vocabulary before import.

A Kinabase linked Collection field (e.g., a 'Client' field in a 'Projects' Collection pointing to a 'Clients' Collection) is a cross-collection reference. In Nutshell, this maps to the built-in People-Company association if the link connects a Person to an Organisation, or to a denormalised text field containing the referenced record ID if the link connects to a non-standard entity. We export linked records in dependency order and resolve the target Nutshell record ID at load time.

Kinabase Computed Fields evaluate a formula at display time; the formula itself is not stored data. During migration, we evaluate each Computed Field formula against the source record at migration time and write the resulting value as a static field in Nutshell. The formula does not migrate — only the computed result is preserved. We flag every Computed Field in the pre-migration audit and document the formula logic for the customer to implement in Nutshell as a calculated field or reporting metric if needed.

Kinabase standalone Task records map to Nutshell Tasks. Assignee Fields map to the Task owner in Nutshell, due date Fields map to due_date, and status Fields map to the Task status field. Tasks linked to a specific record in Kinabase retain that association by setting the Nutshell Task's related Person, Company, or Deal reference.

Kinabase engagement records stored within a Collection or linked via a relationship field map to Nutshell Activities on the relevant People record. Email activities map to Nutshell email records, call records map to Task (Call) subtype, and meeting records map to Nutshell Event or Task (Meeting). Timestamps and owner references are preserved. We handle these as a post-record-import batch to ensure the parent People record exists first.

Kinabase Collections that represent custom entity types not native to Nutshell (e.g., Projects, Properties, Subscriptions) require a mapping decision during scoping: the Collection can become a set of custom fields on the most closely related Nutshell object (e.g., Project details on Deal), or the records can be stored as a denormalised JSON or text block in a custom field. We document this decision per Collection in the scoping phase and implement the agreed approach during schema setup.