Migrate from CRM and Deals for Zendesk to HubSpot

Zendesk Leads map directly to HubSpot Contacts. The migration routes every Zendesk lead record into HubSpot as a contact. HubSpot does not have a separate Lead object; all prospects land in the Contact object with lifecycle_stage reflecting their position in the funnel. The original Zendesk lead creation date is preserved as a custom datetime property for reporting continuity.

Zendesk Contacts migrate to HubSpot Contacts 1:1. Standard fields (name, email, phone, job title, address) map to HubSpot's corresponding contact properties. Owner resolution happens by matching the Zendesk contact owner email to a HubSpot user email, with unmatched owners flagged before migration commits records to HubSpot.

Zendesk lead_status values (New, Open, Won, Lost) do not map directly to HubSpot lifecycle_stage because HubSpot's model uses a longer funnel progression. We map each Zendesk lead status value to the most appropriate HubSpot lifecycle_stage: 'New' and 'Open' typically map to 'lead' or 'MQL' based on your specification, 'Won' maps to 'customer', and 'Lost' maps to a custom property or lifecycle stage of your choosing.

Zendesk Organizations map to HubSpot Companies 1:1. Organization name maps to Company name, domain maps to the Company website property, industry maps to industry (with value-mapping for picklist alignment), and employee count maps to numberofemployees. Zendesk parent-child organization hierarchies are preserved using HubSpot's Parent Company field.

Zendesk allows a contact to be associated with multiple organizations. HubSpot contacts have one primary Company association plus secondary company associations via the Company Contacts feature. We migrate the most-recently-modified organization as the primary company (or the one you specify as primary) and surface all others as secondary company associations in HubSpot.

Zendesk Deals map to HubSpot Deals. The deal name maps to dealname, amount maps to amount, close date maps to closedate, and owner maps to hubspot_owner_id resolved by email match. The primary translation work is mapping the Zendesk deal stage and status to the appropriate HubSpot deal pipeline and stage.

Zendesk Deal status (open, won, lost) combined with deal stage name maps to HubSpot Deal stage values. If Zendesk has a single pipeline, we create one HubSpot deal pipeline. If Zendesk uses deal categories or multiple pipelines, we create corresponding HubSpot pipelines. Stage probability and forecast category are re-applied per HubSpot pipeline configuration.

Zendesk activities—calls, emails, meetings, and tasks—migrate to HubSpot's engagement timeline on the associated Contact record. HubSpot shows these as logged activities with original timestamps, activity type, and owner preserved. Emails map as email engagements, calls as call activities, meetings as meeting events, and tasks as notes on the contact timeline.

Zendesk notes attached to contacts, deals, or organizations migrate to HubSpot as notes on the corresponding record. Rich-text formatting is preserved where possible. The note creation date and note author are mapped to HubSpot's note metadata.

Files attached to Zendesk deals, contacts, or organizations are downloaded from Zendesk and re-uploaded to HubSpot's file storage, then linked to the target record. HubSpot allows up to 256MB per file on most plans, so files exceeding this limit are flagged for manual handling. Original filenames and creation dates are preserved on upload. Inline images embedded in notes are extracted and re-hosted individually in HubSpot's file manager to ensure they render correctly on the contact or deal timeline.

Zendesk custom objects (available on Suite Professional and Enterprise plans) map 1:1 to HubSpot custom objects. We create the corresponding HubSpot custom object schema, define its properties, and migrate all custom object records. Custom object associations that are many-to-many in Zendesk may require HubSpot custom junction objects, which we surface in the migration plan.

Zendesk users who are assigned as deal owners or contact owners are resolved against HubSpot users by matching the email address. Unmatched users are flagged before migration runs so your team can either invite them to HubSpot or reassign their records to a designated fallback owner. No record lands without a valid HubSpot owner assignment.