Skip to content
Get a quote

Migrate to HubSpot Service Hub

HubSpot Service Hub is the helpdesk inside HubSpot's Smart CRM — a migration target where Tickets, Conversations Inbox and Knowledge Base have to be staged before the first row lands, and where SLAs, macros and feedback survey history all need rebuild work that the import tool will not do for you.

Short answer

FlitStack AI migrates tickets, threads, and customer histories into HubSpot Service Hub from 250+ helpdesks, including Salesforce Service Cloud, Zendesk, Intercom, Freshdesk. Every field is mapped to HubSpot Service Hub's objects, history and associations come across, the HubSpot Service Hub setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationHubSpot Service Hub
Salesforce Service CloudZendeskIntercomFreshdesk
250+ sources mapped into HubSpot Service Hub

Systems we move into HubSpot Service Hub

The helpdesks teams most often move from. Each page shows what moves, the field mapping and what to watch for.

What HubSpot Service Hub supports, and where its import tools stop

  • Unified CRM context means every support ticket links directly to the Contact and Company record without a separate integration
  • Free tier provides unlimited support seat access with basic ticketing and a shared inbox for small teams to validate fit before committing
  • Omnichannel routing consolidates email, live chat, Facebook Messenger, WhatsApp, and Instagram DM into one queue
  • Built-in customer success workspace gives health scores and portfolio views that other standalone helpdesks cannot match
Bulk APIOAuth 2.0 with Private App tokens
Rate limits100–190 req/10sec (per app, varies by tier); 250,000–1,000,000 req/day (shared across all apps in account)
ObjectSupportNote
TicketsfullTickets are HubSpot's primary support object. We map them 1:1 with standard fields (subject, status, priority, source) and preserve all custom ticket properties. For Zendesk migrations, we reconstruct the ticket structure but acknowledge that side conversations require manual re-creation or a custom workaround in HubSpot.
ContactsfullContacts map directly across platforms. Standard properties (name, email, phone, lifecycle stage) migrate cleanly. We flag any custom contact properties that need mapping to destination field names and warn if the destination uses a different lifecycle stage taxonomy.
CompaniesfullCompanies are a standard HubSpot CRM object shared across all hubs. We map company properties and associations to contacts. If the destination CRM uses a different account hierarchy model, we flatten or restructure accordingly during migration.
Conversations (Engagements)mappedHubSpot stores individual email, chat, and call events as separate engagement objects linked to tickets. We reconstruct these into threaded conversations for most destinations, but the association metadata may not survive the translation intact. We flag this during scoping so customers can decide whether to include partial history.
Knowledge Base ArticlesmappedArticles can be exported via API and migrated to alternatives like Zendesk Guide or Intercom Articles. We handle the article body, category structure, and publish status. HubSpot-specific features like article performance analytics do not have equivalents in most destination platforms.
Customer Health ScoresmappedHubSpot CS Hub provides health score calculations based on engagement data. We migrate the raw engagement data but cannot guarantee that health score algorithms will produce identical results in the destination system. We recommend re-running health score calculations post-migration.
Custom ObjectsmappedCustom Objects are only available on Enterprise tier. If you are migrating from a lower HubSpot tier that did not use Custom Objects, this is not a concern. For Enterprise-to-Enterprise migrations, we map custom object records and their associations, though schema differences must be resolved during field mapping.
Pipelines (Ticket Pipelines)mappedTicket pipelines and their stages migrate as a configuration artifact. We extract the pipeline name, stage names, display order, and probability percentages. If the destination has fewer stage slots, we consolidate and warn which stages were merged.
Owners (Agents/Users)fullHubSpot users and owners map directly. We migrate user records including name, email, role, and team assignments. Active versus inactive status is preserved. If two-factor auth is required by the destination, we flag this as a pre-migration step for the customer.
TagsmappedTags on tickets and contacts migrate as string values. HubSpot does not enforce a global tag taxonomy, so tags from multiple sources may have naming collisions. We deduplicate and prefix where necessary to avoid silent data loss.
AttachmentsmappedFile attachments on tickets and emails can be exported via HubSpot's API. We migrate them to the destination as file references or attachments. Large attachment volumes affect migration speed and may require chunked processing to stay within rate limits.
Feedback Surveys (CSAT)mappedPost-conversation survey responses are stored as a HubSpot object linked to tickets. We map response scores and free-text answers. The destination platform must support CSAT data to preserve this, otherwise we export it as a report CSV.

The HubSpot Service Hub migration guide

Why teams migrate to HubSpot Service Hub

The four shapes a Service Hub migration takes, and what makes the helpdesk easier — or harder — than the category average.

HubSpot, Inc. was founded by Brian Halligan and Dharmesh Shah in 2006 and is headquartered in Cambridge, Massachusetts1. Service Hub is the customer-service product inside a broader suite that also includes Sales Hub, Marketing Hub, Content Hub and Data Hub, all sharing the same underlying Smart CRM.

The helpdesk experience is split across two surfaces: the Conversations Inbox for unified email/chat/social threads, and the Help Desk workspace — a ticket-centric UI launched in 2024 to give agents the queues, filters and SLA timers that legacy users expected from Zendesk-style tools.

The typical Service Hub customer is a 10 to 200-seat support team already standardised on HubSpot for sales or marketing, or a B2B SaaS support org consolidating away from a standalone helpdesk. Compared with Zendesk and Freshdesk, Service Hub positions on tighter integration with Contacts, Companies and Deals — a shared graph that means an agent sees deal context on every ticket. Compared with Intercom, it positions on lower per-seat pricing on Professional and a more mature ticketing primitive9.

The shapes of migration that actually land on Service Hub fall into four patterns. First, consolidation projects: a company replacing Zendesk plus a separate live-chat tool with Service Hub's unified Conversations Inbox and Help Desk workspace. Second, Zendesk exits, driven by per-seat price pressure and a desire to use one CRM for sales and support.

Third, legacy replacements — Freshdesk, Help Scout, Kayako, Groove, or a shared inbox like Gmail — where the source schema is loose and the project is really a re-architecture. Fourth, add-on rollouts inside existing HubSpot accounts that already run Sales or Marketing Hub and are now activating Service Hub on top of the same portal.

What makes migrating to Service Hub easier than the category average is that Tickets are a first-class CRM object — they share the import tool, the property model and the association engine used by every other Hub. CSV and Excel uploads handle multi-object files via cross-reference columns, and tier-scaled file and row limits run up to 512 MB and 10 million rows per day on paid plans2.

What makes it harder than the average is the helpdesk-specific layer that sits on top of the generic CRM. HubSpot does not allow migrating ticket Created at, Updated at or Closed at dates — they re-stamp to import day, which breaks every SLA report you built in the source.

Conversations as a separate object cannot be backfilled with the same fidelity as Notes. Macros, triggers, SLA policies and feedback survey rules do not import at all — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

Tickets are a CRM object you can import. The Conversations Inbox, macros, SLAs and CSAT history are not — they are rebuild work, and the scope of that rebuild is the whole project.

The HubSpot Service Hub data model you need to map into

Tickets, Conversations, Pipelines and Knowledge Base articles — the destination schema decoded for support migrations.

