Migrate from Kizen to Pipedrive

Kizen's core unit is the Object — a customer-defined container with custom fields and relationships. We discover every Object via the Kizen API at migration time and map each one to the closest Pipedrive equivalent. Simple Objects with flat fields map to Pipedrive People or Organizations. Objects with key-value pairs map to Pipedrive custom fields on the relevant object. Complex Objects with relationships to other Objects may require denormalization into text fields or a separate custom Object strategy depending on Pipedrive plan tier.

Kizen Contacts are standard Objects with fields for name, email, phone, address, and lifecycle stage. We map these directly to Pipedrive People. Custom Contact properties migrate as Pipedrive custom fields on Person. Owner assignment resolves by email match to Pipedrive User.

Kizen Companies map to Pipedrive Organizations. The company domain maps to Organization Website. We preserve the one-to-many relationship back to Contacts during migration by linking each Contact to its parent Organization via the Organization ID field. Industry, size, and revenue fields map where present as Pipedrive custom fields.

Kizen Deals track pipeline records with stage, amount, close date, and owner. We map these directly to Pipedrive Deals with the Kizen pipeline becoming a Pipedrive pipeline and Kizen stages becoming Pipedrive stages. Custom deal fields migrate as Pipedrive Deal custom fields. The Deal-to-Contact and Deal-to-Company links resolve via the parent record lookup at migration time.

Kizen Pipelines are Objects with ordered stage definitions. We export pipeline names, stage names, and stage order, then configure equivalent Pipedrive pipelines and stages before any Deal migration begins. Stage-specific field defaults map as custom field values on the Deal record at the relevant stage.

Kizen Activities are a distinct object type capturing interactions logged against Objects. Not all activity types are equally structured. We preserve the activity record and its linked Object reference by mapping to Pipedrive Notes with a timestamp field and a reference to the parent Person, Organization, or Deal. Structured activities (calls, emails, meetings) with duration or outcome fields map to Pipedrive Activity records where available or to custom fields on the linked entity.

Kizen's Primary relationship type creates one-to-many linked records. Pipedrive supports lookup links on People and Organizations but does not expose a configurable relationship field API. We resolve the relationship by setting the linked record's foreign key reference at migration time. If the destination does not support the relationship type natively, we denormalize the relationship into a text field containing the linked record ID or name.

Kizen's Additional relationship type creates many-to-many associations that have no direct Pipedrive equivalent without building a junction object. We denormalize Additional relationships into a text field on the primary record containing the comma-separated IDs or names of all linked records. This preserves the association for audit and reporting but changes how the data is queried at the destination.

Kizen tags are label values applied to Object records. We export tags as Pipedrive custom fields configured as multi-select picklists or as plain text values depending on tag volume and cardinality. Tags without a clear Pipedrive equivalent are preserved in a custom field for manual cleanup post-migration.

File attachments linked to Kizen Objects are exported as binary blobs with their parent record reference. We attach files to the corresponding Pipedrive Person, Organization, or Deal record via the Pipedrive file upload API. Document management capabilities vary by Pipedrive plan tier; Enterprise plans include higher storage limits.

Kizen Owners assigned to Contacts, Companies, Deals, and Activities resolve by email match against the Pipedrive destination User table. Any Kizen Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive user status is preserved where possible.