Migrate your Kizen data

Kizen's core data unit is the Object — a user-defined container with custom fields and relationships. Every Kizen customer's schema is unique. We discover the Object list via the Kizen API at migration time, map each Object to the destination equivalent, and handle field-type translation. Required fields and validation rules must be replicated at the destination.

Contacts are standard Kizen Objects with well-documented fields. We map name, email, phone, address, lifecycle stage, and owner assignment directly. Custom Contact properties are migrated as mapping.

Companies are standard Objects with relationship fields back to Contacts. We preserve the one-to-many relationship during migration, and map domain, industry, size, and revenue fields where present.

Deals track pipeline records with stage, amount, close date, and owner. We map deal fields and link them to corresponding Contact and Company records. Custom deal fields are handled as mapping.

Kizen Activities are a distinct object type that captures interactions logged against Objects. Not all activity types are equally structured; we preserve the activity record and its linked Object reference but flag activity text as unstructured content requiring destination field mapping.

Kizen Forms and Surveys create and update Object records. Form definitions (field names, types, conditional logic) must be replicated at the destination separately from the submitted data. We export submitted records and flag the form definition as a manual rebuild item.

Kizen allows custom fields on any Object, added at the Object level or via the Customize Fields page. Custom field types include text, number, date, choice, currency, and relationship fields. We inventory all custom fields during discovery and map each to the destination field by type and name.

Kizen supports Primary (one-to-many) and Additional (many-to-many) relationship types defined at the Object or custom field level. Relationship fields must be reconstructed at the destination. We capture the relationship type, source field, and target Object for every relationship defined in the schema.

Kizen Automations trigger on events and execute sequences of actions. Standard workflow automations (update field, send email, create task) translate to destination workflow rules. AI-driven automations and multi-agent orchestration steps are flagged as non-transferable logic requiring manual rebuild.

Pipelines are standard Kizen Objects with ordered stage definitions. We export pipeline names, stage names, and stage order. Stage-specific field defaults are mapped as custom field values.

File attachments linked to Objects are exported as binary blobs with their parent record reference. We preserve the association but note that document management capabilities vary by destination CRM.

Tags in Kizen are label values applied to Object records. We export tags as multi-select field values or tag arrays depending on destination support. Tags without a clear destination equivalent are preserved as a custom text field.