Migrate your Richpanel data
AI-first help desk built for ecommerce brands, combining a multichannel agent inbox with a self-service portal and order context. Most migrations involve Gorgias, Zendesk, or Help Scout.
In its favor
Why people choose Richpanel
The signal that keeps Richpanel on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Lowest entry price among ecommerce-native help desks — Starter at $29/seat includes ticketing, live chat, and email with no minimum seat count.
Order context built directly into the agent view means support teams resolve queries without switching between the CRM and the order management system.
AI Sidekick learns from top-agent responses and provides real-time assist, reducing training time for new hires without full autonomous AI deployment costs.
Self-service portal handles returns, exchanges, and order tracking, cutting ticket volume by an estimated 30% according to the vendor.
Built-in migration wizard supports imports from Zendesk, Gorgias, Help Scout, and Kustomer, making the initial setup a known path rather than a custom engineering project.
The self-service portal is not included in any base plan — it starts at ~$100/month extra — and customers frequently discover the true cost only after evaluating the product.
Sidekick AI is marketed as an autonomous agent but functions as an agent-assist tool; ecommerce brands expecting full ticket automation report disappointment with the level of autonomy.
No native phone channel — Aircall integration requires a minimum of 3 Aircall licenses regardless of how many agents actually handle calls, creating unexpected vendor lock-in.
Reported integration gaps with non-Shopify ecommerce platforms mean teams on WooCommerce, Magento, or custom stacks find themselves rebuilding data connections manually.
Customer support responsiveness, while praised in reviews, varies by plan tier — Starter users report longer resolution times on critical issues compared to higher-tier accounts.
Reasons to switch
Why people leave Richpanel
The recurring reasons buyers give for replacing Richpanel. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Richpanel fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Richpanel pricing overview
Richpanel uses a dual billing model: agent seats priced per-plan ($29–$99/seat/month) plus a self-service portal priced by monthly order volume (starting ~$100/month). AI Sidekick costs $20/seat as an add-on. A realistic 3-agent ecommerce setup with self-service portal typically runs $300–$600/month before AI features or phone integration costs.
Starter
Tier 1 of 5
$29/seat/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Richpanel's schedule — see our quote-based pricing →
What gets migrated
Richpanel object support
Object-by-object support for Richpanel migrations. Per-pair details surface during scoping.
Conversations
Fully supportedConversations are the primary ticket object in Richpanel. We migrate the full conversation thread including messages, internal notes, status, priority, and assignee. Tags are preserved as a flat array and can be remapped at the destination. The conversation-to-order link is maintained via the Order ID field.
Customer Profiles
Fully supportedCustomer Profiles include contact details, billing/shipping addresses, and a consolidated view of all interactions. We migrate profile fields 1:1 where field names match, and flag custom profile fields for explicit mapping during scoping.
Orders
Fully supportedOrders are synced from the connected ecommerce platform (Shopify, WooCommerce, etc.) and linked to Customer Profiles. We migrate the order reference, line items, totals, fulfillment status, and tracking information. The order-to-conversation linkage is preserved by matching Order IDs.
Subscriptions
Mapping requiredSubscriptions are only available on certain plan tiers and are tied to the connected ecommerce platform's subscription data. We migrate subscription records as linked objects but note that subscription metadata schemas vary significantly between platforms and may require field-level mapping.
Agents
Fully supportedAgent records include name, email, role, and team assignment. We migrate agent profiles and preserve team membership. Agent permissions and role-based access control (Admin, Agent, Viewer) are mapped to equivalent roles at the destination.
Teams
Fully supportedTeams are organizational units used for routing and assignment. We migrate team names and member lists. Where the destination uses a different routing model (e.g., groups vs. queues), we map team membership to the closest equivalent structure.
Tags
Fully supportedTags are applied to Conversations and Customer Profiles for categorization. We migrate all tags as flat key-value strings. Where the destination uses a hierarchical taxonomy or label scheme, we flag for manual review during scoping.
Automations / Rules
Not in this platformRichpanel Automations and Rules are executable workflow logic stored in the platform. These are not exported as data — they are configuration. We do not migrate them as records. We catalog them as a reference artifact and document the trigger/condition/action structure so the customer can rebuild them in the destination platform or with the destination's native automation engine.
Self-Service Portal Content
Mapping requiredThe self-service portal includes Help Center articles, custom flows, and order management widgets. Article content, categories, and published status are migratable. Custom flows are configuration-heavy and may not map 1:1 to other platforms' self-service builders. Portal settings (branding, domain) are documented as reference only.
Reports / Analytics
Not in this platformHistorical reporting data (resolution times, CSAT scores, agent metrics) is computed and stored in Richpanel's analytics layer, not as exportable records. We do not migrate analytics history. We recommend exporting reports as CSV from the Reports dashboard prior to migration cutoff as a separate customer-owned artifact.
Attachments
Mapping requiredFile attachments on conversations (images, PDFs, order documents) are stored in Richpanel's media layer. We migrate attachment metadata and re-download/re-upload files to the destination where the target platform supports file attachments. Large batch attachment migrations may extend timeline estimates.
Custom Fields
Mapping requiredCustom fields on Conversations and Customer Profiles are supported. We discover the custom field schema via the API during discovery and map each field individually. Field types (text, dropdown, date, checkbox) are preserved. Custom field behavior at the destination depends on the target platform's support for custom fields on equivalent objects.
| Object | Support | Notes |
|---|---|---|
| Conversations | Fully supported | Conversations are the primary ticket object in Richpanel. We migrate the full conversation thread including messages, internal notes, status, priority, and assignee. Tags are preserved as a flat array and can be remapped at the destination. The conversation-to-order link is maintained via the Order ID field. |
| Customer Profiles | Fully supported | Customer Profiles include contact details, billing/shipping addresses, and a consolidated view of all interactions. We migrate profile fields 1:1 where field names match, and flag custom profile fields for explicit mapping during scoping. |
| Orders | Fully supported | Orders are synced from the connected ecommerce platform (Shopify, WooCommerce, etc.) and linked to Customer Profiles. We migrate the order reference, line items, totals, fulfillment status, and tracking information. The order-to-conversation linkage is preserved by matching Order IDs. |
| Subscriptions | Mapping required | Subscriptions are only available on certain plan tiers and are tied to the connected ecommerce platform's subscription data. We migrate subscription records as linked objects but note that subscription metadata schemas vary significantly between platforms and may require field-level mapping. |
| Agents | Fully supported | Agent records include name, email, role, and team assignment. We migrate agent profiles and preserve team membership. Agent permissions and role-based access control (Admin, Agent, Viewer) are mapped to equivalent roles at the destination. |
| Teams | Fully supported | Teams are organizational units used for routing and assignment. We migrate team names and member lists. Where the destination uses a different routing model (e.g., groups vs. queues), we map team membership to the closest equivalent structure. |
| Tags | Fully supported | Tags are applied to Conversations and Customer Profiles for categorization. We migrate all tags as flat key-value strings. Where the destination uses a hierarchical taxonomy or label scheme, we flag for manual review during scoping. |
| Automations / Rules | Not in this platform | Richpanel Automations and Rules are executable workflow logic stored in the platform. These are not exported as data — they are configuration. We do not migrate them as records. We catalog them as a reference artifact and document the trigger/condition/action structure so the customer can rebuild them in the destination platform or with the destination's native automation engine. |
| Self-Service Portal Content | Mapping required | The self-service portal includes Help Center articles, custom flows, and order management widgets. Article content, categories, and published status are migratable. Custom flows are configuration-heavy and may not map 1:1 to other platforms' self-service builders. Portal settings (branding, domain) are documented as reference only. |
| Reports / Analytics | Not in this platform | Historical reporting data (resolution times, CSAT scores, agent metrics) is computed and stored in Richpanel's analytics layer, not as exportable records. We do not migrate analytics history. We recommend exporting reports as CSV from the Reports dashboard prior to migration cutoff as a separate customer-owned artifact. |
| Attachments | Mapping required | File attachments on conversations (images, PDFs, order documents) are stored in Richpanel's media layer. We migrate attachment metadata and re-download/re-upload files to the destination where the target platform supports file attachments. Large batch attachment migrations may extend timeline estimates. |
| Custom Fields | Mapping required | Custom fields on Conversations and Customer Profiles are supported. We discover the custom field schema via the API during discovery and map each field individually. Field types (text, dropdown, date, checkbox) are preserved. Custom field behavior at the destination depends on the target platform's support for custom fields on equivalent objects. |
Gotchas
What to watch for in Richpanel migrations
Issues we've hit on past Richpanel migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Self-service portal is a separate billing dimension
Sidekick AI is agent-assist, not autonomous resolution
Phone support requires Aircall with a 3-license minimum
Automations and Rules are not migratable data records
API rate limits are not publicly documented
| Severity | Issue |
|---|---|
| High | Self-service portal is a separate billing dimension |
| Medium | Sidekick AI is agent-assist, not autonomous resolution |
| Medium | Phone support requires Aircall with a 3-license minimum |
| Medium | Automations and Rules are not migratable data records |
| Low | API rate limits are not publicly documented |
Leaving Richpanel?
Where Richpanel customers move next
7 destinations Richpanel can migrate to.
How a Richpanel migration works
Four steps, Richpanel-specific
Connect
Not publicly documented into Richpanel. Scopes limited to read-only on the data we move.
Map
We translate Richpanel-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Richpanel quirks before production.
Migrate
Full migration with Richpanel rate-limit handling. Rollback available throughout.
FAQ
Richpanel migration FAQ
Answers to the questions buyers ask most during Richpanel migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Richpanel migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Richpanel.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Richpanel setup and destination — written quote back within a business day.