Migrate from CRM and Deals for Zendesk to HighLevel

Zendesk Contact records map 1:1 to GoHighLevel Contacts. Standard fields (name, email, phone, address) migrate directly. Custom fields on Zendesk Contact map to GoHighLevel custom fields which must be pre-created in the destination account before import. We resolve the primary Organization link and write it as the Contact's primary company affiliation in GoHighLevel.

Zendesk Organizations map to GoHighLevel Companies. The organization domain, custom fields, and address data migrate directly. GoHighLevel Companies are created before Contact import so the company-contact affiliation is satisfied at insert time. Zendesk's flat org structure maps cleanly to GoHighLevel's single company type without the multi-level Account hierarchy that Salesforce uses.

Zendesk Deals map to GoHighLevel Opportunities. This is the highest-risk mapping because Zendesk stores pipeline stage, probability, and deal value as properties on the Deal object, but stage-change history lives in the Activities table. We run a de-normalization query joining Activities to Deals to reconstruct a synthetic stage-history array before writing to GoHighLevel's pipeline stage entries.

Zendesk Pipelines become GoHighLevel Pipelines with stage names, ordering, and probabilities preserved. GoHighLevel Pipelines are created before Deal migration so that each Deal can be assigned to the correct pipeline and stage at insert time. Non-standard stage names in Zendesk are mapped to GoHighLevel stage labels with a lookup table built during scoping.

Zendesk Activities are stored as a flat table with a polymorphic relationship to Contact or Deal via type and id fields. Each Activity must be typed and routed to the correct GoHighLevel timeline entry: calls become Opportunity Call Log entries, emails become Opportunity Emails, meetings become Opportunity Meetings. Activity dates are preserved as timestamps on each entry. The split is computed at migration time using the Activity's related_type field.

Zendesk Notes attached to Contacts or Deals migrate as GoHighLevel Notes linked to the corresponding Contact or Opportunity. Zendesk Tasks migrate as GoHighLevel Tasks with status, due date, and assignee preserved. Task assignment resolves by matching the Zendesk agent email to a GoHighLevel user email.

Zendesk Tickets do not have a native GoHighLevel equivalent because GoHighLevel is not a help-desk platform. We discuss the customer's desired treatment during scoping: closed tickets migrate as read-only Opportunity Notes or Contact Notes for historical context; open tickets are flagged as a separate inventory item for manual handling or a dedicated help-desk migration to a separate platform. We do not attempt to force a ticket-to-task 1:1 mapping because the object semantics differ substantially.

Zendesk v2 Custom Objects map to GoHighLevel Custom Objects. We pre-create the GoHighLevel schema including all custom fields and lookup relationship fields before any records are imported. Lookup relationships to Contacts or Companies require the parent record to exist at insert time, so we sequence Custom Object migration after Contact and Company migration.

Zendesk Legacy Custom Objects cannot be written to GoHighLevel directly because the v1 API schema is deprecated and incompatible. We run the mandatory five-step v2 migration: object type definition, schema creation, relationship type creation, record import, then relationship record linkage. This step adds 3-5 days to the timeline and may reveal object counts that exceed GoHighLevel's Custom Object plan-tier limits on the customer's target plan.