Migrate from Zendesk Sell to HubSpot

Standard person contacts in Zendesk Sell map directly to HubSpot Contact records. Email is the primary unique identifier used for de-duplication. The contact's primary organization (linked via the contacts_organizations relationship) maps to the HubSpot Contact's primary company association. During migration, any duplicate email detected triggers a merge of the newer record into the existing HubSpot Contact, preserving the original created_at timestamp and all associated activities.

This is the most critical routing decision in the migration. Zendesk Sell stores organization-type contacts with a name and domain but no first/last name. FlitStack evaluates the is_organization flag on every contact and routes those records to HubSpot Companies instead of Contacts. The domain field maps to the HubSpot company domain property.

Zendesk Sell organizations are standalone company records with name, domain, industry, phone, and address fields. These map 1:1 to HubSpot Company records. The organization ID is preserved as a custom field for traceability. If the same entity exists as both an Organization record and an is_organization: true Contact, the Organization record is prioritized and the duplicate Contact is merged.

Zendesk Sell leads map directly to HubSpot Lead records. Lead status, lead source, owner, and custom fields transfer to their HubSpot equivalents. Leads that are converted in Zendesk Sell (marked as contacted/opportunity) can be mapped to HubSpot Contacts or Opportunities based on the lead's stage value.

Zendesk Sell deals map to HubSpot Deal records. Each deal carries its pipeline, stage, amount, probability, expected close date, owner, and custom fields. Pipeline names become HubSpot deal pipeline names; stage names map via value mapping to HubSpot deal stage names within each pipeline.

Zendesk Sell products with name, price, SKU, and description map to HubSpot Products. The product name maps to the HubSpot product name; the SKU maps to hs_sku. Products must exist in HubSpot before line items can reference them, so product migration runs before line-item migration.

Zendesk Sell line items link a product to a deal and carry quantity and discount information. These map 1:1 to HubSpot Line Items. The product reference resolves to the migrated HubSpot Product ID, and the deal reference resolves to the migrated HubSpot Deal ID.

Zendesk Sell call logs — including call direction, duration, outcome, timestamp, and associated contact or deal — map to HubSpot Calls logged against the corresponding Contact or Deal record. The original timestamp and owner are preserved. Call direction (inbound/outbound) maps to hs_call_direction; duration in seconds maps to hs_call_duration; outcome values map to hs_call_status where applicable. If a recording URL exists, it populates hs_call_recording_url for playback.

Email activity in Zendesk Sell (sent and received emails associated with contacts) migrates to HubSpot Email records attached to the Contact. The subject, body, timestamp, and owner all transfer. HubSpot's email tracking state (opened/clicked) is not preserved — that is a HubSpot-side tracking event with no Zendesk equivalent.

Zendesk Sell notes attach to contacts, deals, or organizations. They map to HubSpot Notes with the same body text, creation timestamp, and owner. Notes attached to multiple records in Zendesk are migrated as separate HubSpot Notes linked to each parent record.

Zendesk Sell tasks (reminders, to-dos) map to HubSpot Tasks attached to the corresponding Contact, Deal, or Lead. Task status, due date, priority, and owner transfer. Completed vs. open status is preserved. The task subject maps to hs_task_subject; the body maps to hs_task_body. Recurrence patterns are not transferred, as HubSpot Tasks lack native recurrence. If a task has a linked contact, the association is created via the HubSpot contact-to-task association.

Zendesk Sell SMS and WhatsApp messages are logged as HubSpot Communication records. The channel type (SMS, WHATS_APP, LINKEDIN_MESSAGE) maps to the hs_communication_channel_type property. The message body, timestamp, and direction (inbound/outbound) transfer. Media URLs from Zendesk Sell messages are stored in a custom HubSpot property, as Communication records do not preserve file binaries. Outbound messages keep the owner field; inbound messages assign the owner from the associated contact.

Zendesk Sell custom fields on any object — including custom fields on contacts, deals, leads, and organizations — require pre-creation of equivalent HubSpot Custom Properties. Field type mapping: text fields to single-line text, picklists to single-option or multi-option properties, number fields to number properties, date fields to date properties. Value mapping is required for picklist custom fields.

Zendesk Sell file attachments and documents linked to contacts, deals, or organizations are downloaded and re-uploaded to HubSpot Files. File associations are preserved by linking each file to the corresponding HubSpot record. File size limits (25MB per file in HubSpot) are enforced; files exceeding the limit are flagged for manual handling.

Zendesk Sell allows a contact to be associated with multiple organizations simultaneously (N:N). HubSpot supports one primary company per contact natively. For Enterprise-tier HubSpot portals, secondary associations can be created using Contact Association Types. For Starter and Professional tiers, only the primary association migrates and additional associations are flagged for post-migration manual setup.