Richpanel to HubSpot Service Hub migration is bottlenecked by Richpanel's 100 calls/min API limit. Migrated tickets appear on the Activity Timeline, not the Help Desk conversation pane.
Migrating from Richpanel to HubSpot Service Hub requires a fundamental architectural shift from an e-commerce, order-centric conversation platform to a CRM-first ticket-and-engagement model — there is no native end-to-end import path that handles this transfer automatically. Richpanel's core objects (Conversations, Messages, Customers, Orders, Tags) must be decomposed and reconstructed across 3–5 separate HubSpot API endpoints, mapping to Tickets, Engagements, Contacts, Custom Properties, and Owner assignments respectively. The primary extraction bottleneck is Richpanel's API rate limit of 100 calls per minute (492 status code on breach), which means extracting 50K conversations requires approximately 51,000 API calls and roughly 8.5 hours of extraction time at the rate limit ceiling. Custom work is required to handle order-context preservation, attachment re-hosting via HubSpot's File API, and full manual reconstruction of automation rules, self-service portal flows, and canned responses, none of which have an export or automated transfer mechanism.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
If your team is primarily a Shopify-native DTC brand with fewer than 10 agents and you
If your team is primarily a Shopify-native DTC brand with fewer than 10 agents and you don't use HubSpot CRM for anything else, the migration cost may outweigh the benefit. Richpanel's deep Shopify integration and self-service portal are hard to replicate in HubSpot without significant custom work.
CSV export limitation
Richpanel allows exporting conversations to CSV via bulk actions. But this export is metadata-level — it includes conversation IDs, statuses, assignees, and timestamps, but typically does not include full message thread content. Always verify your CSV export contains complete message bodies before relying on it as your primary extraction method.
The multi-store problem
Many Richpanel endpoints require an appClientId parameter — a unique identifier representing a specific store or brand. Find your app client IDs in Richpanel Settings → Connected Apps. If you run multiple stores in Richpanel, you need to extract each store's data separately and decide how to structure them in HubSpot (single portal with brand properties, or separate portals).
Association type IDs can vary by portal configuration and HubSpot updates
Validate the IDs above against your specific portal using GET /crm/v4/associations/{fromObjectType}/{toObjectType}/labels before running at scale. Using a wrong associationTypeId produces a 400 error rather than a silent failure, so these are detectable.
This is a platform limitation, not a migration bug
HubSpot distinguishes between "Engagement" objects (API-created emails and notes) and "Conversation" objects (native channel messages). There is currently no public API to create Conversation thread objects. Your migrated ticket history will live on the Activity Timeline, not in the conversation pane. Set agent expectations before cutover.
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 Richpanel
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 Richpanel → 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.
Richpanel → HubSpot Service Hub specifics
- CRM consolidation
- Teams already running HubSpot for Marketing or Sales want support in the same platform. Similar to the drivers behind Intercom to HubSpot Service Hub migrations, running Richpanel alongside HubSpot CRM means maintaining a separate integration just to keep customer context in sync.
- Reporting depth
- Richpanel's standard reports cover ticket volume, agent productivity, and channel performance, and you can export data for analysis in external tools like Excel or Google Sheets. HubSpot's custom reporting engine with cross-object datasets and attribution reporting gives teams more analytical power without exporting to spreadsheets.
- Scaling beyond e-commerce
- Richpanel works well for specific types of ecommerce brands but has clear limitations as businesses grow. Teams expanding into B2B, SaaS, or multi-vertical support need ticket pipelines, SLA management, and workflow automation that span sales and service — which is HubSpot's core strength.
- Pricing structure
- Richpanel charges one AI agent for $500/mo and $100/seat for the helpdesk. For teams not heavily leveraging AI resolution, HubSpot Service Hub Professional at $100/seat/month with included automation, knowledge base, and SLA tools can be more cost-effective (though you should account for mandatory onboarding fees, as detailed in our HubSpot Service Hub to Help Scout migration guide).
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 Richpanel 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 Richpanel 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 Richpanel 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
Richpanel → HubSpot Service Hub specifics
- Sample audit
- Pick 50–100 random tickets and programmatically verify that the number of messages in Richpanel matches the number of Engagements associated with that ticket in HubSpot.
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 Richpanel → 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 Richpanel → 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.
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 Richpanel 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 Richpanel 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 Richpanel 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 Richpanel 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 Richpanel 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.
Richpanel → HubSpot Service Hub specifics
- Count check
- Total tickets in HubSpot should match total conversations in Richpanel.
- Association check
- Every ticket should be associated with a Contact. Every Engagement should be associated with both its parent Ticket and the Contact. Use GET /crm/v3/associations/ticket/contact/batch/read to verify at scale.
- Attachment check
- Manually inspect 10–20 attachment-heavy tickets in the HubSpot UI to ensure files open correctly and HTML formatting is preserved.
- HTML fidelity check
- Open 10–20 tickets that contained HTML-formatted messages in Richpanel and confirm the formatting renders correctly in HubSpot — not as raw angle brackets.
- Owner check
- Confirm agent/owner assignments are correct.
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
| Richpanel field | HubSpot Service Hub field | Notes |
|---|---|---|
| Conversation | Ticket | One conversation = one ticket. Map status to hs_pipeline_stage. |
| Message (Agent/Customer) | Engagement (Email/Note) | Customer/agent messages → Email Engagements. Internal comments → Note Engagements. |
| Customer | Contact | Map email, phone, name, addresses. De-duplicate against existing HubSpot contacts. |
| Customer Address | Contact properties | Richpanel stores billing/shipping separately; HubSpot has a single default address. Use custom properties for shipping. |
| Order | Custom Object or Deal | Requires HubSpot Enterprise for Custom Objects. Or store key order data as custom Ticket properties. |
| Subscription | Custom Object or custom properties | Same Enterprise requirement for Custom Objects. |
| Tags | Ticket property (Dropdown/Multi-select) | HubSpot doesn't have a native tag object on tickets; pre-define dropdown or multi-select properties. |
| Agent | Owner | Map Richpanel agent emails to HubSpot user emails. |
| Team | Team | Create matching teams in HubSpot before import. |
| CSAT rating | Custom ticket property | Richpanel CSAT data needs a custom property in HubSpot. |
| Attachments | File Manager + Engagements | Files must be uploaded to HubSpot's File API, then linked to the corresponding Engagement via hs_attachment_ids. |
| Automation rules | Workflows | No export. Must be rebuilt manually in Service Hub Professional+. |
| Self-service portal flows | Knowledge Base + Chatflows | No export. Requires full manual recreation. |
| Macros / Canned responses | Snippets / Templates | No export. Must be manually copied over. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Conversations (Tickets) | medium | Conversations map cleanly to HubSpot Tickets one-to-one, but pipeline stage mapping must be manually defined and the migrated history will only appear on the Activity Timeline rather than the Help Desk conversation thread. |
| Messages (Engagements) | high | Each individual agent and customer message must be created as a separate HubSpot Email or Note Engagement and explicitly associated with both the Ticket and the Contact, making this the most API-call-intensive and structurally complex part of the migration. |
| Customers (Contacts) | medium | Customer records map to HubSpot Contacts with relatively straightforward field mapping, but deduplication against pre-existing HubSpot CRM contacts is mandatory and carries risk of data corruption if not handled carefully before import. |
| Orders | high | Order-to-conversation linkage is native in Richpanel but has no equivalent in HubSpot without Enterprise-tier Custom Objects or significant custom scripting to associate historical tickets with Deals synced via the Shopify integration. |
| Attachments | high | Attachments require a multi-step process of downloading from Richpanel, uploading to HubSpot's File Manager API, and re-linking to the correct Engagement, adding substantial extraction time and risk of broken file references if any step fails. |
| Tags | low | Richpanel Tags translate to HubSpot custom dropdown or multi-select Ticket properties, which is straightforward to implement provided the property options are pre-defined in HubSpot before the migration import runs. |
| Agents and Teams | low | Richpanel Agents map to HubSpot Owners by email address matching and Teams map to HubSpot Teams, making this a low-risk mapping provided all agent email addresses exist in the destination HubSpot portal before ticket assignment is applied. |
| CSAT Ratings | medium | CSAT data has no native destination field in HubSpot and requires a custom Ticket property to be created prior to migration, with a risk of data loss if the custom property schema is not defined and validated before the import begins. |
| Automation Rules and Workflows | high | Richpanel automation rules have no export path and cannot be migrated programmatically, requiring full manual recreation in HubSpot Workflows with a high risk of gaps in business logic if rules are not comprehensively documented before the migration begins. |
| Self-Service Portal and Macros | medium | Self-service portal flows and canned responses/macros must be manually recreated as HubSpot Knowledge Base articles, Chatflows, and Snippets, representing a significant effort risk for teams with large or complex self-service content libraries. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
API Rate Limit Extraction Bottleneck
Richpanel enforces a hard limit of 100 API calls per minute (returning a 492 status on breach), meaning extraction of large conversation datasets — requiring list calls plus per-conversation detail calls — can take 8–17+ hours and demands robust exponential backoff logic in the extraction pipeline.
Order Context Loss
Richpanel natively links conversations to e-commerce order and subscription data (Shopify, Magento, WooCommerce), but HubSpot has no equivalent native ticket-to-order association, requiring teams to choose between HubSpot Enterprise Custom Objects, Deal associations via a Shopify integration, or flattening order data into custom Ticket properties.
Conversation Thread Reconstruction
HubSpot tickets created via API do not populate the Help Desk workspace conversation thread, so migrated message history only appears on the ticket Activity Timeline, requiring each individual message to be created as a separate Engagement object (Email or Note) and explicitly associated with both the Ticket and the Contact via the Associations API.
Attachment Re-Hosting Complexity
All file attachments must be individually downloaded from Richpanel, uploaded to HubSpot's File Manager via the File API, and then re-linked to their corresponding Engagement objects using the `hs_attachment_ids` field, adding a significant volume of additional API calls beyond the core conversation extraction.
No Automation or Portal Export
Richpanel automation rules, self-service portal flows, and macros/canned responses have no export mechanism and must be fully rebuilt manually in HubSpot as Workflows, Knowledge Base articles, Chatflows, and Snippets/Templates respectively.
Contact Deduplication Risk
Richpanel Customer records must be matched against existing HubSpot Contacts by email or phone prior to import, as creating duplicate Contact records during migration will corrupt CRM history and break cross-object reporting for teams already using HubSpot for marketing or sales.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
Migrated tickets appear in Help Desk
but with empty conversation threads
Message history is visible on the Ticket record's Activity Timeline
— agents can see it, but not from the Help Desk workspace's conversation pane
Only tickets created through HubSpot's native channels
(connected inbox, chat, forms) automatically generate conversation threads
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Richpanel conversation history to HubSpot Service Hub?
Yes, but with a limitation. Conversation messages are migrated as HubSpot Engagement objects (emails and notes) and appear on the ticket's Activity Timeline. They do not appear in the Help Desk workspace's conversation thread pane — that only shows messages from HubSpot's native channels.
How long does a Richpanel to HubSpot migration take?
1–3 weeks for teams with under 50K conversations, 3–5 weeks for larger multi-store setups. Richpanel's API rate limit of 100 calls per minute is the main extraction bottleneck. Workflow and automation reconstruction adds 1–2 weeks on top.
Can I migrate Shopify order history from Richpanel to HubSpot?
Yes, but it requires mapping. You can use HubSpot's native Shopify integration to sync orders as Deals, create Custom Objects (Enterprise only), or map specific order data to custom Ticket properties during the migration.
Do Richpanel automation rules transfer to HubSpot?
No. Richpanel automation rules, self-service portal flows, macros, and widget configurations have no export mechanism. They must be manually rebuilt as HubSpot Workflows, Snippets, Knowledge Base articles, and Chatflows.
How do I keep ticket timestamps accurate during the migration?
You must explicitly pass the original Richpanel timestamps into the createdate or hs_createdate properties when making POST requests to HubSpot's APIs. For engagements, use hs_timestamp. Otherwise, HubSpot defaults to the date of the API call.