HubSpot's Smart CRM is built around a small set of standard objects, each with default and custom properties, and associations that connect them. Service Hub does not introduce its own database — it adds object access and behaviour (ticket pipelines, SLAs, knowledge-base authoring, the Help Desk workspace) on top of the same shared schema used by Sales and Marketing Hubs.

Before you can map a field on the source side, you need to know exactly which destination object the row belongs on, what properties it requires, and which value will serve as its upsert key. The table below summarises the objects you will touch in a Service Hub migration.

ObjectWhat it storesRequiredTier
TicketsSupport cases — the spine of the helpdeskTicket name, pipeline, ticket statusAll tiers; full tooling on Service Hub Starter+
Conversations (inbox threads)Email/chat/social threads, the messages and repliesConversation source, contact, channelConversations Inbox on all tiers; routing on Pro+
ContactsIndividual people — requesters, end usersOne of: email, first name, last nameAll tiers
CompaniesOrganisations associated with contacts and ticketsName or domainAll tiers
Knowledge Base articlesHelp-centre content — categories, sections, articlesTitle, body, meta description; CSV importService Hub Professional, Enterprise14
Feedback submissionsCSAT, NPS and CES survey responsesSurvey type, contact, score, submitted dateService Hub Professional, Enterprise9
Activities (notes, emails, calls, meetings, tasks)Engagement timeline events on tickets and contactsType, timestamp, ownerAll tiers; bulk import limits per tier
Custom ObjectsCustomer-defined record types (e.g. Assets, Subscriptions)Schema defined first; per-property requirementsEnterprise

Tickets do not have a natural unique key, so plan to either let HubSpot assign Record IDs and store them back in the source, or create a custom single-line text property, mark it Require unique values for this property, and use it as your external ID. Once a property is created you cannot retroactively make it unique — plan for this on day one.

Contacts use email as the default unique identifier — two rows with the same email collapse into one record on import2. Companies use company domain name. Knowledge Base articles import via the dedicated KB import tool and use URL slug plus category as their effective key14. Custom property types determine validation and storage; the catalogue below covers what you can model and the limits you need to plan around.

Field typeLimitNotes
Single-line text65,536 chars via CRM/importStores any alphanumeric string
Multi-line text65,536 chars via CRM/importUsed for ticket descriptions; rich-text supported in UI9
Number17 significant digitsNumeric filters: before/after/between
Date pickerMidnight UTC storedDate-only; timezone-stripped
DatetimeISO-8601 with offsetUI accepts looser formats; stricter on programmatic loaders
Single-select (enumeration)1,000 optionsInternal value differs from display label — bites every helpdesk move
Multi-select (checkbox)1,000 optionsSemicolon-delimited on import; common for ticket Tags
Calculation / scoreEnterprise for advanced; 25 calculated baselineDoes not import — rebuild as formula property9
Custom properties per objectDefault 1,000 per object; up to 3,000 via add-on$220/mo per 500-property add-on pack9

Relationships in HubSpot are modelled as associations with optional association labels (for example, a contact labelled Primary Requester on a ticket). HubSpot raised the per-record association cap to 50,000 in late 2025, but high-volume support scenarios where one company has tens of thousands of historical tickets still bump that ceiling5.

Custom Objects (Enterprise) are how teams model assets, subscriptions, devices or contracts that tickets associate to. There is no native master-detail cascade-delete: deleting a parent does not delete children, which is a behaviour you reproduce in workflows if your source platform relied on it.

Pre-migration prep — the work before you touch Service Hub

What must be true on the source, the destination, and across the support team before the first ticket hits the import tool.

The single best predictor of a clean Service Hub migration is how much work you do on the source side before the first import button is pressed. Help Desk Migration's own checklist warns that any data that fails in the demo migration will fail in the full run — pre-processing is the only place that gets cleaned.

Treat the source export as raw material that needs shaping to HubSpot's expected formats — email lowercased, ticket statuses converted to HubSpot internal values, dates rewritten to ISO-8601, agent emails resolved to HubSpot user IDs.

Any data that fails in the demo migration will fail in the full run. Pre-processing is the only place that gets cleaned.

Source-side prep

  • Decide your data horizon — how many years of ticket history you actually need. Migrating 8 years of closed Tier-1 tickets that nobody will ever reference adds cost and noise; most teams cap at 2–3 years and archive the rest.
  • Audit and dedup contacts and companies with a third-party tool like Insycle or Koalify — Service Hub inherits the CRM dedup model, and email-case-only duplicates will silently merge once they hit the importer.
  • Normalise ticket statuses and priorities — Open, Pending, Solved, Closed in your source need to be mapped to HubSpot ticket-stage internal values per pipeline. Do this in the spreadsheet, not in HubSpot afterward.
  • Stamp a stable external ID on every ticket — the source platform's case number — so re-runs and reconciliation are deterministic and so agents can search by legacy ID after cutover.
  • Inventory your macros, triggers and SLA policies — print them, classify them as rebuild, redesign or retire. Most teams find half their automations are stale and only a third are worth carrying forward.

Destination-side prep

  • Create a sandbox from Settings → Account Management → Sandboxes (Enterprise) or use a standard development account on lower tiers. Dry-run a 20-ticket sample with attachments and conversation history before you scale.
  • Provision agents first under Settings → Users and Teams → Create user, using the same email addresses as the source platform — agent identity has to match for ticket ownership to resolve.
  • Pre-create every custom ticket property with the right type — single-line text vs single-select matters, and HubSpot will not let you change a created property's type later for many combinations.
  • Build ticket pipelines and stages before importing tickets — recreate one pipeline per support queue (e.g. Tier 1, Tier 2, Billing) with the stages and SLA timers you need. Tickets that target a non-existent stage on the named pipeline are rejected.
  • Set up the Conversations Inbox and channel connections (email forwarder, chat, social) — but do not turn on the live channels until after cutover, or new messages will mix with the backfill.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours for a helpdesk, scheduled over a weekend to minimise live-ticket disruption — and communicate it across customer support, customer success and any sales reps who watch tickets. Train agents on the Help Desk workspace, ticket views, and the rebuilt macros before go-live, not after.

Import mechanisms: UI wizard, CSV, and KB importer

Multiple paths in — each with different limits and shapes. Picking the wrong one is how helpdesk migrations stall at scale.

HubSpot exposes several load paths for a Service Hub migration and the right one depends on object type and dataset size. The UI Import Tool handles Tickets, Contacts and Companies. The Knowledge Base importer is its own purpose-built tool. Third-party staging tools like Help Desk Migration sit on top of all of them and add source-platform extraction, schema translation and attachment handling.

UI Import Tool

The native import lives at Settings → Data Management → Data Integration → Import, or by clicking Import in the top right of any object index page. There are two modes: Quick Import for a single object with auto-mapped property names, and Advanced Import for full mapping control, multi-object files, and association creation. HubSpot ships a dedicated Tickets sample spreadsheet to demonstrate the expected column set16.

Limits are tier-scaled: free accounts get 20 MB files, 50 imports/day and 500,000 rows/day; Starter, Professional and Enterprise accounts get 512 MB files, 500 imports/day, 10,000,000 rows/day, and up to 1,048,576 rows per individual file2. Up to three imports run simultaneously, and only two can exceed 10,000 rows. The right call: UI for one-shot Ticket and Contact loads under 100k records, or any time you want a visual mapping review before commit.

