Migrate from Kinabase to Pipedrive

A Kinabase Collection whose Fields resemble a contact — name, email, phone, job title — maps to Pipedrive Person. We create Pipedrive custom fields for any non-standard Kinabase Fields (e.g., a 'Department' dropdown) before import. Email becomes the dedupe key. The Collection's Records export as Person records with all mapped field values written to the corresponding Pipedrive Fields.

A Kinabase Collection storing company-level data — company name, domain, address, industry — maps to Pipedrive Organization. We use the company name as the Organization name and apply domain as the Website field where available. Any company-type Collection is created before Person import so that the Organization ID can be resolved and linked on Person insert.

A Kinabase Collection tracking transactional outcomes — deal name, value, stage, expected close date, owner — maps to Pipedrive Deal. We create a Pipedrive Pipeline with stages that correspond to the Kinabase Collection's stage values. Deal owner resolves by email match against Pipedrive Users. The Kinabase stage progression metadata is preserved as a written stage map for the admin to configure Pipedrive Automation or manual stage updates.

A Kinabase Collection that does not map cleanly to Person, Organization, or Deal — for example, a 'Projects' or 'Properties' Collection — migrates to a Pipedrive Custom Object (available on Power tier and above). We pre-create the Custom Object schema including all Kinabase Fields mapped to typed Custom Object fields, then import via Pipedrive's REST API. Custom Object records link to Persons, Organizations, or Deals via lookup relationships where the original Kinabase linked collection field pointed to a CRM-type Collection.

A Kinabase linked collection field (e.g., a 'Client' field in a 'Projects' Collection pointing to a 'Clients' Collection record) is a cross-collection foreign key. We export Collections in dependency order — parent Collections first — and resolve the Kinabase record ID to the newly created Pipedrive record ID at load time. The relationship is written as a typed Pipedrive Lookup field (Organization, Person, or Custom Object depending on destination type). If the target Pipedrive plan does not include Custom Objects, the linked reference is stored as a text field containing the referenced record name for denormalised reference.

Kinabase Computed Fields evaluate a formula expression dynamically — the result is stored but the formula is not persistent. Pipedrive has no computed field equivalent. We evaluate the formula at migration time using the field's expression logic (extracted from Kinabase's field definition), write the computed result as a static custom field value, and flag the formula as non-transferable in the pre-migration audit report. The customer receives the formula logic for reference if they wish to re-implement it in Pipedrive.

Kinabase Field types map to Pipedrive field types: short text to VARCHAR, long text to TEXTAREA, number to NUMBER, date to DATE, single-select dropdown to DROPdown, multi-select dropdown to MULTIdropdown. We create each custom field in Pipedrive before the corresponding Collection data loads. Multi-select Kinabase dropdowns require a separate Pipedrive MULTI dropdown field; values are comma-separated during import.

Kinabase standalone Tasks map to Pipedrive Activities (type Task). We preserve assignees (resolved by email to Pipedrive User), due date, status (open/closed), and the linked record association (which Person, Organization, Deal, or Custom Object the task belongs to). Task subject and body map to Pipedrive subject and note respectively.

Kinabase Documents attached to Records are exported by filename and reference URL. Pipedrive does not support importing file binary content via CSV or standard API import. We capture the filename, original URL, and linked record association, then document the file location for the customer to manually re-attach in Pipedrive or use Pipedrive's Google Drive / OneDrive integrations to link the same files post-migration.

Kinabase stage values (Draft, In Progress, Approved, Closed) within a Collection migrate as a categorical value. For deal-type Collections, stage values become Pipedrive Deal stage labels within the configured Pipeline. For other Collections, the stage value is stored as a Pipedrive dropdown custom field. We map the visual stage order from Kinabase to the Pipedrive stage sequence so that the relative progression is preserved.

Kinabase workflows define stage progression, trigger-based rules, role-based permissions, and scheduled actions. Pipedrive Automation (available on Growth+ tiers) uses a different action-trigger model. We do not migrate workflows as code. We audit every Kinabase workflow definition, document its trigger conditions and actions in a written Workflow Inventory, and map each to a recommended Pipedrive Automation equivalent. The customer's Pipedrive admin rebuilds them post-migration.