Skip to content
Get a quote

Zendesk Sell to HubSpot migration

Moving from Zendesk Sell to HubSpot CRM means rewriting your data model from Zendesk's contact-organization split to HubSpot's native Company + Contact objects — with deal pipelines, custom fields, and activity history preserved. FlitStack AI handles the is_organization routing, owner resolution by email match, and the pipeline-to-deal-stage value mapping so your HubSpot portal is live without a day of manual re-entry.

Short answer

FlitStack AI migrates contacts, companies, leads, deals and products from Zendesk Sell to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records with a straightforward data model.

By

Source Zendesk Sell
DestinationHubSpot
ContactCompanyLeadDealProduct
Mapped field by field · sample run · one-click rollback

What moves from Zendesk Sell to HubSpot?

Zendesk Sell's data model splits its contact records by an is_organization flag — records marked true behave as company records, and records marked false behave as person contacts.

Read the full summary

HubSpot uses separate Company and Contact objects natively, so every Zendesk Sell contact record must be evaluated at migration time to determine whether it lands as a HubSpot Company or a HubSpot Contact. FlitStack AI reads the is_organization flag and the associated data (domain, name format, employee count) to route records correctly, avoiding duplicate company records when the same entity appears as both an org-flagged contact and a standalone organization in Zendesk Sell. We migrate contacts, organizations, leads, deals, products, line items, calls, emails, meetings, notes, tasks, and custom fields via the Zendesk Sell Core API, mapping each field to its HubSpot equivalent. Workflows, sequences, and automation logic are not transferred — Zendesk Sell's automation engine has no HubSpot equivalent, and these must be rebuilt as HubSpot workflows post-migration. We deliver a field-level diff against a representative sample before the full run commits, and a 24–48 hour delta-pickup window captures any records modified in Zendesk Sell during cutover so HubSpot reflects your final source state at go-live.

direct

Contact (is_organization: false) → Contact

Standard person contacts in Zendesk Sell map directly to HubSpot Contact records.

How it maps

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.

transformed

Contact (is_organization: true) → Company

This is the most critical routing decision in the migration.

How it maps

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.

direct

Organization → Company

Zendesk Sell organizations are standalone company records with name, domain, industry, phone, and address fields.

How it maps

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.

direct

Lead → Lead

Zendesk Sell leads map directly to HubSpot Lead records.

How it maps

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.

direct

Deal → Deal

Zendesk Sell deals map to HubSpot Deal records.

How it maps

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.

direct

Product → Product

Zendesk Sell products with name, price, SKU, and description map to HubSpot Products.

How it maps

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.

What moves15 objects
Zendesk SellHubSpot
  • ContactContact1:1
  • ContactCompanytransformed
  • OrganizationCompany1:1
  • LeadLead1:1
  • DealDeal1:1
  • ProductProduct1:1

+ 9 more in the mapping below