Knowledge Base importer

Knowledge Base articles do not go through the CRM import tool. The dedicated KB importer is at Settings → Content → Knowledge Base → Current view → Import knowledge base and accepts a CSV with columns for Title, Article Body (HTML source), Meta description, Category, Subcategory, Tags (comma-separated) and Keywords14. The importer is published only on Service Hub Professional and Enterprise — teams on Starter migrate KB content by hand or via a partner tool.

Third-party staging tools

Help Desk Migration, Import2 and Suprdense's SuprSwitch are purpose-built for helpdesk-to-HubSpot moves. They handle the source-platform extraction (Zendesk, Freshdesk, Help Scout, Intercom, Jira Service Management and a long tail of others), the schema translation, the file/attachment fetch-and-attach, and the conversation threading that the generic CRM import does not handle natively. Most run a Demo Migration of 20 sample tickets before committing to the full run, and most support Delta Migration to catch records that change during the cutover window.

Mapping your helpdesk data into Service Hub

The longest section — tickets, conversation threads, KB articles, macros and SLA rebuild, CSAT history, and the multi-channel inbox.

Mapping is where every helpdesk migration earns its scars. The schema decisions you make determine whether SLA reports work on day two, whether macros fire on day five, and whether your agents trust the queue on day thirty.

Work object by object, top to bottom of the import order: Companies first (so contacts and tickets can associate to them), then Contacts, then Tickets, then Conversations and Activities, then Knowledge Base articles, then Feedback submissions and Custom Objects.

Contacts and Companies

Common source → HubSpot Contact mapping
SourceDestinationNote
requester emailemail (unique identifier)Lowercased on import; upsert key by default
requester namefirstname / lastnameIf only full name is available, split before import; missing name backfills as 'Empty'
organisation / accountCompany association via domainHubSpot strips http(s):// and www. on match
phonephoneNormalise to E.164 before import
language preferencehs_language (or custom)Drives KB language routing; map ISO-639 codes
marketing opt-in flagMarketing contact statusDrives billing — leave support-only contacts as non-marketing

Tickets and pipelines

Recreate every pipeline and every ticket stage in HubSpot before importing tickets. The Help Desk Migration tool defaults all tickets into a single pipeline — if you need source groups mapped to different HubSpot pipelines, that is custom work. Each ticket stage has an internal value (commonly 1, 2, 3, 4 for New, Waiting on contact, Waiting on us, Closed) which you reference in the import file, not the display label.

Common source → HubSpot Ticket mapping
SourceDestinationNote
subject / summarysubject (ticket name)Required field on every ticket row
statushs_pipeline_stageUse internal value, not label — closed is internal, Closed is label
priorityhs_ticket_priorityMap to LOW / MEDIUM / HIGH / URGENT internal values
category / typehs_ticket_category or customSingle-select; map source values to internal options
source channelsource_typeEMAIL, CHAT, FORM, PHONE, CHATFLOW etc.
assignee / agenthubspot_owner_idMap by user email; pre-provision agents
requesterContact associationSet via cross-reference column using contact email
organisationCompany associationUse company domain or Record ID
case number / legacy IDCustom unique-text propertyMark Require unique values; preserves legacy lookups
created_at / closed_atCustom datetime propertiescreatedate cannot be overridden — see audit-trail section

Ticket history and conversation threading

This is where source platforms differ most and where the cleanest migrations spend the most planning time. Zendesk stores ticket history across CaseComment (public/internal comments), EmailMessage (email threads), CaseHistory (field-change audit) and FeedItem (Chatter-style posts). Salesforce Service Cloud uses the same pattern with different object names. HubSpot Service Hub uses a flatter model — every ticket has a timeline populated by Notes, Emails, Calls, Tasks and Meetings, all associated as engagements, plus Conversations objects for the threaded inbox view.

The practical pattern: split source comments into three buckets — public-facing replies map to Emails (engagement type EMAIL), internal comments map to Notes (hs_note_body with the comment text and hs_timestamp preserving the original date), and field-change audit history is captured into a custom Ticket History (Legacy) multi-line text property because HubSpot has no native per-field audit log on tickets.

Conversations Inbox and multi-channel routing

The Conversations Inbox is HubSpot's unified channel object — email, chat, Facebook Messenger, WhatsApp, calls and form submissions land here as conversation threads before (or alongside) becoming tickets. Conversations themselves are not imported with the same fidelity as Tickets. Most teams map source channel threads to a Ticket with the conversation body captured as Email engagements, leaving the live Conversations Inbox to backfill forward from cutover day.

Channel connectors (email forwarder, Facebook, WhatsApp, calling) are set up after the historical import — under Inbox & Help Desk settings — and the routing rules that send conversations to inboxes or agents are configured live, not migrated.

Knowledge Base articles, categories and translations

Knowledge Base content has its own importer at Settings → Content → Knowledge Base14. The CSV columns are URL slug, Title, Subtitle, Category (required), Subcategory, Tags (comma-separated, no spaces after the comma or the import errors), Keywords, Meta description (required) and Article Body (HTML source — required)14. Images inside articles must be referenced by URL — HubSpot does not bulk-upload binary images during KB import.

Multi-language support is handled by uploading each language as a separate import and linking translations via the article's language variant settings. Each article has a 100-tag ceiling on the new KB editor — articles with more need pruning before import17. Service Hub Enterprise allows multiple knowledge bases; Pro is capped at one.

Macros, triggers, workflows and SLA rebuild

None of these import. Zendesk Triggers, Freshdesk Automations and Help Scout Workflows are all rebuilt as HubSpot Workflows under Automations → Workflows after the data is loaded. Macros (the canned-response style) become Snippets or Templates in HubSpot. SLA policies become SLA configurations on the ticket pipeline under Service settings — they cannot be backfilled with historical SLA breach data, so any historical SLA report stops at cutover day.

The judgment call most teams underestimate: not every source automation is worth rebuilding. Print the trigger/macro inventory, classify each as rebuild, redesign or retire. Teams routinely discover half their macros are stale and only a third merit the work.

CSAT, NPS and CES survey history

Feedback surveys are a Service Hub Pro/Enterprise feature. Historical survey scores from a source platform are imported as Feedback submission records associated to the contact and (where possible) the ticket, with the score in a numeric property, the survey type (CSAT/NPS/CES), the response text in a multi-line text property, and the submitted date preserved in a custom datetime property. The live survey machinery — embedded survey emails, the in-product CSAT prompt, the NPS schedule — is configured live in HubSpot, not migrated.

Files and attachments

Attachments do not import in bulk via the CSV UI flow. The supported path is to upload each binary into the HubSpot Files tool and attach it to a Note that is then associated with the ticket. Specialist helpdesk migration tools automate this loop, including the option to convert inline images in source ticket bodies into proper attachments. Customer Portal attachments are capped at 50 MB; one-to-one email attachments at 20 MB8.

Audit trail, ownership and original timestamps

Standard createdate, hs_object_id, hs_createdate and hs_lastmodifieddate are HubSpot-managed system properties — they cannot be overwritten during import. For tickets specifically, HubSpot does not allow migrating ticket Created at, Updated at, or Closed at dates to Service Hub. That means SLA dashboards filtered on those system fields will treat every imported ticket as created on import day.

