A Front to HubSpot Service Hub migration requires API-based orchestration across 4–6 HubSpot endpoints per conversation. Plan 4–8 weeks. CSV imports can't preserve message threads.
There is no native migration path from Front to HubSpot Service Hub, and third-party tools offer limited coverage for this specific route—most lack support for full engagement history with timestamp preservation, attachment linking, and multi-object association orchestration. The core challenge is translating Front's flat, conversation-centric shared-inbox model into HubSpot's relational CRM architecture, where every ticket, email engagement, and note must be explicitly associated with Contact and Company records via multiple API calls. A single Front conversation can require 5–10 separate HubSpot API calls, and Front's free-form tags must be mapped to HubSpot's typed property system (enumeration dropdowns) before any data import can begin. Rules, automations, shared drafts, per-inbox signatures, and analytics dashboards cannot be migrated and must be rebuilt manually in HubSpot.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
The bottom line
CSV exports from Front do not include full conversation threads. To preserve message history with original timestamps and sender attribution, you need an API-based migration using Front's Core API and HubSpot's Engagements API. There is no native Front-to-HubSpot migration tool, and third-party migration platforms (e.g., Import2, Help Desk Migration) offer limited coverage of this specific path — most lack support for full engagement history with timestamp preservation, attachment linking, and multi-object association orchestration.
Do not skip the tag audit
HubSpot will accept a text field, but if you want filterable ticket states, queues, or categories, you need enumeration properties with their option values created before import. HubSpot property option internal values must be lowercase with no special characters — Front tags have no such restrictions. This mismatch is where bulk loads fail most often.
On API versions
HubSpot now documents email activities through date-versioned APIs (e.g., 2026-03). The older Engagements API (v1) still exists in the legacy reference. For new integrations, HubSpot recommends the newer APIs, but the legacy Engagements endpoint remains the most commonly documented path for migrations requiring timestamp preservation. Key difference: the legacy v1 API uses timestamp at the engagement level, while the newer APIs use hs_timestamp as a property on the activity object. Both achieve the same result for migration purposes.
Critical order-of-operations
Contacts and companies must exist before tickets (associations require both objects). Tickets must exist before engagements can be associated. Attachments must be uploaded before they can be linked to engagements. Violating this order creates orphaned records that are painful to clean up.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Front
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm HubSpot Service Hub can hold your support model
Walk your current workflow through HubSpot Service Hub: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Front → HubSpot Service Hub timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Front → HubSpot Service Hub specifics
- Unified CRM view
- The team already uses HubSpot CRM or Marketing Hub and wants sales, marketing, and service on the same Contact and Company records. Front's lightweight contact model doesn't provide lifecycle stages, deal associations, or activity timelines. Eliminating the Front↔HubSpot CRM sync layer removes a recurring source of data drift and integration maintenance.
- Native SLA management
- HubSpot Service Hub Professional and Enterprise include time-to-first-response and time-to-close SLAs with business-hours support and a built-in compliance dashboard (knowledge.hubspot.com). Front handles SLAs through inbox-scoped rules — less granular, no centralized compliance reporting.
- Ticket pipelines with lifecycle automation
- HubSpot organizes service work around pipeline stages (New → Waiting on contact → Waiting on us → Closed, plus custom stages), powered by Workflows with conditional branching, delays, and multi-object triggers. Front organizes work around inbox assignment — no formal pipeline.
- Built-in knowledge base, CSAT/NPS, and customer portal
- These are Service Hub Professional+ features with no Front equivalent. Teams planning to use them are building net-new, not migrating.
- Shared-inbox vs. CRM-first
- HubSpot Service Hub is not a standalone helpdesk — it is a service layer on top of a CRM. Every Ticket and Conversation ties to a Contact and Company record. Contact and company data must be clean and deduplicated before tickets can be imported.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Front export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Front export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Front where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Front → HubSpot Service Hub specifics
- When it works
- Contacts, companies, and basic ticket metadata (subject, status, pipeline, custom properties). Good for the CRM data layer.
- Limitation
- HubSpot's CSV import for Tickets does not preserve threaded email engagement history with original timestamps and per-message sender attribution. You get ticket metadata, not the full conversation thread. Front's account export also excludes attachments and individual inbox data.
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Front → HubSpot Service Hub field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Front → HubSpot Service Hub field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where HubSpot Service Hub has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
-
Contact deduplication
Front allows duplicate contacts by email. HubSpot deduplicates by email — on API create, HubSpot returns the existing contact ID if the email matches. Decide on merge rules for conflicting field values before migration (newest wins, most complete wins, Front value overrides).
Front → HubSpot Service Hub specifics
- Front Conversations → HubSpot Tickets + associated Engagements
- Each Front conversation becomes a Ticket with linked email and note Engagements. Closed or archived Front conversations import as Tickets with associated Engagements, not as live Conversations in HubSpot's Conversations Inbox. Note that HubSpot accounts created after April 1, 2024 cannot create tickets from channels connected to the Conversations Inbox — ticketing is centered in Help Desk instead (knowledge.hubspot.com).
- Front Messages → HubSpot Engagements
- Email messages become Email Engagements. Use HubSpot's email activity API with hs_timestamp, hs_email_subject, hs_email_html or hs_email_text, hs_email_headers, and hs_attachment_ids. The headers field auto-populates sender/recipient properties, keeping migrated email history readable (developers.hubspot.com). Internal comments become Note Engagements — hs_note_body tops out at 65,536 characters, so very long internal threads may need splitting across multiple notes. Each engagement links to both the Ticket and the Contact.
- Front Contacts → HubSpot Contacts (CRM object)
- This is a major upgrade — HubSpot Contacts are full CRM records with lifecycle stages, lead status, deal associations, and extensive default properties (firstname, lastname, email, phone, company, jobtitle, lifecyclestage). Many Front custom fields already map to existing HubSpot default properties, so audit your schema before creating redundant custom properties. Use email as the primary dedupe key.
- Front Contact Groups / Contact Lists → HubSpot Companies
- (if organizational) or HubSpot Static Lists / Contact properties (if categorical). Front deprecated the contact_groups API endpoint, replacing it with contact_lists (dev.frontapp.com), so inspect what the grouping actually represents before forcing it into Company.
- Front Teammates → HubSpot Users (Owners)
- Ticket assignment uses HubSpot Owner ID, not display names. Users must exist in HubSpot before tickets can be assigned.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a HubSpot Service Hub sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a HubSpot Service Hub sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under HubSpot Service Hub's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in HubSpot Service Hub, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Front stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from HubSpot Service Hub's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Front and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Front read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Front and HubSpot Service Hub record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in HubSpot Service Hub, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Front read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | high | Each Front conversation must be structurally decomposed into a Ticket plus multiple Engagement records with explicit associations, making this the most complex and error-prone entity to migrate. |
| Email Engagements (Messages) | high | Preserving original timestamps, sender attribution, HTML body content, and email headers requires the legacy Engagements API with precise field mapping and per-message API calls. |
| Attachments | high | Attachments must be uploaded individually via the Files API and then linked to engagements by setting hs_attachment_ids, with plan-based storage limits adding another constraint. |
| Contacts | medium | Front contacts map well to HubSpot CRM Contacts using email as the dedupe key, but existing HubSpot contact data requires careful deduplication and field-level merge logic. |
| Companies | medium | Front's contact groups/lists may or may not represent organizational entities, requiring manual inspection to determine whether they map to HubSpot Companies, Static Lists, or Contact properties. |
| Tags (Conversation) | high | Front's free-form tags must be mapped to HubSpot dropdown or multi-select properties with pre-created lowercase option values, and any mismatch in formatting or naming causes bulk import failures. |
| Custom Fields | medium | Type matching between Front and HubSpot custom properties is critical—many Front custom fields may already map to existing HubSpot default properties, requiring a schema audit to avoid redundant property creation. |
| Internal Comments | medium | Front conversation comments become HubSpot Note Engagements with a 65,536-character limit on hs_note_body, so very long internal threads may need splitting across multiple note records. |
| User Assignments (Teammates) | low | Front teammates map to HubSpot Users/Owners, but all users must exist in HubSpot with valid Owner IDs before ticket assignment can proceed. |
| Rules and Automations | medium | Front rules, SLA configurations, and routing logic have no migration path and must be entirely rebuilt as HubSpot Workflows and SLA policies, which use a fundamentally different trigger/action model. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Conversation-to-Ticket Structural Translation
Each Front conversation must be decomposed into a HubSpot Ticket plus separate Engagement records (emails, notes) with explicit associations to Contacts and Companies, requiring 5–10 API calls per conversation.
Free-Form Tags to Typed Properties
Front's unrestricted tag values must be audited and mapped to HubSpot enumeration properties with lowercase, special-character-free internal values pre-created before import, which is the most common point of bulk load failure.
Timestamp and Attribution Preservation
CSV exports do not include full threaded conversation history with original timestamps and per-message sender attribution, requiring an API-based migration using Front's Core API and HubSpot's Engagements API.
Multi-Object Association Orchestration
HubSpot does not auto-create associations, so Contact↔Company, Ticket↔Contact, Ticket↔Company, and Engagement↔Ticket+Contact links must all be explicitly built via the Associations API v4 in the correct sequence.
Contact Deduplication Across Systems
Front's lightweight contact model must be reconciled against HubSpot's full CRM Contact records—including lifecycle stages, deal associations, and existing data—using email as the primary dedupe key before tickets can be imported.
Automation and Rules Rebuild
Front's per-inbox assignment rules, SLA configurations, and canned responses have no migration path and must be manually recreated as HubSpot Workflows, SLA policies, Snippets, and Email Templates.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
How long does a Front to HubSpot Service Hub migration take?
A typical migration for a 30-agent team with 150K conversations takes 4–8 weeks including planning, CRM setup, data migration, and validation. The ticket-plus-engagement import phase is the bottleneck, as each conversation requires multiple API calls across different HubSpot endpoints.
Can Front conversation history be preserved in HubSpot?
Yes, but only via API-based migration. Each Front message imports as a HubSpot Email or Note Engagement associated with the Ticket and Contact, with original timestamps preserved via the Engagements API. CSV import captures ticket metadata only, not threaded message history.
What data can't be migrated from Front to HubSpot Service Hub?
Shared drafts, conversation links, per-inbox assignment rules, per-inbox signatures, Front Rules, analytics dashboards, SLA timer state, and integration configurations cannot be migrated. These must be rebuilt manually or have no HubSpot equivalent.
Which HubSpot Service Hub tier is needed for a full migration?
Service Hub Professional is the minimum for SLA management, custom reporting, ticket automation, and knowledge base. Starter tier supports basic tickets but lacks Workflows on tickets, SLAs, and the customer portal.
Do I need to shut down Front during migration?
No. Front and HubSpot Service Hub can run side-by-side. Most teams keep Front active for live support during migration, then cut over channels to HubSpot at go-live. Front stays in read-only mode for 6–12 months post-migration as a fallback.