How Zendesk Sell and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionZendesk SellHubSpot
Contact vs. Company modelZendesk Sell uses a single Contact object with an is_organization flag. When is_organization is true, the contact behaves as a company record — it has no first/last name but has a name and domain.HubSpot uses separate Company and Contact objects. A record with is_organization = true in Zendesk must become a HubSpot Company record; is_organization = false becomes a HubSpot Contact record.
Contact-company associationsZendesk Sell supports N:N relationships — a single contact can be associated with multiple organizations, and a single organization can have multiple contacts.HubSpot supports one primary Company per Contact via the native associations API. Secondary company associations require HubSpot's paid Enterprise tier Contact Association Type feature.
Lead handlingZendesk Sell has a distinct Lead object, separate from Contact. Leads have their own status, source, and owner fields.HubSpot routes incoming people into the Contact object and optionally the Lead object depending on lifecycle stage. The Lead and Contact objects are separate in HubSpot and require explicit lifecycle-stage routing.
Pipeline and stage modelingZendesk Sell pipelines are tied to deal records. Each pipeline has named stages with probability percentages. Stages are pipeline-specific and cannot be shared across pipelines.HubSpot Deals use a single pipeline object with stages per pipeline. Probability is a stage-level property. Stage names are free-text and scoped to each deal pipeline independently.
Workflows and automationsZendesk Sell sequences, triggers, and automation rules live in the Sell automation engine and can include time-based actions, lead scoring, and email sequences.HubSpot has no equivalent import format. Workflows must be rebuilt in HubSpot's workflow editor or via HubSpot's Automation API. FlitStack exports the rule definitions as a rebuild reference.
Product and line-item modelZendesk Sell products are standalone objects with name, price, and SKU, linked to deals via line items. A line item references one product and one deal.HubSpot Products are linked to Deals via Line Items. The product SKU maps to the hs_sku property, and the line item amount, quantity, and discount all have direct HubSpot equivalents.
User/owner resolutionZendesk Sell owner_id on each record references a Sell User object. Owners have names, emails, and role-based permissions.HubSpot uses owner_id on Contact, Deal, Ticket, and Lead. Matching is performed by email address. Unmatched owners are flagged before migration — they must be invited to HubSpot first or assigned to a fallback owner.

Zendesk Sell to HubSpot field mapping

The 30 most-used fields of 60 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
Zendesk SellHubSpot
  1. first_nameContact firstnameContact
  2. last_nameContact lastnameContact
  3. emailContact emailContact
  4. phoneContact phoneContact
  5. mobileContact mobilephoneContact
Zendesk Sell fieldHubSpot fieldMappingNote
Contact.first_nameContact.firstnamedirect
Contact.last_nameContact.lastnamedirect
Contact.emailContact.emaildirect
Contact.phoneContact.phonedirect
Contact.mobileContact.mobilephonedirect
Contact.titleContact.jobtitledirect
Contact.addressContact.addressdirect
Contact.cityContact.citydirect
Contact.stateContact.statedirect
Contact.postal_codeContact.zipdirect
Contact.countryContact.countrydirect
Contact.websiteContact.websitedirect
Contact.created_atContact.createdatedirect
Contact.updated_atContact.lastmodifieddatedirect
Contact.idContact.hs_object_iddirect
Contact.is_organizationCompany.is_organization__mapping_flagtransformedWhen is_organization is true, the contact record routes to a HubSpot Company instead of a Contact. The flag value is preserved in a custom property for audit.
Contact.organization_nameCompany.nametransformedFor is_organization: true contacts, the organization_name field maps to the HubSpot Company name property.
Contact.domainCompany.domaindirect
Contact.owner_idContact.hubspot_owner_idtransformedOwner resolved by email match against HubSpot users. Unmatched owners flagged before migration; records assigned to a fallback owner if not resolved.
Organization.nameCompany.namedirect
Organization.domainCompany.domaindirect
Organization.industryCompany.industryvalue_mappingIndustry pick-list values in Zendesk Sell map to HubSpot's industry pick-list via value mapping. Custom industry values are created as HubSpot custom properties.
Organization.employee_countCompany.numberofemployeesdirect
Organization.phoneCompany.phonedirect
Organization.addressCompany.addressdirect
Organization.created_atCompany.createdatedirect
Organization.idCompany.hs_object_iddirect
Lead.first_nameLead.firstnamedirect
Lead.last_nameLead.lastnamedirect
Lead.emailLead.emaildirect

What to watch for in a Zendesk Sell to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

is_organization split creates duplicate company records if both entity types exist

Zendesk Sell stores organizations in two places: as standalone Organization records and as Contact records with is_organization = true.

How we handle it

Both record types contain company data (name, domain, industry). Migrating both independently into HubSpot creates duplicate Company records — the same legal entity appears twice with slightly different field populations. FlitStack detects this collision by domain match and email-match heuristics: the richer record wins, and the secondary record is merged with a flag preserved for audit. Teams must confirm the deduplication rule during the sample migration review before the full run.

high