The pattern: create three custom properties per ticket — Legacy Created Date, Legacy Closed Date, Legacy Updated Date — populate them from the source export, and rewrite every historical-period support report to filter on the legacy fields. Owner assignment during import works only if the agent email exists at the moment of import; rows whose owner cannot be resolved are imported with no owner set, which silently breaks downstream owner-based routing.

The pitfalls that derail Service Hub migrations

Eight specific failure modes — ranked by impact, each tied to the exact HubSpot mechanism that breaks.

Validation and cutover

What to verify after the ticket import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and agents being allowed in. The Help Desk Migration playbook recommends a three-stage validation: a Demo Migration of 20 tickets and 20 articles with stakeholder spot-checks, the full load with real-time monitoring of record counts and attachment integrity, and a 30-day post-migration data-quality audit. The most reliable signal is having support team leads verify their own queues — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before agents get login access.

  • Total tickets imported per pipeline per stage vs source — and a date-bucketed comparison against Legacy Created Date to confirm the historical distribution survived.
  • Total contacts and companies vs source — checking that domain-based collapse did not over-merge support requesters who use the same generic vendor email.
  • Total ticket comments and emails per ticket — sampling 100 random tickets and counting Notes + Emails on the HubSpot timeline against the source thread length.
  • Attachments — download a sample of attachments from imported tickets and confirm the binaries match the source, particularly for inline images that the migrator converted to attachments.
  • Associations per object type — count ticket→contact, ticket→company and ticket→deal associations and compare against the source-derived expected counts.
  • Agent ownership distribution — GROUP BY hubspot_owner_id and confirm no ticket landed unowned that should not have, and that deactivated source agents were reassigned.
  • Knowledge Base — count articles per category, count translations per article, and verify the meta description, URL slug and tags imported cleanly on a 30-article sample.

On top of reconciliation, run a manual spot-check protocol: pick 30 random tickets across age and priority, and verify each field against the source UI. Pick five high-touch tickets with long conversation threads and trace the full timeline. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected tickets by external ID.

HubSpot ships Restore CRM Properties and Records, which captures the last 20 versions of every property change (45 for contacts) and lets super admins undo changes from the last 14 days via Settings → Data Management → Backup and Restore. This is the closest thing to a native undo, but it is not a bulk-rollback button — it works property-by-property.

The real rollback strategy: export everything to S3 before the import starts, stamp every imported ticket with an Import Batch ID custom property, and if catastrophe strikes, bulk-delete by that batch ID and re-import from the cleaned source.

Cutover sequencing: (1) source helpdesk goes read-only; (2) final delta export captures every ticket that changed during the test-import window — most specialist tools support Delta Migration explicitly; (3) delta is imported; (4) reconciliation runs; (5) channels are switched (email forwarder, chat widget, social) so new conversations land in HubSpot; (6) agents get login access and a 48-hour hyper-care window; (7) source decommission is scheduled 30 to 90 days out.

Migration partners and tools

Solutions Partners, helpdesk-specific migration vendors, and managed services — what each is good for and how to choose.

The HubSpot Solutions Partner Program tiers Elite, Diamond, Platinum and Gold partners by certifications, customer count and revenue. For Service Hub migrations specifically, partners with explicit Zendesk-to-HubSpot, Freshdesk-to-HubSpot or Help Scout-to-HubSpot practices tend to ship cleaner than generalist implementation shops. Origin 63, Incremental, Impulse Creative, SmartBug Media and Infinite Renewals are commonly named on the helpdesk side of the partner directory.

HubSpot itself charges a one-time onboarding fee — $1,500 on Service Hub Professional and higher amounts on Enterprise9 — and some partners waive that fee in exchange for the implementation contract.

For self-service automated tooling, Help Desk Migration is the most widely cited specialist — it supports 30+ source helpdesks, runs a free Demo Migration, is SOC 2 Type II and GDPR-aligned, and prices by record count plus options. Import2 offers a similar one-click model with a money-back guarantee. Suprdense's SuprSwitch focuses on HubSpot-to-HubSpot and helpdesk-to-HubSpot moves with intelligent mapping.

On the ETL and iPaaS side, Fivetran, Airbyte, Workato and MuleSoft have HubSpot connectors. Their role in a helpdesk migration is rarely the migration itself — it is the ongoing sync layer that takes over once the one-time migration is complete, keeping HubSpot Service Hub in sync with a data warehouse, a billing system or a product analytics tool.

Managed-migration cost ranges vary widely. A clean Help Scout-to-Service Hub move of under 10,000 tickets with no Knowledge Base typically lands in the £2,500–£7,500 / $3,000–$10,000 range — Incremental's published model starts at £500 for setup and adds packages by record count.

A Zendesk-to-Service Hub project with 100,000 tickets, KB articles, custom fields, macros to rebuild and SLAs to redesign typically runs $25,000–$120,000, with the upper end driven by ticket count, custom-field complexity, conversation-thread depth and the number of automations rebuilt.

For teams that want to outsource the migration end-to-end, FlitStack specialises in HubSpot Service Hub migrations and handles the field mapping, ticket-pipeline design, Knowledge Base import, attachment fetching, picklist internal-value conversion, and the validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on ticket count and source platform, with separate line items for KB articles, Custom Objects and macros-to-workflows rebuild scope so the cost is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Solutions Partner, HubSpot's in-house onboarding, an automated specialist tool, or a managed migration vendor. [Explore FlitStack →](/contact)

HubSpot Service Hub migration checklist

A phased, atomic task list for moving a helpdesk operation onto HubSpot Service Hub — covering tickets, conversations, knowledge base, SLAs, and validation. Typical timeline: 6–16 weeks.

0. Decide & Plan10 tasks
  • Define in-scope objects: Tickets, Contacts, Companies, Conversations, Knowledge Base articles, Users, Teams, Files. Document each in or out of scope in writing. Custom Objects are gated to Service Hub Enterprise, so confirm tier before promising them.If skipped: Scope drift mid-migration forces re-mapping after fields are already loaded, and Enterprise-only objects discovered late blow the budget.
  • Decide the historical-data window for tickets and conversations. Choose a cutoff (e.g., 24 months, 36 months, all-time). Older closed tickets often have low operational value but multiply migration volume and storage.If skipped: Importing unbounded history inflates association counts, custom-property usage, and runtime past the cutover window.
  • Decide whether to use the Help Desk workspace (2024 ticket-centric UI) or the older Conversations Inbox. Help Desk requires Service Hub Professional or Enterprise. Both surfaces share underlying tickets and threads, but agent UX, routing, and views differ.If skipped: Switching surfaces post-cutover forces a second round of view/routing rebuild and retraining.
  • Confirm the HubSpot subscription tier per Hub and add-on pack you need (Free, Starter, Professional, Enterprise). Map required features (SLAs, custom objects, multi-KB, playbooks, advanced routing) to the tier that includes them. Custom Properties Limit Increase is sold at $220/mo per 500-property pack up to 3,000 per object.If skipped: Discovering a feature is tier-locked after kickoff forces a contract change order and delays cutover.
  • Identify the data center region (NA vs. EU) the portal lives in. If EU residency is required for GDPR, confirm the portal is provisioned in the EU data center. Migration between data centers is restricted once HIPAA storage is indicated on the account.If skipped: GDPR sign-off blocks go-live if customer data lands in the wrong data center.
  • Document compliance constraints: GDPR data subject rights, SOC2 evidence requirements, retention policies, BAA limitations. HubSpot does not sign BAAs for the standard product, so flag any PHI exposure now. Inactive-contact data retention can be configured under Privacy & Consent.If skipped: Compliance objections surface at UAT and block sign-off after the data is already loaded.
  • Assign a single accountable migration DRI and a service-side product owner. Name the human, not the team. Add a backup for the cutover weekend.
  • Set the cutover date, freeze window, and rollback window in writing. Pick a low-volume window (typically a weekend). Define the exact hour the source goes read-only and the exact hour Service Hub becomes the system of record.If skipped: Without a freeze, tickets created during cutover get split across source and destination and customers see duplicate responses.
  • Document the success criteria for declaring the migration complete. Specify: open-ticket count reconciled, agent assignments reconciled, KB article counts reconciled, CSAT/NPS history accessible, and named UAT users signed off.
  • List out-of-scope items explicitly. Common exclusions for HubSpot Service Hub imports: ticket Created/Updated/Closed dates (cannot be backdated programmatically), CC recipients on tickets, inline images inside ticket emails, groups, and historical user-to-user conversations.If skipped: Stakeholders assume excluded items are coming and surface them as defects during UAT.
