Migrate from Kizen to HighLevel

Kizen Contacts map directly to GoHighLevel Contacts. Standard fields (name, email, phone, address, lifecycle stage, owner) map to their GoHighLevel equivalents. Custom Contact properties are mapped as Contact Custom Fields. We resolve the owner reference by email match against GoHighLevel Users. Contact record count and field inventory are established during schema discovery.

Kizen Companies map to GoHighLevel Companies. Domain, industry, size, and revenue fields map to their GoHighLevel equivalents where present. Company records are migrated before Contact records so that the Company lookup relationship is satisfied at Contact insert time. Deduplication runs on company domain as the matching key.

Kizen Deals map to GoHighLevel Opportunities. Pipeline stage, amount, close date, and owner assignment migrate directly. Kizen deal properties map to GoHighLevel Opportunity Custom Fields. The Opportunity-Contact association migrates by resolving the Contact ID reference to GoHighLevel Contact ID.

Kizen Pipelines (standard Objects with ordered stage definitions) map to GoHighLevel Pipelines. Stage names and stage order migrate. Stage-specific field defaults map as custom field values on the Opportunity record. We capture the full pipeline configuration during schema discovery before configuring the GoHighLevel destination pipeline.

Kizen custom Objects (user-defined data containers) do not have a direct GoHighLevel equivalent. We map custom Object fields to Contact Custom Fields or Opportunity Custom Fields depending on the Object's relationship to Contact or Deal records. Highly complex custom Objects with multiple relationship types may require partial denormalization into text fields. Schema discovery determines the mapping strategy per Object.

Kizen Activities are distinct Object records that capture interactions logged against Objects. We migrate the activity type, timestamp, linked Object reference, and activity body to GoHighLevel's activity model (calls, emails, meetings, notes). The parent record reference is resolved to the corresponding GoHighLevel Contact or Opportunity ID at migration time. Activity ordering is preserved by timestamp.

Kizen Primary (one-to-many) and Additional (many-to-many) relationship fields require reconstruction in GoHighLevel's flat record model. Where the relationship is one-to-many (e.g., Company to Contacts), we use GoHighLevel's standard Company lookup on Contact. Where the relationship is many-to-many or Kizen-specific, we denormalize the related record IDs into a custom text field or comma-separated ID field, preserving the association for query purposes while noting that it changes the data access pattern.

Kizen Tags applied to Object records migrate as GoHighLevel Tags. Tags are preserved as multi-value label arrays on the Contact or Opportunity record. We do not migrate tag grouping or taxonomy hierarchies that exceed GoHighLevel's flat tag model.

File attachments linked to Kizen Objects migrate as binary blobs with their parent record reference preserved. We note that GoHighLevel's document management capabilities differ from Kizen's; file associations migrate but the document repository structure does not.

Kizen standard Automations (field updates, email sends, task creation) are catalogued with trigger conditions, action sequences, and logic flow. We deliver a written automation inventory document with each automation's trigger event, conditions, and action chain described in plain text, plus a recommended GoHighLevel Workflow equivalent. The rebuild is performed by the customer's admin post-migration.