---
title: "Salesforce Service Cloud to HubSpot Service Hub Migration"
description: "Migrate Salesforce Service Cloud to HubSpot Service Hub with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/hubspot-service-hub"
---

# Salesforce Service Cloud to HubSpot Service Hub migration

We migrate Cases, Contacts, Accounts, Case Comments, and engagement history from Salesforce Service Cloud into HubSpot Service Hub as Tickets, resolving the Entitlement-to-SLA field mapping, preserving Case milestone timestamps, and flagging every Salesforce Flow that requires a HubSpot replacement before any records move.

Short answer

FlitStack AI migrates tickets, contacts, companies, ticket conversation threads and custom property or snapshots from Salesforce Service Cloud to HubSpot Service Hub, 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: 4-8 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/hubspot-service-hub#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Salesforce Service Cloud ![](https://flitstack.ai/platforms-trim/salesforce-service-cloud.webp)

Destination HubSpot Service Hub ![](https://flitstack.ai/platforms-trim/hubspot-service-hub.webp)

Ticket Contact Company Ticket conversation thread Custom property or snapshot

Mapped field by field · sample run · one-click rollback

## What moves from Salesforce Service Cloud to HubSpot Service Hub?

Moving from Salesforce Service Cloud to HubSpot Service Hub requires resolving a fundamentally different case data model.

Read the full summary

Salesforce treats Cases as the top of an object graph that includes Entitlements, Milestones, Case Comments, and a full audit trail; HubSpot Service Hub represents the same concept as a Ticket with conversation threads and custom properties. We handle the Case-to-Ticket mapping, translate Entitlement SLA terms into HubSpot custom properties or a custom SLA object available on Professional and above, and preserve Case milestone timestamps as a custom field on each Ticket. Salesforce Flow automations and entitlement processes do not migrate; we deliver a written inventory of every active Flow and automation for the customer's HubSpot admin to rebuild. We extract from Salesforce via Bulk API under the org's daily request limit, using parallel date-range splits to avoid REQUEST\_LIMIT\_EXCEEDED failures on high-volume orgs, and load into HubSpot via the Tickets, Contacts, and Companies APIs with batch chunking and parent-record resolution.

1:1

### Case → Ticket

Salesforce Cases map directly to HubSpot Tickets.

How it maps

CaseNumber becomes Ticket ID for cross-reference; Subject maps to Ticket subject; Status maps to Ticket status (New, Open, Pending, Solved, Closed); Priority maps to Ticket priority (Low, Medium, High, Urgent); Origin maps to a HubSpot dropdown property. Record Type maps to a Ticket pipeline only if multiple pipelines are configured in HubSpot. Parent Case and Case parent lookup to Contact and Account are resolved at migration time via the Contact and Account import.

1:1

### Contact → Contact

Salesforce Contacts map to HubSpot Contacts with email as the dedupe key.

How it maps

FirstName, LastName, Email, Phone, Title, and Department migrate directly. The Contact-to-Account relationship in Salesforce maps to HubSpot's primary Company association on the Contact record. Multi-address contacts require field-level mapping of MailingStreet, MailingCity, MailingState, MailingPostalCode, MailingCountry to HubSpot address properties.

1:1

### Account → Company

Salesforce Accounts map to HubSpot Companies.

How it maps

Account Name becomes Company name; Website becomes the Company domain for HubSpot's company detection logic. Industry, Type, and BillingAddress map to equivalent HubSpot Company properties. Parent Account hierarchies in Salesforce flatten to HubSpot's simple Company record with a custom parent\_company\_\_c field if hierarchy depth is required by the customer's reporting.

1:1

### Case Comment → Ticket conversation thread

Case Comments (public and private, distinguished by IsPublished flag) map to HubSpot Ticket conversation entries.

How it maps

Public comments become visible ticket replies; private comments are added as internal notes in HubSpot if the customer's workflow requires them. Rich-text formatting is sanitized to plain text or HTML depending on HubSpot's rendering support at the time of migration. CreatedDate and CreatedById on each comment are preserved as the conversation timestamp and author.

configuration

### Case History → Custom property or snapshot

Case History tracks field-level changes on the Salesforce Case record.

How it maps

HubSpot Tickets do not have a native audit trail equivalent in the free or Starter tiers. We offer selective migration of Case History as a custom multi-line text property on the Ticket (e.g., status\_change\_log\_\_c) capturing the most recent 10-20 status and priority changes with timestamps. Full field-level audit trail requires HubSpot Service Hub Enterprise with the audit log add-on.

configuration

### Case Team Member → Ticket Team Member or custom property

Salesforce Case Team Members assign roles (e.g., Escalation Agent, Tier-2 Support) to individual Users on specific Cases.

How it maps

HubSpot has no native case team concept on Starter or Professional. On Service Hub Enterprise, HubSpot's Teams feature can be used to associate multiple agents with a Ticket. We map team roles to HubSpot Teams (if Enterprise) or to a custom multi-checkbox property on the Ticket listing assigned agents and their roles.

******What moves 15 objects

Salesforce Service Cloud HubSpot Service Hub

- Case Ticket 1:1
- Contact Contact 1:1
- Account Company 1:1
- Case Comment Ticket conversation thread 1:1
- Case History Custom property or snapshot transformed
- Case Team Member Ticket Team Member or custom property transformed

\+ 9 more in the mapping below

## How Salesforce Service Cloud and HubSpot Service Hub 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.

| Dimension                    | Salesforce Service Cloud                                                                 | HubSpot Service Hub                                                                                       |
| ---------------------------- | ---------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Primary ticket object        | Case with multi-object graph (Comments, History, Milestones, Entitlements)               | Ticket with conversation threads and optional Knowledge Base link                                         |
| SLA and entitlement tracking | Entitlement and Milestone objects with breach-time Remaining tracking, all tiers         | Custom SLA properties on Professional and above; no native milestone Remaining field                      |
| Custom objects               | Available from Professional tier ($175/user/mo) without additional setup fees            | Custom objects require Service Hub Professional ($90/seat/mo) or above; no Enterprise gate                |
| Automation model             | Salesforce Flow (record-triggered, scheduled, screen) plus Apex triggers                 | HubSpot Workflows (property-triggered) and Sequences (time-based cadences)                                |
| Omnichannel routing          | Omnichannel digital channels, Facebook Messenger, WhatsApp via Digital Engagement add-on | Conversational Bots and live chat available from Professional; messaging channels on Enterprise           |
| Case team roles              | Case Team Members with role assignment at the individual case level                      | No native case team concept; roles represented via custom Ticket properties or Teams on Enterprise        |
| Knowledge base               | Salesforce Knowledge with versioned articles, categories, and article-case linking       | HubSpot Knowledge Base with articles, categories, and article-to-ticket linking on Professional and above |

## What to watch for in a Salesforce Service Cloud to HubSpot Service Hub migration

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

high

### Entitlement and Milestone data requires deliberate translation design

Salesforce's Entitlement and Case Milestone objects model SLA breach tracking with time Remaining (in minutes) and CompletionDate tied to BusinessHours.

How we handle it

HubSpot Service Hub has no native equivalent on Starter and no automatic Remaining calculation on any tier. We translate Entitlement terms into custom numeric fields on Tickets (sla\_first\_response\_hours\_\_c, sla\_resolution\_hours\_\_c) but the automatic countdown timer that Salesforce provides does not exist in HubSpot. If the customer relies on milestone breach alerts or automatic escalation triggered by time-remaining thresholds, those automations must be rebuilt in HubSpot Workflows or require a third-party SLA add-on. This gap is discovered late in migrations where SLA compliance reporting was central to the Salesforce instance, so we flag it during scoping.

high

### Case History audit trail cannot be fully replicated in HubSpot Starter

Salesforce's Case History object captures every field-level change on a Case with old value, new value, field name, and timestamp.

How we handle it

HubSpot Tickets have no native equivalent audit trail in Starter or Professional tiers. We offer selective Case History migration as a snapshot property on the Ticket capturing the last N status and priority transitions, but a full field-by-field change log is not structurally supported. Customers with compliance requirements for audit-level change tracking need Service Hub Enterprise with the audit log add-on or a third-party compliance tool, which we identify during scoping before migration begins.

high

### Salesforce Flow automations do not migrate to HubSpot Workflows

Salesforce Flows (record-triggered, scheduled, and screen variants) and Apex triggers responding to Case events do not have a migration path to HubSpot.

How we handle it

HubSpot Workflows use a different trigger model (property-change and enrollment-based rather than record-event-based), and HubSpot does not have an equivalent to Apex triggers. We deliver a written inventory of every active Salesforce Flow and trigger affecting the Case object — with trigger object, entry condition, action, and recommended HubSpot Workflow equivalent — for the customer's HubSpot admin to rebuild post-migration. Entitlement processes and Omni-Channel routing configurations are documented separately and are not migrated as functional equivalents.

medium

### Picklist dependency translation can silently corrupt case data

Salesforce enforces dependent picklists (e.g., Country gates State values, Case Type gates Case Reason) that are not enforced in HubSpot.

How we handle it

When migrating picklist values from Salesforce to HubSpot dropdown properties, unmapped values either get added to HubSpot's dropdown or force a value-mapping decision (map to nearest equivalent or skip). We generate a picklist value translation table before any records load and resolve every Salesforce picklist (Status, Priority, Origin, Type, Reason, Account Role) against HubSpot's dropdown structure. Records with invalid combinations after translation are held in a reconciliation queue rather than loaded silently.

medium

### Salesforce Bulk API daily limits constrain large-volume migration windows

Salesforce Enterprise Edition grants 100,000 API requests per 24-hour rolling window; Unlimited and Einstein 1 grant higher limits.

How we handle it

Active integrations (Outlook sync, custom REST endpoints, other CRM connectors) consume headroom before migration extractions begin. When extracting millions of Case, Contact, Case Comment, and Email Message records, we split exports by date range or record type and schedule passes during off-peak hours. We audit API consumption during scoping and surface the risk of REQUEST\_LIMIT\_EXCEEDED failures before production extraction to avoid partial exports that silently truncate the migration scope.

## How the migration runs

1. ### Discovery and scoping

   We audit the source Salesforce org across license edition, Case record count, active Case Comment and Email Message volumes, Entitlement and Milestone configuration, picklist values on Status, Priority, Origin, and Type, active Salesforce Flows and triggers affecting Cases, and any custom objects linked to Cases via lookup.

   What this step covers

   We pair this with a HubSpot Service Hub tier review to confirm whether the destination supports the required features (custom objects, Knowledge Base, Teams, SLA properties). The discovery output is a written migration scope document with record counts, object list, and a HubSpot tier recommendation if the customer has not yet provisioned the destination account.

2. ### Schema design and Entitlement translation plan

   We design the HubSpot destination schema: Ticket pipelines and statuses mapped from Salesforce Case Record Types and Status values, custom SLA fields mapped from Salesforce Entitlement and Milestone records, picklist translation tables for all Salesforce dropdown fields, and Knowledge Base category structure mapped from Salesforce article categories.

   What this step covers

   If the customer requires a custom SLA object (multiple milestone types per case), we pre-create the schema in HubSpot including all custom properties and their types before any data import. Schema validation happens in the customer's HubSpot sandbox or trial before production.

3. ### Sandbox migration and reconciliation

   We run a full migration into the production HubSpot account using a representative sample (first 500-1,000 records per object type) to validate the mapping.

   What this step covers

   The customer's service desk manager or RevOps lead reviews 25-50 random Tickets against the Salesforce source records, checks SLA field values, confirms Knowledge Base article visibility, and validates that Case Comment threads render correctly in HubSpot. Any mapping corrections (picklist values, Entitlement translation, field type mismatches) happen in this phase. The customer signs off the sandbox validation before production migration begins.

4. ### User provisioning and Owner reconciliation

   We extract every distinct Salesforce Owner (agent) referenced on Cases, Case Comments, and Email Messages and match by email against the HubSpot destination account's User list.

   What this step covers

   Agents without HubSpot accounts go to a reconciliation queue. The customer's HubSpot admin provisions any missing users before production migration because OwnerId references on Tickets must be satisfied at import time. If the customer uses Salesforce Case Teams, we confirm the HubSpot tier (Enterprise required for native Teams) and design the agent-to-Team mapping accordingly.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Companies (from Salesforce Accounts), Contacts (with Company association resolved), Products and Pricebook entries (if linked to Cases), Knowledge Base articles (if migrating Solutions as KB articles), Tickets (with custom SLA fields resolved), Case Comments (as ticket conversation entries linked to parent Ticket), Email Messages (as ticket emails), Case Team Members (as Teams or custom agent properties on Tickets), and Custom Objects (last, because they often have lookups to Tickets, Contacts, or Companies).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. Bulk API extraction from Salesforce uses parallel date-range splits to stay within the org's daily request limit.

6. ### Cutover, delta sync, and Flow rebuild handoff

   We freeze Salesforce writes during the cutover window, run a final delta migration of any Cases, Comments, or Email Messages modified during the migration window, then designate HubSpot Service Hub as the system of record.

   What this step covers

   We deliver the Flow and automation inventory document to the customer's HubSpot admin, including every active Salesforce Flow and trigger, the Case object events it responds to, and a recommended HubSpot Workflow equivalent. We support a one-week hypercare window where we resolve any Ticket-to-Case reconciliation issues surfaced by the service team. We do not rebuild Salesforce Flows as HubSpot Workflows within the migration scope; that is a separate engagement or an internal admin task.

![](https://flitstack.ai/platforms/salesforce-service-cloud.svg) Salesforce Service Cloud ![](https://flitstack.ai/platforms/hubspot-service-hub.svg) HubSpot Service Hub

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Service Hub Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**4-8 weeks** Typical, smaller accounts

**8-16 weeks** Large or heavily customised accounts

A quote scales with record volume, custom object complexity, and whether Entitlement and Milestone data require translation into HubSpot custom fields or a custom SLA object. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Salesforce Service Cloud to HubSpot Service Hub →](https://flitstack.ai/contact)

## Why teams move from Salesforce Service Cloud to HubSpot Service Hub

- Salesforce Service Cloud annual costs compound 30-40% above sticker price when storage overages ($125/GB), Agentforce conversation charges ($2/conversation), and 8-10% annual contract uplifts are included. Mid-market teams with 10-30 service agents cite this gap as the trigger for evaluating HubSpot Service Hub at $45-$90/seat/month flat tiers, where the total cost of ownership is predictable and transparent.
- Agent adoption on Salesforce Service Cloud is consistently lower than on HubSpot in Capterra and G2 reviews. Reviewers describe the Salesforce interface as unintuitive for non-power-users, requiring consultant time for admin tasks that should be self-service. HubSpot's onboarding is cited as faster for support teams without a dedicated Salesforce admin, reducing the time-to-first-resolved-ticket after platform switch.
- Salesforce's picklist-heavy data model (Case Origin, Status, Priority, Type, Reason, Account Role) requires explicit translation during any outbound migration. Teams migrating to HubSpot discover that their picklist-heavy workflows need simplification in HubSpot's dropdown model, which many reviewers treat as a forcing function to clean up Salesforce configuration debt rather than a blocker.
- HubSpot's integrated CRM model places customer service data on the same Contact and Company records used by sales and marketing without a sync layer. For teams with HubSpot Marketing Hub already in place, adding Service Hub creates a unified timeline of marketing touchpoints, sales interactions, and support cases on one record, which G2 reviewers cite as a structural advantage over the siloed Service Cloud model.
- Enterprise teams with complex Salesforce entitlement processes (SLA with multiple Milestone types, Entitlement Processes per Account, and breach-time tracking) discover that HubSpot's SLA capabilities require either custom fields or a custom SLA object available on Professional and above. This migration gap forces a deliberate SLA design decision that many teams treat as a benefit — a chance to simplify entitlement tracking that Salesforce allowed to grow unnecessarily complex.

Questions, answered

## Salesforce Service Cloud to HubSpot Service Hub migration questions

How long does a Salesforce Service Cloud to HubSpot Service Hub migration take?

Most migrations land between four and eight weeks for accounts under 5,000 Cases with no custom objects, no Entitlement translation, and no Knowledge Base migration. Migrations with Entitlement and Milestone translation, Case History snapshot requirements, large Case Comment and Email Message volumes (over 200,000 records), or active Salesforce-to-HubSpot bidirectional sync in place move to eight to sixteen weeks because of picklist dependency review, custom SLA schema design, and Bulk API extraction scheduling under rate-limit constraints.

Do Salesforce Flows, Entitlements, and Milestones migrate to HubSpot?

No. Salesforce Flows and Apex triggers are code-based automations with no migration path to HubSpot Workflows, which use a different trigger and action model. Entitlement and Milestone objects have no native HubSpot equivalent on Starter or Professional tiers; we translate them into custom SLA fields on Tickets during migration but the automatic breach-time Remaining calculation and milestone escalation triggers do not transfer. We deliver a written inventory of every active Flow, trigger, Entitlement process, and Milestone type requiring rebuild in HubSpot. Automations are rebuilt by the customer's HubSpot admin or a HubSpot partner post-migration as a separate scope.

Do we lose historical Case data and engagement history?

No. We migrate the full Case record including Subject, Status, Priority, Origin, Description, and all standard fields. Case Comments migrate as Ticket conversation entries preserving author and timestamp. Email Messages migrate as Ticket emails with subject, body, FromAddress, and ToAddress. Case History migrates as a snapshot property on the Ticket (capturing the last 10-20 status and priority transitions) rather than a field-by-field audit log, unless the customer has Service Hub Enterprise with the audit log add-on. Milestone timestamps migrate as custom fields on the Ticket. Knowledge Articles migrate as HubSpot Knowledge Base articles with categories and article-to-ticket linking preserved.

Which HubSpot Service Hub tier do we need for this migration?

Service Hub Starter ($45/seat/month) supports Tickets, basic reporting, and email-to-ticket but lacks custom objects, Knowledge Base, Teams, and SLA properties. Service Hub Professional ($90/seat/month) adds custom objects, Knowledge Base, and SLA properties on Tickets. Service Hub Enterprise ($180/seat/month) adds Teams, advanced reporting, and audit logging. We recommend Professional minimum for migrations with Entitlement data or Knowledge Base articles; Enterprise if Case Teams or full audit trail migration is required. We identify the required tier during scoping based on the customer's Salesforce schema.

Can we run HubSpot Service Hub alongside Salesforce Service Cloud during migration?

Yes. A common pattern is a parallel-run window where Salesforce remains the system of record for open Cases while HubSpot Service Hub is provisioned, migrated, and validated. During this window, new Cases created in Salesforce continue to be worked; on cutover day we run a final delta migration into HubSpot and switch agent login to HubSpot as the system of record. We do not recommend a bidirectional sync between Salesforce Service Cloud and HubSpot Service Hub as a long-term architecture because no native sync exists between these two platforms and a third-party middleware layer introduces latency and data consistency risk.

Does FlitStack AI migrate Salesforce custom objects to HubSpot custom objects?

Yes. Salesforce custom objects (with \_\_c API names) linked to Cases migrate to HubSpot custom objects of equivalent name, provided the destination account has Service Hub Professional or above. We pre-create the HubSpot custom object schema including all custom properties, lookup relationships, and required-field configuration before any data import. Custom object import runs last in the migration sequence because destination records (Contacts, Companies, Tickets) must exist to satisfy lookup references. The customer chooses whether each Salesforce custom object becomes a standalone HubSpot custom object or whether its data is merged into the Ticket record as properties.

What happens to our Salesforce integrations during migration?

During migration we schedule Salesforce API extractions during off-peak hours to minimize impact on active integrations (Outlook sync, telephony connectors, other CRM connectors). We do not migrate integrations as part of the migration scope; the customer provisions equivalent HubSpot integrations post-migration. Common replacement patterns include HubSpot's native Outlook and Gmail integrations (replacing Einstein Activity Capture), HubSpot Conversations inbox (replacing Salesforce Omni-Channel routing for chat and email), and HubSpot calling features (replacing Salesforce Open CTI or browser-based telephony). We provide a written integration inventory of every active Salesforce integration as a reference for the rebuild.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot-service-hub.webp) Migrate to **HubSpot Service Hub** Every source we move into HubSpot Service Hub, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/helpdesk/hubspot-service-hub)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot Service Hub and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Zendesk to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/hubspot-service-hub) [**Intercom to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/intercom/to/hubspot-service-hub) [**Freshdesk to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshdesk/to/hubspot-service-hub) [**Salesforce Service Cloud to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/freshdesk) [**Salesforce Service Cloud to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/salesforce-service-cloud/to/intercom)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Batch limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/batch-limits)
3. [Batch read associations — HubSpot Knowledge Base](https://knowledge.hubspot.com/crm-setup/batch-read-associations)
4. [Import knowledge base articles — HubSpot Knowledge Base](https://knowledge.hubspot.com/knowledge-base/import-knowledge-base-articles)
5. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
6. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
7. [Sandboxes — Staging Environments for Customizing and Testing](https://help.salesforce.com/s/articleView?id=platform.deploy_sandboxes_parent.htm)

Get a quote

## Moving from Salesforce Service Cloud to HubSpot Service Hub?

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

[Get a quote](https://flitstack.ai/contact)