1. Pre-Migration Prep22 tasks
  • Export current record counts per object from the source helpdesk as a baseline. Capture counts for tickets (open and closed), contacts, companies, conversations, articles, attachments, agents, tags, macros, triggers, SLA policies, and surveys.If skipped: Without a baseline, post-migration reconciliation cannot prove completeness.
  • Run dedup analysis on source contacts using email as the match key. Resolve duplicates before export. HubSpot will deduplicate contacts on email at import, which can silently collapse rows that should have stayed distinct.If skipped: Silent merges at import permanently fuse separate customer histories into one contact record.
  • Run dedup analysis on source companies using primary domain. HubSpot uses domain as the default company unique identifier. Multiple source companies sharing a domain will merge on import unless an external ID is used.
  • Standardize email casing, phone number format, and country codes. Lowercase emails. Normalize phone to E.164. Use ISO country codes or HubSpot picklist values exactly. Trim leading and trailing whitespace from every cell.If skipped: Foreign characters and trailing whitespace trigger 'Property values were not valid' errors that fail entire batches.
  • Audit ticket status, priority, type, source, and tag values for spelling variants. Consolidate variants like 'In progress', 'In Progress', 'in-progress' into a single canonical value before mapping.If skipped: Picklist mismatches trigger 'Invalid enumeration option' errors and block entire ticket batches.
  • Identify and resolve tickets and contacts with missing required fields. First name and last name are common offenders. The HubSpot importer fills missing name fields with the literal word 'Empty', which leaks to agents.
  • Inventory all macros, triggers, automations, and SLA policies. Export the rule logic to a spreadsheet. None of this transfers directly into HubSpot — it rebuilds as Workflows, Snippets, and pipeline-level SLAs.
  • Inventory active integrations on the source helpdesk. List every calendar sync, CTI/voice integration, BI extract, and CSAT/NPS survey hook. Each one has to be paused at cutover and re-pointed at HubSpot.
  • Provision the production HubSpot portal and a standard sandbox. Standard sandbox is gated to Enterprise tiers. If you do not have access, use a development sandbox or a separate test portal cloned to match intended production settings.If skipped: Skipping a sandbox load means production is your test run, and import errors burn property and association limits you cannot fully reclaim.
  • Set account currency, timezone, fiscal year, and language defaults. These affect how dates render and how currency fields parse during import. Set them once before any record is created.
  • Create all required users with Service Hub seats. Agents handling tickets need a Service paid seat. Email addresses must match the source agent emails one-to-one wherever possible so ticket ownership maps cleanly.If skipped: Mismatched agent emails force a fallback assignee on every imported ticket and destroy historical workload reports.
  • Configure Teams and the Service permission set for each role. Settings > Users and Teams. Decide who is Super Admin, ServiceTeam member, who can edit pipelines, and who can publish KB articles.
  • Create all ticket pipelines and stages before importing tickets. Each pipeline has its own stages and SLA configuration. Capture both the display label and the internal value of each stage — import files match on internal value, not label.If skipped: Importing tickets into a stage that does not exist drops every row in the batch.
  • Create all custom contact, company, and ticket properties before any import. Match field types exactly: Single-line text, Multi-line text, Number, Date picker, Date and time picker, Single checkbox, Multiple checkboxes, Dropdown select, Radio select, File. Capture the internal name of each property.If skipped: Importing into a property that does not exist silently drops the column data with no row-level error.
  • Pre-create dropdown and multi-select picklist values to match source values exactly. HubSpot matches on internal value, not display label. Trailing/leading whitespace in option values is also rejected.
  • If audit dates matter, create custom datetime properties named 'Legacy Created At', 'Legacy Updated At', and 'Legacy Closed At' on the Ticket object. HubSpot does not allow migrating native Created/Updated/Closed dates onto tickets, so the original timestamps must live in custom properties.If skipped: Without legacy date properties, every imported ticket appears created on cutover day and historical SLA reporting is destroyed.
  • Create a 'Legacy Ticket ID' single-line text property on the Ticket object. Use this as the upsert key during import. It also gives agents a way to look up tickets by the old system's IDs in customer correspondence.If skipped: Without an external ID, re-running a partial load creates duplicate tickets instead of updating existing ones.
  • Configure the Conversations Inbox channels you will use post-cutover. Connect email channels (team aliases), forms, live chat, and any messaging channels in scope. Verify DKIM/SPF/DMARC records before going live.If skipped: Unverified sending domains cause customer replies to bounce or land in spam from day one.
  • Set all newly configured workflows and integrations to 'off' or 'paused' until cutover. Notification emails, customer-portal welcome emails, and SLA breach alerts will all fire against imported tickets unless paused.If skipped: Imports trigger thousands of automated notifications to live customers on resolved tickets.
  • Announce the freeze window to all source-system users in writing. State the exact hour the source goes read-only and the channel for emergencies during cutover.If skipped: Agents working past the freeze create tickets that vanish at delta cutoff.
  • Schedule end-user training on Help Desk workspace, Tickets, and the Conversations Inbox before go-live. Cover canned responses (Snippets), Workflows that auto-assign, and how to find a ticket by Legacy Ticket ID.
  • Designate first-responder agents for the first 48 hours post-cutover. These people triage user issues, watch the inbox, and own the rollback decision if something is wrong.
