Plain to HubSpot Service Hub migration requires API-only extraction via GraphQL, careful data model translation (Threads→Tickets, Timeline→Engagements), and rate limit management on both sides.
Migrating from Plain to HubSpot Service Hub is a moderate-to-high complexity project with no native export or direct migration path — all data extraction must be performed through Plain's GraphQL API, as Plain provides no bulk CSV export for thread history. The two platforms operate on fundamentally different data philosophies: Plain uses a flat, event-driven, GraphQL-based timeline model while HubSpot uses a relational, object-oriented REST-based CRM model, meaning every entity requires deliberate mapping and transformation rather than a simple lift-and-shift. Plain's core objects — Threads, Customers, Companies, Timeline Entries, and Labels — map to HubSpot Tickets, Contacts, Companies, Engagements, and Tags respectively, but entities like Tenants, Custom Timeline Entries, and Customer Events have no native HubSpot equivalent and require Custom Objects (Enterprise-only) or serialization into standard note records. Custom work is required for schema pre-creation, rate-limit-aware extraction scripting, tenant architecture decisions, and full rebuild of automations, SLAs, and AI agent configurations.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Rate limit management
Parse x-ratelimit-remaining on every response. When remaining hits 0, read x-ratelimit-reset (Unix timestamp), compute reset_time - now(), and sleep for that duration plus a 200ms buffer. Do not use a fixed sleep — windows are time-based, not request-count-based, and a fixed sleep wastes extraction time. Implement exponential backoff (starting at 1s, capping at 32s) for 429 responses that occur despite header-based throttling.
Verify association type IDs before hardcoding them
Association type IDs can vary by portal configuration and HubSpot periodically updates them. The value 16 represents the standard Ticket-to-Contact association in most portal configurations, but you must confirm the correct IDs for your portal by calling:
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 Plain
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 Plain → 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.
Plain → HubSpot Service Hub specifics
- CRM unification
- a single platform where sales, marketing, and support share the same contact and company records without custom sync logic
- Multi-pipeline ticket management
- HubSpot supports multiple ticket pipelines with granular stage automation; Plain's model is limited to Todo/Done/Snoozed
- Built-in cross-object reporting
- tickets tied to deals, contacts, and companies in one reporting layer
- Knowledge base
- HubSpot includes SEO-optimized templates and analytics; Plain ships no knowledge base
- No-code workflow automation
- HubSpot Workflows cover SLA escalations, conditional branching, and multi-step sequences without engineering involvement
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 Plain 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 Plain 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 Plain 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 -
Audit and Map
Map Plain Tenants to HubSpot Companies using the decision tree above. Map Plain Users to HubSpot Owners by email. Document all custom properties needed and pre-create them.
Plain → HubSpot Service Hub specifics
- Endpoint
- https://core-api.uk.plain.com/graphql/v1
- Schema introspection
- https://core-api.uk.plain.com/graphql/v1/schema.graphql
- Rate limit
- The limit for your workspace is 450 requests per window, with headers x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset returned on every response. The window duration is 60 seconds. The x-ratelimit-reset header returns the Unix timestamp at which the window resets — sleep until that timestamp before issuing further requests.
- Customers
- All customers with email, name, company association, and external IDs.
- Exponential backoff
- on 429 responses (start at 1s, double up to 32s)
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 Plain → 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 Plain → 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.
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.
-
Test Migration
Extract 500–1,000 representative threads from Plain. Transform and load into HubSpot sandbox. Run full validation checklist.
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 Plain 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 Plain 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 Plain read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Plain → HubSpot Service Hub specifics
- Schema Setup
- Create custom properties (plain_thread_id, plain_customer_id, Thread Field properties). Configure pipeline stages. Verify association type IDs against production portal.
- Production Initial Sync
- Re-run extraction and load against production HubSpot portal using production credentials and ID maps. Record extraction start timestamp.
- Delta Sync and Cutover
- Pause incoming requests to Plain (set an auto-reply). Run delta script using updatedAfter filter for threads changed since initial sync. Route incoming mail to HubSpot. Archive Plain workspace.
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 Plain 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 Plain 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
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Object HubSpot Object
| Plain field | HubSpot Service Hub field | Notes |
|---|---|---|
| Customer | Contact | Email is the primary match key. |
| Company | Company | Match on domain. HubSpot auto-deduplicates on company domain. |
| Tenant | Custom property on Company/Contact | HubSpot has no native Tenant equivalent. Store externalId in a custom property. See tenant decision tree below. |
| Thread | Ticket | One thread = one ticket. Map status to pipeline stage. |
| Timeline Entry (Email/Chat/Slack) | Engagement (Email) | Each message becomes an engagement with original timestamp and sender mapping. Channel attribution (Slack vs. email) is lost unless stored as a custom engagement property. |
| Timeline Entry (Note) | Engagement (Note) | Internal notes on threads. |
| Custom Timeline Entry | Engagement (Note) | Serialize componentJson into human-readable text; HubSpot has no custom UI components in ticket timelines. |
| Labels | Tags or Custom Property | Labels are freeform in Plain; map to HubSpot tags or a multi-select property. |
| Thread Fields | Custom Ticket Properties | Must be pre-created in HubSpot before import. Match data types carefully. |
| Thread Status (Todo/Done/Snoozed) | Pipeline Stage | Map to Open, In Progress, Closed (or custom stages). Snoozed → "Waiting on Customer" custom stage. |
| Assignments (user/team) | Owner | Map Plain users to HubSpot owners by email. |
| Customer Events | No native equivalent | Requires Custom Timeline Events (Enterprise) or archived as notes. |
| SLA/Tier config | HubSpot SLAs (Service Hub Pro+) | Must be rebuilt. Config does not transfer. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Threads (Tickets) | medium | Plain Threads map cleanly one-to-one to HubSpot Tickets, but status mapping (Todo/Done/Snoozed to pipeline stages) requires pre-configured pipelines and custom stages, and volume above 50K threads introduces multi-hour extraction windows. |
| Timeline Entries (Engagements) | high | Each timeline entry must be individually fetched per thread and transformed into a HubSpot Engagement record, with channel attribution data (Slack vs. email) permanently lost unless explicitly stored in a custom engagement property. |
| Custom Timeline Entries | high | Plain's structured componentJson custom entries have no HubSpot equivalent and must be serialized into human-readable plain-text notes, resulting in irreversible loss of structured data and rendering fidelity. |
| Contacts (Customers) | low | Plain Customers map directly to HubSpot Contacts using email as the primary match key, and HubSpot's deduplication logic handles most collision scenarios, making this one of the lowest-risk entity types in the migration. |
| Companies | low | Plain Companies map to HubSpot Companies with domain as the match key and HubSpot auto-deduplicates on company domain, though any companies lacking a domain value will require manual resolution. |
| Tenants | high | Plain's Tenant model has no native HubSpot equivalent, and the chosen mapping strategy — custom property, parent-child Company, or Enterprise Custom Object — permanently determines the queryability and filterability of tenant-scoped data post-migration. |
| Labels (Tags) | low | Plain labels are freeform strings that can be mapped to HubSpot tags or a multi-select custom property with minimal data loss, though the full label taxonomy must be pre-created in HubSpot before ticket import. |
| Thread Fields (Custom Properties) | medium | Plain Thread Fields must be mapped to pre-created HubSpot custom ticket properties with precisely matched data types, and any type mismatches will cause import failures or silent data truncation. |
| Customer Events | high | Plain Customer Events have no native HubSpot equivalent and require either Enterprise-tier Custom Timeline Events or archival as note engagements, in both cases losing the structured event schema and queryability of the original data. |
| Attachments | medium | Attachments embedded in thread timelines must be downloaded from Plain and re-uploaded to HubSpot's file system before being referenced in Engagement records, significantly increasing extraction time for workspaces with high attachment volume. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
API-Only Data Extraction
Plain provides no bulk CSV export for threads or conversation history, forcing all extraction through its GraphQL API subject to a 450-requests-per-60-second workspace rate limit, making large dataset extraction a multi-hour operation requiring careful throttling logic.
Tenant Model Has No Equivalent
Plain's Tenant object supports many-to-many customer-to-tenant relationships via external IDs, and HubSpot has no native Tenant construct, requiring a pre-migration architectural decision between custom properties, parent-child Company associations, or Enterprise-only Custom Objects.
Timeline Entry Data Loss Risk
Plain's Custom Timeline Entries use a structured componentJson format with no HubSpot equivalent, requiring lossy serialization into plain-text Note engagements and permanently discarding channel attribution data for Slack-sourced messages.
Schema Pre-Creation Dependency
All custom ticket properties, pipeline stages, and Custom Objects must be created in HubSpot before import begins, as the API will reject records referencing property definitions or pipeline stages that do not yet exist in the target environment.
Automation and Workflow Rebuild
Plain's rule-based automations, webhook-driven workflows, AI agent configurations, and Customer Card integrations are runtime constructs that contain no portable data and must be fully rebuilt from scratch in HubSpot Workflows and custom sidebar cards.
Owner and Association Mapping
Every Plain Thread assignment must be resolved to a matching HubSpot Owner by email, and every Ticket must be linked to Contacts and Companies via HubSpot's Associations v4 API, requiring a complete user directory reconciliation before ticket import.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I export data from Plain as CSV for a HubSpot migration?
No. Plain does not offer a bulk CSV export for threads or full conversation history. All data extraction must go through Plain's GraphQL API at core-api.uk.plain.com/graphql/v1. You need an API key with appropriate read permissions and a script that handles pagination and the 450-request window rate limit.
How do Plain threads map to HubSpot tickets?
Each Plain Thread becomes one HubSpot Ticket. Thread timeline messages (emails, chat, Slack) become HubSpot Engagement records associated with the ticket. Thread status maps to pipeline stages: Todo→Open, Snoozed→In Progress, Done→Closed. Labels map to tags or custom multi-select properties. Thread Fields become custom ticket properties.
How do I migrate Plain Custom Timeline Entries to HubSpot?
HubSpot does not support custom UI components in ticket timelines. Serialize Plain's componentJson into a human-readable text string and insert it into HubSpot as a standard Note engagement, prefixed with [SYSTEM EVENT] so agents understand its origin.
How long does a Plain to HubSpot migration take?
For under 10K threads with simple schemas, 1–2 weeks. For 10K–50K threads with thread fields and labels, 2–4 weeks. For 50K–200K threads with attachments and customer events, 4–6 weeks. These include planning, HubSpot setup, script development, test migration, and validation.
What Plain data cannot be migrated to HubSpot?
Customer Cards (live API data panels), AI agent config (Ari), automations and webhook workflows, saved views and queue config, and Linear/GitHub bidirectional issue links cannot be migrated. Customer Events and Tenant data have no native HubSpot equivalent on Professional plans — they require Enterprise features or must be archived.