N:N contact-company associations collapse to one primary association in non-Enterprise HubSpot

Zendesk Sell's contact-organization relationship is many-to-many: a single contact can belong to multiple organizations simultaneously, and vice versa.

How we handle it

HubSpot's Contact-to-Company association is natively one-to-many (one Contact, many Companies) only at the Enterprise tier with Contact Association Types enabled. On HubSpot Starter and Professional plans, only the primary company association migrates. Secondary associations are flagged in the migration report, and teams on non-Enterprise plans must recreate them manually post-migration using HubSpot's company associations UI.

medium

HubSpot has no lifecycle stage equivalent for pre-migration deal state

Zendesk Sell tracks deal progress through its pipeline stages (Qualification, Proposal, Negotiation, Closed Won, Closed Lost).

How we handle it

HubSpot Deals have a dealstage property and a closedate, but no concept of a deal lifecycle stage separate from the pipeline stage value. Deals that were closed-won in Zendesk Sell become closed-won in HubSpot (dealstage = Closed Won), but the historical time spent in each prior stage is not preserved as a separate audit trail. If deal stage history is needed for reporting, it must be recreated using HubSpot's deal stage history API or a custom object.

medium

Zendesk Sell API rate limit is 36,000 requests per hour per token

The Zendesk Sell Core API enforces a rate limit of 36,000 requests per hour (10 requests per token per second).

How we handle it

For migrations involving 200,000+ records with associated activities, this cap can extend migration clock time significantly if pagination and retry logic are not managed carefully. FlitStack uses paginated API fetches with exponential backoff and batch inserts into HubSpot's bulk import API to stay within rate limits while maximizing throughput. Large migrations may run overnight or across multiple days to respect the rate ceiling.

low

HubSpot marketing contact billing flag has no Zendesk equivalent

HubSpot bills based on the number of marketing contacts in your portal at the start of each billing period.

How we handle it

A contact becomes a marketing contact when they receive HubSpot marketing emails, are added to a HubSpot list, or interact with tracked marketing content. Zendesk Sell has no equivalent concept — all contacts are treated uniformly. When migrating contacts into HubSpot, teams should decide proactively whether contacts should be imported as marketing contacts or kept as sales-only contacts to avoid an unexpected billing increase. FlitStack can suppress the marketing-contact flag during import on request.

How the migration runs

  1. Audit Zendesk Sell data model and pre-create HubSpot custom properties

    FlitStack reads the Zendesk Sell account via the Core API to inventory all object types, custom fields, and pipeline configurations.

    What this step covers

    We identify all is_organization: true contacts that require company routing, N:N association groups that will be affected by the HubSpot association limit, and custom field types that need HubSpot property pre-creation. We deliver a HubSpot setup checklist — listing every custom property to create, every pipeline to configure, and every pick-list value to set up — so the HubSpot portal is schema-ready before any data moves.

  2. Resolve owners and users by email match

    We extract the full user list from Zendesk Sell — name, email, role, and owner_id — and match each against HubSpot users by email address.

    What this step covers

    Email is the unique identifier for owner resolution in HubSpot's API. Any Zendesk Sell owner with no corresponding HubSpot user account is flagged in the migration plan with a recommended fallback owner assignment. No record lands in HubSpot without a resolved owner; this prevents orphaned records and broken assignment rules at go-live.

  3. Migrate companies before contacts; contacts before deals; deals before activities

    HubSpot enforces foreign-key dependency ordering: Company records must exist before Contacts can associate to them, and Deal records must exist before Line Items can link to them.

    What this step covers

    FlitStack sequences the migration in four phases: Phase 1 migrates Organizations and is_organization: true Contacts to HubSpot Companies (with deduplication applied); Phase 2 migrates is_organization: false Contacts and Leads with primary company associations resolved; Phase 3 migrates Deals with pipeline and stage mapping applied; Phase 4 migrates Products, Line Items, Calls, Emails, Notes, and Tasks in dependency order.

  4. Run a sample migration with field-level diff

    A representative sample — typically 200–500 records spanning the full object mix — migrates first.

    What this step covers

    We generate a field-level comparison report showing every mapped field, the source value, the destination value, and any transformation applied. The is_organization routing, N:N association collapse decisions, stage value mapping, and owner resolution are all visible in the diff. You review the diff report before we proceed to the full run. Mapping adjustments are made at this stage at no additional cost.

  5. Execute full migration with delta-pickup window and rollback on demand

    The full migration runs in dependency order against the production HubSpot portal.

    What this step covers

    A delta-pickup window of 24–48 hours opens at cutover: any Zendesk Sell records created or modified during the window are captured and applied to HubSpot after the initial bulk load completes. Every operation is logged in the audit log. If reconciliation fails — missing records, duplicate companies, incorrect stage mapping — one-click rollback reverts the HubSpot portal to its pre-migration state so the migration can be re-run with corrected mappings.