2. Source Export13 tasks
  • Export the agent/user list from the source helpdesk with email, role, team, and active/inactive status. Include deactivated agents — historical tickets reference them and need a remap target.
  • Export contacts with all standard and custom fields as CSV (UTF-8). Save as 'CSV UTF-8 (Comma-delimited)' to preserve non-ASCII characters. Confirm fewer than 1,000 columns per file.If skipped: Non-UTF-8 encoding turns Korean, Cyrillic, and accented characters into '??????' on import.
  • Export companies/organizations with all standard and custom fields. Include primary domain as a separate column — it is the default HubSpot match key.
  • Export tickets with all standard and custom fields, including original ticket ID. Capture original Created, Updated, and Closed timestamps in separate columns. Keep them — they will land in the Legacy date properties created in Phase 1.If skipped: Omitting original dates collapses years of SLA history into the cutover date.
  • Export ticket conversation threads — public comments, internal notes, and email messages — as separate files per type. Split into three buckets per the destination model: comments and internal notes map to Notes; email exchanges map to Emails; field-change history maps to a custom property.If skipped: Re-importing emails is not supported — existing Email engagements cannot be updated, so the data has to be right on first write.
  • Export ticket-to-contact and ticket-to-company associations. Each row should carry both the legacy ticket ID and the legacy contact/company ID so associations can be rebuilt on the HubSpot side.
  • Export knowledge base articles with title, body HTML, category, tags, and meta description. Capture the article body as full HTML source including image URLs. HubSpot's KB importer expects an 'Article Body' column containing source code.
  • Export all attachments and the metadata that links each file to its ticket or contact. Produce a manifest CSV (filename, MIME type, size, source ticket ID) and download binaries to a structured folder. Note the per-record file size limits: 20 MB on one-to-one emails, 25 MB on chat to visitor, 50 MB on Customer Portal.
  • Export macros, automation rules, and SLA policies as configuration snapshots. Capture screenshots and exported JSON/YAML where the source allows. These rebuild manually as HubSpot Workflows, Snippets, and pipeline-level SLAs.
  • Export CSAT/NPS/CES survey definitions and historical responses. Survey history lands on the Feedback object in HubSpot (Service Hub Professional/Enterprise). Preserve respondent contact and response timestamp.
  • Export tag, group, and team taxonomies separately as reference files. Note: HubSpot Service Hub KB articles have a 100-tag cap per article on the new KB tools, so over-tagged source articles must be trimmed in Phase 3.
  • Capture screenshots of all source dashboards and saved reports. Reports do not migrate. They rebuild manually in HubSpot Reports after cutover.
  • Record the exact UTC timestamp of each export. Cutover delta loads at Phase 5 use these timestamps to compute the delta window.If skipped: Without timestamps you cannot prove which records were already exported, and the delta load misses or duplicates rows.
3. Transform & Map26 tasks
  • Build a master mapping spreadsheet covering every source field for contacts, companies, tickets, and articles. Columns: source object, source field, destination object, destination property internal name, type, required-on-import flag, transformation rule, nullability, picklist resolution.If skipped: Without a single source of truth, transform logic diverges across CSVs and bugs surface only at validation.
  • Resolve every picklist value mismatch between source and destination. For each enumeration property, list source value -> HubSpot internal value. Strip leading/trailing whitespace; HubSpot rejects it.
  • Choose the upsert key per object. Contacts: email. Companies: domain or a custom external ID. Tickets: Legacy Ticket ID. KB articles: source article slug.
  • Decide handling for source fields with no destination equivalent. Options: drop, concatenate into a generic Notes field, or create a new custom property. Document the decision per field.
  • Map source agents to HubSpot users by email. Where a source agent is deactivated or missing, reassign their tickets to a designated 'data migration' user or to a current team lead. Record the rule per source agent.
  • Convert all dates and datetimes to a consistent ISO-8601 format. HubSpot's import wizard parses dates against the format you select; mixed formats inside one column raise 'Could not parse date' on every off-format row.If skipped: Inconsistent date formats fail rows individually with no batch-level early warning.
  • Re-save every CSV as UTF-8 explicitly (CSV UTF-8, Comma-delimited). Excel's default 'CSV (Comma delimited)' is not UTF-8 on Windows. Use the UTF-8 variant or Google Sheets export.
  • Trim leading and trailing whitespace from every cell. Apply across enumeration fields especially — HubSpot rejects leading/trailing whitespace and invisible Unicode characters on non-string properties.
  • Truncate text fields that exceed HubSpot property limits. Default text properties: ~256 characters. Multi-line text fields handle longer content but still have caps. Custom event properties cap at 256 chars (URL/referrer at 1,024). Split or move overflow content to a Notes engagement.
  • Escape commas, quotes, and newlines inside text cells per CSV rules. Wrap problematic cells in double quotes and escape inner quotes by doubling them.
  • Cap article tag counts at 100 per article. The new HubSpot KB tools enforce a 100-tag-per-article limit. Trim less useful tags or consolidate them before import.If skipped: Articles exceeding 100 tags fail KB import or get silently truncated.
  • Split contact import files so each file stays under 512 MB and 1,048,576 rows. Free tier caps at 20 MB and 500,000 rows per day. Starter/Pro/Enterprise cap at 512 MB per file and 10,000,000 rows per day, with at most 3 simultaneous imports.
  • Sort import files so parent records precede child records. For parent-child company hierarchies, stage parent rows above child rows in the file. The child's parent-company column should reference the parent's record ID or domain that HubSpot can resolve in the same import.
  • Populate Legacy Created At / Updated At / Closed At custom datetime properties on every ticket row. These are the only ways to preserve original ticket timestamps. The native ticket Created/Closed/Updated dates will all stamp to the load time and cannot be overwritten.If skipped: every imported ticket looks created on cutover day and breaks tenure/closure-rate reporting.
  • Decide and document the strategy for the source field-change audit trail. HubSpot has no native equivalent for systems like Salesforce CaseHistory. Concatenate the change log into a custom multi-line text 'Legacy Case History' property on each ticket, or attach a one-time PDF per ticket in Files.
  • Decide and document attachment strategy: re-upload binaries or link to external storage. Re-uploading into HubSpot Files preserves search and customer-portal access. Linking out (S3, Drive) saves storage but loses portal access.
  • Decide handling for inline images embedded in source ticket emails. Inline images cannot be migrated into HubSpot's email engagement bodies. Either convert them to attachments associated with the ticket, or strip them and leave a placeholder reference.If skipped: Inline images in source emails render as broken images on imported tickets unless converted to attachments.
  • Decide how to map source 'CC' recipients on tickets. CC fields are not part of the HubSpot ticket import schema. Capture CC addresses in a custom multi-line text property if you need to preserve them.
  • Map source ticket groups/queues to HubSpot Ticket Pipelines and stages by internal value. Each source group/queue typically becomes a Pipeline. Each status becomes a Stage with both a display label and an internal value the importer matches on. If your source uses one queue with many statuses, model that as one Pipeline with many Stages.If skipped: Mapping by display label instead of internal value silently drops every ticket whose source status name differs in casing or punctuation.
  • Transform ticket conversation history into HubSpot's engagement model: public/internal comments -> Notes, customer-agent emails -> Emails, field-change history -> a custom 'Legacy Case History' property. Notes carry hs_note_body and hs_timestamp (preserved from source). Emails carry direction, from, to, subject, body — and cannot be updated after import, so the first write has to be correct.If skipped: Loading email engagements with wrong direction or missing addresses leaves an unfixable record and forces a full delete-and-reload of that ticket's thread.
  • Configure the Conversations Inbox and Help Desk workspace routing to handle the post-cutover channel mix. Connect email, chat, forms, and any messaging channels. Build inbox routing rules so new conversations from imported contacts auto-associate to existing tickets or contacts.
  • Prepare the Knowledge Base CSV per HubSpot's importer schema and upload via Settings > Content > Knowledge Base > Import knowledge base. Required columns: Article Body (full HTML source including image URLs), Meta description. Optional: Title, Subtitle, Category, Subcategory, Keywords (comma-separated, no spaces after commas). KB import is a Service Hub Professional/Enterprise feature.If skipped: Spaces after commas in the Keywords column trigger tag-import errors that hide successful article imports underneath.
  • Rebuild macros as Snippets and rebuild trigger/automation rules as Workflows. HubSpot's Workflows engine is unified across all Hubs. Replace each source trigger with a workflow enrollment trigger plus actions. Document the source rule and the destination rule side by side.If skipped: Skipping the rebuild means agents lose their canned responses and tickets stop auto-routing on day one.
  • Rebuild SLA policies at the pipeline level using Service automation. SLAs are configured per Pipeline in HubSpot. Define first-response and time-to-close targets per priority and per business hours calendar.If skipped: Without pipeline SLAs, breach alerts never fire and SLA dashboards show empty after cutover.
  • Map CSAT/NPS/CES survey history to Feedback submissions on the Feedback object. Surveys are a Service Hub Professional/Enterprise feature. Each historical response becomes a Feedback record associated to the original contact and ticket where possible.
  • Upload binary attachments into HubSpot Files and capture each returned file ID for ticket association. Two-step pattern: upload the binary to Files, then attach the returned fileId to the ticket via an engagement (Note or Email). Convert inline ticket-email images to attachments using this same pattern.If skipped: Skipping the file-to-ticket association upload step leaves orphaned files no agent can find.
