Migrate from Zendesk Sell to HighLevel

Sell Leads map to GoHighLevel Contacts with a custom field sell_lead_source__c preserving the original lead source value. Sell's Lead conversion process (converting a Lead to a Contact with associated Deal) has no direct GoHighLevel equivalent because GoHighLevel does not maintain a separate Lead object; converted Leads land as Contacts directly. We set sell_original_type__c = 'Lead' on all records migrated from the Lead object so the customer's team can filter and report on formerly-unqualified records.

Sell Contacts migrate directly to GoHighLevel Contacts with standard fields (name, email, phone, address) and all custom Contact fields mapped to GoHighLevel custom fields. Duplicate detection runs on email as the primary key. Contact owner maps to GoHighLevel User by email match. We resolve sell_custom_field_id to the field key during the scoping phase using Sell's Custom Fields Mapping API endpoint before any write occurs.

Sell Deals map to GoHighLevel Opportunities. The Deal's value, stage, loss reason, and source migrate directly. The sell_pipeline and sell_stage assignment from Sell becomes a GoHighLevel pipeline with inline stage configuration. Closed-Loss reason from Sell's loss_reasons property migrates to a custom opportunity field loss_reason__c. We create GoHighLevel pipelines with stage names matching the destination naming convention before Opportunity records are imported.

Sell Pipelines map to GoHighLevel Pipeline objects. Each Sell Pipeline becomes a separate GoHighLevel pipeline with the same ordinal position preserved. Stages inside each Sell Pipeline map to stage entries inside the corresponding GoHighLevel pipeline configuration with probability percentages rounded to nearest integer and status values (open, won, lost) set to match Sell's stage flags.

Sell Tasks migrate to GoHighLevel Tasks with due dates, assignees, completion status, and priority preserved. Task owner resolves to GoHighLevel User by email. Notes attached to Tasks in Sell migrate as child records sequenced after the Task itself is created. Recurring Task patterns in Sell do not have a GoHighLevel equivalent and are flagged in the automation inventory.

Sell Notes attached to Contacts, Deals, Leads, or Companies migrate as GoHighLevel Notes with parent reference intact. The parent Contact or Opportunity ID is resolved at migration time so that conversation context links to the correct record in GoHighLevel. Rich-text formatting in Sell Notes is preserved as-is in GoHighLevel Note body.

Sell Users (sales reps, admins) export with email, role, and territory. We map Users to GoHighLevel Users by email match. Territory assignments in Sell do not have a direct GoHighLevel equivalent and are flagged for the customer's admin to reconfigure in GoHighLevel's team or location settings post-migration.

Sell Tags applied to Contacts, Deals, and Leads migrate as GoHighLevel Tags. Tag-based segmentation in Sell maps to GoHighLevel tagging with the note that GoHighLevel's tag filtering operates at the contact level for list and workflow segmentation. We flag any tag-naming conflicts during scoping.

Sell Line Items attach to Deals and represent products or services with quantity and price. GoHighLevel does not have a native Line Item object as a discrete API object. We map Line Items to GoHighLevel custom opportunity fields or to a custom opportunity products table that the customer configures in GoHighLevel's custom field builder. This is flagged during scoping and requires customer decision on how to model product lines in GoHighLevel.

Sell call logs, call outcomes, and call duration data migrate to GoHighLevel Call records linked to the Contact. Call recordings are audio files that require separate file transfer; we migrate the metadata and recording URL pointer and flag the file transfer as a separate step requiring file storage configuration in GoHighLevel.