Migrate from Kordeva to Twenty CRM

Kordeva Contact records map directly to Twenty People. Standard fields (name, email, phone, address) map to their Twenty equivalents. We preserve any custom contact-level attributes from Kordeva's Custom Fields API by creating matching custom fields in Twenty's Settings Data Model before import. The People record is the first migrated object because Twenty's Company-People relationship requires People to exist before the Company lookup can be resolved.

Kordeva Company records map to Twenty Company. The company domain name maps to the Website field and is used as the dedupe key during import. We create all Companies before importing People so that the People-Company relationship is satisfied at import time. Custom company-level attributes from the Kordeva Custom Fields API carry through as Twenty custom fields.

Kordeva Deal records map to Twenty Opportunity. The deal stage maps to Twenty's Opportunity stage values. Pipeline layout (stage-to-stage mapping) requires customer review during scoping since Kordeva's pipeline configuration is not exposed via documented API. We use the customer's stated stage order to configure the Twenty Opportunity pipeline before import.

Kordeva Activity records (calls, emails, meetings, tasks) log against contacts and deals. We export the full activity history and map call and meeting activities to Twenty Task records (with Task type differentiated via a custom field), and email records to Note records linked to the correct People or Opportunity. The mapping type is 1:1 but depends on API confirmation of activity retrieval since Kordeva's activity export endpoints are not publicly documented.

Kordeva custom fields defined on the Contact object map to Twenty custom fields on the People object. We enumerate all custom field definitions during discovery by querying the Kordeva Custom Fields API, then pre-create matching fields in Twenty's Settings Data Model with equivalent field types (text, number, date, select, multi-select) before importing any People records.

Kordeva custom fields defined on the Company object map to Twenty custom fields on the Company object. Same approach as Contact-level custom fields: enumerate via Kordeva Custom Fields API, create matching typed fields in Twenty Data Model, then import. Custom field values stored on existing Company records migrate as field data in the Company import.

Kordeva custom fields defined on the Deal object map to Twenty custom fields on the Opportunity object. We apply the same enumeration and pre-creation workflow before Opportunity import. Any deal-level custom field used for pipeline-specific tracking is flagged for the customer to configure as a Twenty custom field before migration runs.

Kordeva Owner records (the user assigned to a Contact, Company, or Deal) map to Twenty workspace Members. We extract all distinct owner emails referenced across the dataset and invite them to the Twenty workspace before import. Any owner without a matching Twenty user is held in a reconciliation queue for the customer's admin to provision before the relevant records import.

Kordeva includes accounts and invoicing at the Regular tier. Invoice records, line items, and payment status are migratable but require field-level mapping since invoicing schemas vary significantly between platforms. We typically map invoices to a custom Invoice object in Twenty if the customer has an active billing workflow, or to Note records attached to the relevant Company if the invoice history is reference data rather than operational. This requires explicit scoping during discovery.

Kordeva Intelligent Workflow is gated to the Premium tier. Workflow configurations do not migrate; we do not rebuild Kordeva workflows as Twenty workflows. We deliver a written inventory of every active Kordeva workflow with its trigger, conditions, and actions documented for the customer's admin to rebuild in Twenty's workflow builder post-migration. This is a separate services engagement outside standard migration scope.