4. Sandbox Test Migration12 tasks
  • Load a 1-5% representative sample of each object into the sandbox via the Import Tool (Settings > Import & Export > Import). Cover every pipeline, every priority, every source channel, and every custom-property variant.If skipped: Loading only the easy records hides the gotchas until production load when they cost real time.
  • Validate field-by-field on 10 random sandbox tickets that values arrived correctly. Open the ticket in the Help Desk workspace and compare every visible field to the source. Pay special attention to picklists, dates, and the Legacy Ticket ID.
  • Validate that Legacy Created/Updated/Closed dates landed in their custom datetime properties. Confirm the native Created date stamps as today and the legacy date matches the source. Spot-check 25 tickets.
  • Test long-string, multi-line, and special-character cases explicitly. Include records with quotes, commas, newlines, emoji, RTL text, and non-Latin scripts. Confirm display on the ticket detail view.
  • Test NULL/empty values across every nullable property. If 'Don't import empty values' is needed, set it per column in the import wizard. Confirm empty cells do not overwrite existing populated values during update imports.
  • Test ticket-to-contact, ticket-to-company, and parent-child company associations on imported records. Open a sample contact and confirm the imported ticket appears in their timeline; open a child company and confirm parent_company points up correctly.If skipped: Reversed parent_company direction creates an unnavigable graph that requires re-importing the company file.
  • Test knowledge base article import end-to-end with a 5-article sample. Confirm body HTML renders, image URLs resolve, categories/subcategories land where expected, and keywords appear as tags. Verify no keyword had a trailing space.
  • Test attachment upload into HubSpot Files on a 50-file sample and confirm each file appears on its parent ticket. Time the round-trip and project to full volume. Confirm file size, MIME type, and access from a non-admin agent.
  • Time the test load and extrapolate to the production cutover window. Account for the 3-simultaneous-import cap and the 10,000,000-row-per-day limit on Starter/Pro/Enterprise (500,000 on Free). If the extrapolation exceeds the cutover window, redesign batching now.
  • Have one or two service-team power users spot-check sandbox tickets, KB articles, and conversation threads. Their job is to confirm tickets read correctly in the agent UI, not just that fields match the CSV.
  • Capture the test error report and triage every distinct error code. Map each error to a transform fix: 'Invalid enumeration option' (picklist), 'Could not parse date' (format), 'Could not find owner' (use email not name), 'Duplicate unique property value' (dedup), 'Association record not found' (load order), 'Missing required property'.
  • Get written sign-off on the sandbox results before proceeding. Sign-off from the DRI and the service-team lead. Cutover does not start without it.
5. Production Cutover11 tasks
  • Confirm the freeze is in effect on the source helpdesk. Verify in the source admin panel that no new tickets, comments, or contact edits have been written in the last hour. Document the freeze timestamp.
  • Take a final full export of source data. This is the delta export from Phase 2's baseline. Use the same column schemas so the transform scripts produce identical-shape destination CSVs.
  • Pause every workflow, integration, and notification in the destination portal. Set workflows to 'off' or unpublished, disable conversation-inbox auto-replies, and pause integrations that listen on ticket-create events. Verify in Settings > Automations > Workflows.If skipped: Live workflows fire on every imported ticket and email thousands of customers with auto-replies on resolved tickets.
  • Load users and team configuration first. Confirm every agent who owns historical tickets has a HubSpot seat with the matching email.
  • Load Companies, then Contacts, then Tickets, then conversation engagements (Notes and Emails), then attachments, then KB articles in this dependency order. Each batch uses an idempotent upsert keyed off the external ID property (Legacy Ticket ID for tickets, email for contacts, domain or custom external ID for companies).If skipped: Loading children before parents leaves orphan associations that fail with 'Association record not found' and cannot be repaired without re-running.
  • Use upsert with the external ID for each object. Upsert using legacy_ticket_id (or equivalent) so re-runs update instead of duplicating. Keep batches sized to fit HubSpot's documented per-call ceilings.If skipped: Using create instead of upsert duplicates every row on a re-run.
  • Capture import job IDs, row counts, and error files for every load step. Save the wizard's error CSV and the response payloads. These are needed for reconciliation in Phase 6 and for rollback if the run aborts.
  • Cross-check destination row counts against source at the end of each step. Compare the count returned by HubSpot to the source baseline. Investigate any delta of more than a handful of rows before moving to the next step.If skipped: Pushing forward with an unexplained delta stacks errors that become impossible to untangle later.
  • If a load step fails partway, stop, diagnose, fix the transform, and re-run the upsert. Do not push through with partial data. Idempotent upserts keyed on the external ID let you safely re-run the same batch.
  • Re-enable workflows, integrations, and notifications after all loads complete. Turn workflows back on in deliberate order: routing first, then SLA, then customer-facing notifications. Watch the first few enrollments live.
  • Flip the source helpdesk to read-only and update DNS/email routing to HubSpot. Point team email aliases at the HubSpot Conversations Inbox. Verify a test email lands in the inbox and creates a ticket.If skipped: Forgetting an email alias means customer replies still hit the old system and never reach agents.
