Migrate from Kizen to HubSpot

Kizen contact records map directly to HubSpot contacts. The contact's primary company link maps to HubSpot's primary company association; any additional Kizen company links migrate as HubSpot secondary company associations. Owner assignment resolves by email match to HubSpot users. and any mismatched owners are flagged for manual review.

Kizen company records map to HubSpot companies. Kizen's parent-child company hierarchy maps to HubSpot's parent company field. Multi-contact company associations in Kizen translate to HubSpot's company-contact relationship model where each contact links to its primary company. All company IDs are preserved as custom properties for audit traceability.

Kizen deal records map to HubSpot deals. Kizen pipeline stages map to HubSpot deal pipeline stages with value-by-value mapping. Stage probabilities re-apply based on HubSpot's stage configuration. Kizen deal owner resolves to HubSpot deal owner by email match. All deal IDs are stored as custom properties for reference.

Kizen task records map to HubSpot engagement tasks. Original timestamps, owners, and associated contacts/companies/deals preserve their links during migration. Kizen task status (complete/incomplete) maps to HubSpot engagement completion state. All activity IDs are stored as custom properties to maintain historical traceability and support delta imports.

Kizen note records migrate as HubSpot notes on the associated contact, company, or deal. Original create timestamps and note owners carry forward. Rich-text formatting in Kizen notes converts to HubSpot's note format. All note IDs are preserved as custom properties to ensure continuity for future reporting and audit trails.

Kizen custom objects map to HubSpot custom objects (Enterprise tier). Each custom object creates as a HubSpot custom object with the same name. Custom object associations in Kizen that are N:N require HubSpot junction objects or association preservation as custom properties.

Kizen's N:N relationship fields don't have a direct HubSpot equivalent. We map them by: (1) using HubSpot's native associations where the object pair is supported (Contact-Company, Deal-Contact), or (2) creating a custom property on the primary object that stores the related record IDs as a reference list for manual rebuilding.

Kizen workflow automations do not migrate. We export the automation definitions — triggers, conditions, and action sequences — as a structured reference document. Your HubSpot admin uses this to rebuild equivalent logic in HubSpot's workflow builder or_sequence editor. The exported file includes step-by-step flow diagrams for easier recreation.

Kizen report configurations do not migrate. Underlying data (contacts, deals, activities) migrates fully so you can rebuild equivalent reports in HubSpot's analytics tools. Kizen report export (where available) serves as the schema reference for rebuilding. This ensures continuity of historical reporting after the migration.

Kizen owner records resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — your team either creates HubSpot users first or assigns records to a fallback HubSpot user. System IDs from Kizen preserve as a custom property for audit traceability.

Kizen file attachments on records re-upload to HubSpot Files and re-associate to the migrated record. File size limits per HubSpot's storage tier apply. Inline images in Kizen notes download and rehost as HubSpot file assets.

Kizen sequences and email templates do not migrate. We export the sequence steps and template content as a reference for rebuilding in HubSpot's sequences tool or email template editor. Sequences in HubSpot operate differently — triggers and enrollment logic must be redesigned.