Migrate from Kinabase to Twenty CRM

A Kinabase Collection whose Fields map to standard contact attributes (name, email, phone, address) maps to Twenty CRM's Person object (API name Person). Collections with company-level attributes (legal name, domain, industry, employee count) map to Twenty CRM's Company. We classify each Collection during the pre-migration field audit and assign a mapping type before any export begins.

Kinabase Collections representing deals, projects, or engagements map to Twenty CRM Opportunity. Stage Fields in the Collection map to the Opportunity stageName field. Amount Fields map to amount, and owner assignment maps to the User resolved from the Collection's assigned-user field.

Any Kinabase Collection that does not fit a standard Twenty CRM object maps to a Twenty custom object. We pre-create the custom object schema via the /metadata API (Twenty v0.26+) before migration, including all custom Fields typed as text, number, date, boolean, or relation. Each custom Field gets a unique name matching the source Collection Field with an underscore suffix if a naming conflict exists.

Individual Kinabase Records migrate as rows in the corresponding Twenty CRM object. We map field values by type: text fields to text, numbers to number, dates to date, and dropdown selections to Twenty's select or multiselect type. Null values and empty strings are handled explicitly to avoid unexpected required-field failures on insert.

A Kinabase linked-collection field (e.g., a 'Client' field in a 'Projects' Collection pointing to a 'Clients' Collection record) creates a foreign-key dependency. We export linked Collections in dependency order: parent Collections first, then child Collections. The foreign key value is written as a relation ID in Twenty's custom object relation field. If the target Twenty custom object does not yet exist, the reference is stored as a text field (original_record_id__c) and resolved during a second pass after the parent object is created.

Kinabase Computed Fields evaluate a formula expression at display time; the formula itself is not stored data. We evaluate each formula at migration time using the stored operand values and write the resulting scalar value as a static text or number field in Twenty CRM. The formula is not preserved. We flag every Computed Field in the pre-migration audit with a note that the result value transfers but the expression does not.

Kinabase activity records stored as sub-Records or typed Fields in a Collection (e.g., a 'Interactions' linked Collection or timestamp Fields) map to Twenty CRM Task or Note. Call duration maps to a custom duration field, meeting location maps to a note body, and timestamps are preserved as the ActivityDate on the target Twenty record.

Kinabase standalone Tasks map directly to Twenty CRM Task. We preserve assignee, due date, status (open, completed), and any linked-record reference via the Relation field. Task body or description maps to the note field on Twenty Task.

File attachments linked to Kinabase Records are exported as filename and reference URL only. Twenty CRM does not include file attachments in CSV imports — they must be re-uploaded manually, migrated via API, or handled through a partner-assisted migration. We export the file association as a text field pointing to the original URL or filename for the customer's admin to re-attach post-migration.

Kinabase stage Fields (Draft, In Progress, Approved, Closed) are categorical values. We map them to Twenty's stageName picklist on Opportunity for deal-type Collections, or to a custom status select field on custom objects for non-deal Collections. The stage values are preserved verbatim; the visual pipeline representation does not transfer.

Kinabase owner fields reference a user in the platform. We match by email against the Twenty CRM workspace User list. Any Kinabase Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before the record import phase. If a Twenty workspace is self-hosted and has no Users yet, we advise provisioning at least one admin User before migration begins.

Kinabase Workflows define stage progression, trigger-based rules, and scheduled actions. Twenty CRM does not replicate Kinabase's workflow engine. We capture the full workflow definition — triggers, conditions, actions, and stage maps — as a structured JSON inventory document and deliver it to the customer's admin for rebuild as a documented reference. Automated actions, notifications, and approval gates are not migrated.