6. Validate18 tasks
  • Compare total record counts per object: source vs. destination. Contacts, companies, tickets (open + closed), conversation engagements, KB articles, attachments.If skipped: An unexplained count delta usually means a transform dropped a column or a batch silently failed.
  • Compare open-ticket counts grouped by pipeline and stage. This is the helpdesk-equivalent of a GL trial balance: it is the number agents will look at on Monday.
  • Compare aggregate ticket counts grouped by agent owner. Confirms agent-mapping rules applied as intended and no orphan tickets fell back to the migration user.
  • Field-by-field cross-check on 25-50 randomly selected tickets. For each ticket compare: subject, status, priority, pipeline, stage, owner, contact, company, every custom property, Legacy Created At, Legacy Closed At.
  • Verify all custom property values arrived intact on a sample of 20 contacts and 20 companies.
  • Verify ticket-to-contact and ticket-to-company associations on a 50-ticket sample. Open the contact record and confirm the ticket appears in the activity feed and the associations panel.
  • Verify parent-child company associations. Spot-check 10 child companies and confirm parent_company resolves up correctly.
  • Verify Note and Email engagements are associated to the correct ticket and contact. Open a ticket timeline and confirm engagement order matches the source chronology using preserved hs_timestamp values.
  • Verify attachments are accessible from the ticket detail view and downloadable. Confirm a non-admin agent can open the file. Test from the Customer Portal where applicable.
  • Confirm Legacy Created At / Updated At / Closed At populated on every ticket via filtered list view. Build a tickets view filtered to Legacy Created At is unknown — the count should be zero. Investigate any rows that fail this filter.
  • Run a GDPR data-residency check: confirm the portal is in the expected data center. Verify via Account & Setup > Account Defaults and confirm any subprocessor list matches what was contracted.
  • Confirm data-retention policies for inactive contacts are configured per the legal sign-off. Settings > Privacy & Consent > Data Retention. Capture a screenshot for the audit log.
  • Export the centralized Audit Log post-cutover. Super Admins can view the centralized audit log under Settings > Account Defaults > Security > Audit Logs (Starter+). Save a snapshot as cutover evidence.
  • Confirm a rollback plan exists for the first 14 days using HubSpot's Restore CRM Properties feature. Settings > Data Management > Backup and Restore captures the last 20 versions per record (45 for contacts) within 14 days. Source export archives remain the canonical rollback artifact beyond that window.If skipped: Without an archived source export, an undiscovered defect after day 14 cannot be reversed.
  • Run a UAT cycle with 3-5 power-user agents covering daily workflows end-to-end. Each tester: opens 5 historical tickets, replies, applies a Snippet, transitions a stage, and confirms SLA timers fire as expected.
  • Run a UAT pass on the Knowledge Base: search, article rendering, and helpfulness feedback. Confirm a published article is findable by keyword and renders identical to source.
  • Document every UAT issue with severity and a fix owner. Block go-live on Sev-1 issues. Sev-2/3 issues can ship a fix-forward plan.
  • Get written sign-off from the migration sponsor and the service-team lead before announcing go-live. Sign-off references the success criteria locked in Phase 0.
7. Post-Migration Cleanup11 tasks
  • Communicate go-live to all end users with login URL, training links, and the where-to-get-help contact. Include a one-line note about how to find a ticket by its Legacy Ticket ID.
  • Run role-segmented training sessions on Help Desk, the Conversations Inbox, and Workflows. Separate sessions for agents, team leads, and admins. Record each session and store in the KB.
  • Set the source helpdesk to read-only and post the read-only announcement. State the planned decommission date in the same message so users have one consistent timeline.
  • Rebuild reports and dashboards in HubSpot Reports. Reports do not migrate. Common service dashboards to rebuild: open tickets by pipeline/stage, CSAT trend, first-response time, SLA breach rate, agent workload.If skipped: Without rebuilt dashboards, leadership cannot answer 'how is service going' on day one.
  • Verify rebuilt Workflows, Snippets, Playbooks, and SLAs are live and enrolling. Check enrollment history on each workflow to confirm tickets are flowing through it.
  • Re-establish integrations to other systems. Calendar sync, CTI/voice provider, BI extracts, Salesforce sync if dual-running. Re-validate the field mappings after the data-shape change.
  • Configure customer-facing tools: Customer Portal, KB feedback form, and any embed forms. Confirm the customer portal references the right tickets and that domain settings/branding match.
  • Schedule a 30-day post-migration retrospective. Capture what went well, what surprised the team, and what would change next time. Feed lessons into the next platform migration.
  • Set the source helpdesk's decommission date (typically 90 days after cutover). Coordinate with legal and security on the retention window before final shutoff.
  • Archive all source-system exports and the transform scripts to long-term storage. Encrypted, access-controlled, and indexed. Retain for the full legal retention window. Include the master mapping spreadsheet and the import job logs.If skipped: If a defect surfaces six months later and the archive is gone, root cause cannot be diagnosed.
  • Close out the project formally: final status report, lessons learned, and project closure. Hand the operational ownership of the portal to the long-term admin team.

Questions, answered

Migrating to HubSpot Service Hub: questions

How long does migration to HubSpot Service Hub take?

A small-team migration with under 5,000 tickets and standard fields runs three to five business days end-to-end. A mid-market Zendesk-to-Service Hub project with 100,000 tickets, Knowledge Base articles, macros and SLA rebuild work runs four to six weeks of elapsed time including sandbox dry-runs, validation, agent training and hyper-care.

Can I migrate from Zendesk to HubSpot Service Hub?

Yes, and Zendesk-to-Service Hub is the most common migration shape. Tickets, contacts, organisations and conversation history move with specialist tools, but triggers, macros, SLA policies and views do not — they are rebuilt as HubSpot Workflows, Snippets and pipeline-level SLA configurations after the data lands.

Can I migrate from Freshdesk or Help Scout?

Yes — both are well-supported by Help Desk Migration, Import2 and Suprdense, which handle tickets, conversations, attachments and contacts automatically. Help Scout migrations tend to be cleaner because the source schema is simpler. Freshdesk migrations require more attention to custom-field mapping and the rebuild of automations from scratch.

Are ticket created and closed dates preserved on import?

No. HubSpot does not allow migrating ticket Created at, Updated at or Closed at dates to Service Hub — they re-stamp to import day. The workaround is custom Legacy Created Date, Legacy Closed Date and Legacy Updated Date datetime properties on the Ticket object, populated from the source export.

What happens to macros, triggers and SLA policies during migration?

None of them migrate. Zendesk Triggers and Freshdesk Automations are rebuilt as HubSpot Workflows. Macros become Snippets or Templates. SLA policies become pipeline-level SLA configurations under Service settings — and historical SLA breach data does not carry over. Print the inventory, classify each rule as rebuild, redesign or retire.

Can I migrate Knowledge Base articles in bulk?

Yes — Service Hub Professional and Enterprise ship a dedicated CSV importer at Settings → Content → Knowledge Base. Required columns are Title, Article Body (HTML source), Category and Meta description. Images must be referenced by URL, not embedded. Each article is capped at 100 tags on the new editor.

What's the difference between the UI import and a specialist helpdesk migration tool?

The UI Import Tool handles up to 1,048,576 rows per file on paid tiers and is best for one-shot Ticket and Contact loads under 100,000 records. Specialist tools like Help Desk Migration, Import2 and SuprSwitch ship source-platform extraction, attachment fetch-and-attach, conversation threading and delta-run support out of the box.

Is there an undo or rollback for Service Hub imports?

HubSpot ships Restore CRM Properties and Records, which captures the last 20 property versions per record (45 for contacts) and lets super admins undo changes from the last 14 days via Settings, Data Management. It is not a bulk-rollback button — stamp every imported ticket with an Import Batch ID instead.

Get a quote

Moving to HubSpot Service Hub?

Tell us where your data lives today and roughly how much there is. We scope the migration and the HubSpot Service Hub setup with you, then send a quote.

Get a quote