Migrate from Kizen to Twenty CRM

Kizen's standard Contact Object maps to Twenty's Person record. Name, email, phone, address, and lifecycle stage properties migrate directly. Custom Contact properties (fields added by the Kizen admin) are inventoried during schema discovery and mapped to Twenty custom fields or to the properties JSON field depending on field type. We resolve any owner assignment by matching Kizen owner email to Twenty workspace User email.

Kizen Company records map to Twenty Company records. Domain becomes the website field and is used as the dedupe key. Industry, size, and revenue fields migrate where present. The one-to-many relationship between Company and Contact (Kizen's Primary relationship type) is preserved by setting the Person's company link to the migrated Company record.

Kizen Deal records map to Twenty Opportunity records. Pipeline stage maps to Opportunity stage, amount maps to amount, and close date maps to close date. Owner assignment migrates via email resolution. Custom Deal fields are mapped to Twenty custom fields. Kizen's pipeline and stage definitions migrate as stage configuration.

Each Kizen pipeline with its ordered stage definitions becomes a set of Opportunity stage values in Twenty. Stage probability percentages from Kizen migrate to Twenty's stage probability configuration. We preserve the stage order from Kizen as the canonical pipeline sequence.

Kizen Activities are a distinct object type capturing interactions logged against Objects. We classify Kizen activities by type: logged-call activities map to Twenty Task with a call subtype marker, meeting activities map to Twenty Event, and note activities map to Twenty Note. The linked Object reference is preserved by resolving the Person, Company, or Opportunity ID at migration time. Not all Kizen activity types are equally structured; we migrate structured fields and preserve the activity record reference.

Kizen custom Objects (user-defined containers with custom fields) map to Twenty custom object types. During schema discovery we inventory every Kizen custom Object, its fields, and its relationship definitions. We create equivalent custom object types in Twenty, including all custom fields typed to match Kizen's field definitions. Custom object naming follows Twenty's convention. Objects with lookup relationships to other Objects are handled via Twenty's custom field lookup references.

Kizen allows custom fields on any Object including text, number, date, choice, currency, and relationship field types. Every custom field is inventoried during schema discovery. We map each to a typed Twenty field or to the properties JSON container for field types that Twenty does not natively support. Validation rules (required, format) are noted and reproduced in Twenty where the field type supports equivalent rules.

Kizen's Primary relationship type (one-to-many, typically Contact-to-Company or Deal-to-Company) maps to a Twenty lookup field on the child record pointing to the parent record. We resolve the parent record ID during migration and set the lookup reference. The relationship is preserved as a structured link rather than denormalized.

Kizen's Additional relationship type (many-to-many, where a record can link to multiple other records of a given type) is handled in Twenty via a multi-select field if the cardinality is small, or by creating an intersection custom object type if the relationship requires full many-to-many semantics. The choice is made during scoping based on the customer's query patterns.

Kizen tags are label values applied to Object records. Tags stored as multi-value field properties migrate to Twenty's tag field or to a multi-select text field depending on the destination schema. Tags without a clear destination equivalent are preserved in a migration_notes field for manual review.

File attachments linked to Kizen Objects are exported as metadata records with parent reference, filename, and storage location. Twenty's CSV import does not include file attachment binary data. We preserve the association in a migration notes file listing every attachment with its parent record and filename. The customer re-uploads attachments manually or uses Twenty's API for programmatic upload post-migration.