Zendesk Sell HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 25,000 records with a straightforward data modelTypical, smaller accounts
3–4 weeks for complex setups with 100,000+ records, multiple pipelines, or extensive custom field configurationsLarge or heavily customised accounts

Pricing is driven by three variables: total record count across contacts, organizations, leads, deals, and activities; the number of custom fields requiring HubSpot property creation and value mapping; and the degree of data-model divergence — particularly the is_organization split (which doubles the record-routing validation work), N:N contact-company associations that require post-migration secondary-association setup, and multi-pipeline deal configurations that need per-pipeline stage mapping. Standard migrations with under 25,000 records and fewer than 30 custom fields land in the lower range. Complex migrations with 200,000+ records, 50+ custom properties, and multiple deal pipelines land at the upper end of the range. Sample migrations, field-level diffs, and delta-pickup are included in every engagement. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Zendesk Sell to HubSpot →

Why teams move from Zendesk Sell to HubSpot

  • Zendesk Sell is retiring on August 31, 2027. Organizations that depend on Sell for pipeline management, forecasting, and deal tracking need a replacement CRM in place before the sunset date — and waiting until the last quarter creates unnecessary migration risk, rushed configuration, and potential data loss that a deliberate early migration avoids entirely.
  • Zendesk Sell functions as a standalone sales CRM with limited native integration between sales activity and marketing or customer service data. HubSpot's all-in-one platform connects sales, marketing, and service hubs in a single database, eliminating the need for a separate helpdesk and reducing the total tool stack cost for growing teams.
  • Per-seat pricing in Zendesk Sell scales linearly with team size, and advanced automation features are gated behind higher tiers. HubSpot's free CRM tier provides core contact and deal management for small teams, with predictable upgrade pricing as the team grows — reducing the per-agent cost for teams with 5–15 sellers.
  • Zendesk Sell's automation engine — sequences, triggers, and lead scoring rules — has no direct export format and must be rebuilt in any destination CRM. HubSpot's workflow editor and Breeze AI capabilities offer a different automation paradigm that requires deliberate process redesign rather than a simple configuration port.
  • Zendesk Sell's pricing add-ons for advanced reporting, data export, and API rate-limit tiers compound at scale. HubSpot's native reporting on the Sales Hub Professional plan covers deal tracking, sales rep activity, and pipeline forecasting without additional per-feature charges at the same tier.

Questions, answered

Zendesk Sell to HubSpot migration questions

How long does a Zendesk Sell to HubSpot migration take?

For under 25,000 records across contacts, organizations, leads, deals, and activities, the full migration typically completes in 48–72 hours of clock time. Complex migrations with 100,000+ records, five or more deal pipelines, or 50+ custom fields extend to 3–4 weeks. The is_organization routing and N:N association pre-work add 1–2 days to the planning phase. HubSpot custom property creation and pipeline configuration are completed before data moves, so the migration clock itself starts from a schema-ready state.

Will my Zendesk Sell workflows, sequences, and triggers migrate to HubSpot?

No. FlitStack migrates data and schema only — Zendesk Sell workflows, sequences, triggers, and automation rules do not transfer. The automation engines are architecturally incompatible: Zendesk Sell's sequence engine uses time-based actions and cadence rules that have no HubSpot equivalent. We export your Zendesk Sell workflow definitions as a structured reference document so your HubSpot admin can rebuild them in HubSpot's workflow editor. Macros and templates also do not migrate and must be recreated manually or rebuilt as HubSpot snippets.

What happens to my Zendesk Sell contacts that have is_organization = true in HubSpot?

Contacts with is_organization = true in Zendesk Sell are routed to HubSpot Company records — not Contact records. The organization name maps to the HubSpot Company name, the domain maps to the HubSpot Company domain property, and other org-level fields (industry, employee count) map to their HubSpot equivalents. The is_organization flag value is preserved in a custom property (Zendesk_is_Organization__c) for audit traceability. If the same entity also exists as a standalone Organization record, the two are deduplicated: the richer record wins and the duplicate is merged.

Can I migrate Zendesk Sell custom fields to HubSpot?

Yes. Every Zendesk Sell custom field on contacts, organizations, leads, deals, and products is mapped to a corresponding HubSpot custom property. HubSpot custom properties must be created in the portal before the migration runs — FlitStack delivers a pre-migration checklist with the property name, type, and options for every custom field so your HubSpot admin can create them in advance. Pick-list custom fields require value-by-value mapping; multi-select pick-lists map to HubSpot multi-checkbox or multi-option properties. Custom fields on the legacy custom objects API require additional schema review and are scoped in the initial audit.

What happens to Zendesk Sell deals with multiple stages in multiple pipelines during migration?

Each Zendesk Sell deal pipeline becomes a separate HubSpot deal pipeline. The pipeline name maps directly to the HubSpot pipeline name. Within each pipeline, stage names are mapped via value mapping to the corresponding HubSpot deal stage names. Stage probability percentages transfer as the hs_deal_stage_probability property for each stage in HubSpot. If your Zendesk Sell deals reference stages from multiple pipelines (which is possible in edge cases with deal re-piping), each deal's stage maps to the stage in whichever pipeline the deal was active in at migration time.

Does the migration affect my Zendesk Sell account during cutover?

No. FlitStack uses scoped read access on Zendesk Sell via the Core API — your team continues working in Zendesk Sell throughout the migration. No records are modified or deleted in Zendesk Sell. A delta-pickup window of 24–48 hours opens at cutover to capture any records created or modified in Zendesk Sell during the final phase of the migration. Those delta records are applied to HubSpot after the initial bulk load so that HubSpot reflects Zendesk Sell's final state at go-live. Your Zendesk Sell account remains fully functional until the day you choose to deactivate it.

What is the biggest risk specific to migrating Zendesk Sell to HubSpot compared to other CRM migrations?

The is_organization flag is the highest-risk element unique to this migration pair. Because Zendesk Sell conflates people and organizations in the Contact object, migrating contacts without evaluating the flag produces duplicate Company records in HubSpot — one from the is_organization: true Contact and one from the standalone Organization record for the same entity. This inflates your HubSpot company count, breaks reporting, and creates duplicate records that require manual cleanup post-migration. FlitStack's pre-migration audit explicitly surfaces every potential duplicate before the full run, and the sample migration diff makes the collision visible for your review.

Will my Zendesk Sell products and line items work correctly in HubSpot after migration?

Zendesk Sell products migrate as HubSpot Products with SKU, name, and price preserved. Line items — which link a product to a deal with quantity and discount — migrate as HubSpot Line Items attached to the corresponding migrated Deal. The product reference on each line item is resolved to the migrated HubSpot Product ID. Products must be migrated before line items, so the sequence is enforced in the migration approach. If a product was deleted in Zendesk Sell but referenced by historical line items, the line item migration flags the orphaned reference for manual resolution.

Get a quote

Moving from Zendesk Sell to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote