Helpdesk migration
Field-level mapping, validation, and rollback between Dossier Inbox and Gorgias. We move data and schema; workflows are rebuilt natively in Gorgias.
Dossier Inbox
Source
Gorgias
Destination
Compatibility
8 of 12
objects map 1:1 between Dossier Inbox and Gorgias.
Complexity
CModerate
Timeline
1-2 weeks
Overview
Moving from Dossier Inbox to Gorgias is a migration from a small-team shared inbox to a dedicated e-commerce helpdesk with Shopify-native integrations. Dossier Inbox stores conversations as email threads and chat widget sessions in a single team inbox, with labeling and team assignment for basic triage. Gorgias consolidates email, live chat, phone, and social channels into a unified ticket queue with order context pulled directly from Shopify. We extract Dossier Inbox conversations and messages, separate chat widget sessions from email threads at the source, and import them into Gorgias as distinct channel records so that live chat queues and email queues are populated correctly. Labels migrate as tags; attachments export to cloud storage and re-link in the destination. We do not migrate automations, macros, or Shopify store configuration; these require manual rebuild in Gorgias post-migration.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Dossier Inbox object lands in Gorgias, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dossier Inbox
Conversations
Gorgias
Ticket
1:1Dossier Inbox Conversations map to Gorgias Tickets as the primary record container. Each conversation thread becomes one Ticket with the conversation subject as Ticket subject and the original created timestamp preserved. We export conversations by channel type (email vs chat) and set the Gorgias channel field accordingly so that email threads land in the email channel and chat sessions in the live chat channel.
Dossier Inbox
Messages
Gorgias
Ticket Message
1:1Individual emails and chat messages within a Dossier Inbox Conversation map to Gorgias Ticket Message records. Each message carries sender, recipient, timestamp, body content, and attachment references. Messages are sequenced in arrival order within the parent Ticket. We resolve the sender against the migrated Contact record using email as the matching key.
Dossier Inbox
Contacts
Gorgias
Customer
1:1Dossier Inbox Contact profiles (customer names, email addresses, metadata) map to Gorgias Customer records. We extract contacts from conversation participants and deduplicate by email address before import. If a customer email appears across multiple conversations, we merge into a single Gorgias Customer record with all associated Tickets linked.
Dossier Inbox
Mailbox Accounts
Gorgias
Inbox
lossyDossier Inbox group inboxes (e.g. [email protected]) map to Gorgias Inbox configurations. We export the mailbox name and associated email address and configure them as a routing destination in Gorgias during setup. Customers with multiple group inboxes receive corresponding Inbox records in Gorgias.
Dossier Inbox
Team Members
Gorgias
Agent
1:1Dossier Inbox Team Member records (name, email, role) map to Gorgias Agent records. We resolve agents by email match against the destination Gorgias workspace. Any Team Member without a matching Agent is assigned to a default agent queue for the customer admin to provision post-migration.
Dossier Inbox
Labels and Tags
Gorgias
Tag
lossyDossier Inbox conversation labels map to Gorgias Tags. We export all label assignments per conversation and create corresponding Tag records in Gorgias during migration. If a label name contains characters not supported by Gorgias tag naming, we sanitize to alphanumeric and hyphens. The customer chooses whether to apply tags on import or defer tagging for post-migration review.
Dossier Inbox
Attachments
Gorgias
Attachment
1:1File attachments on Dossier Inbox messages are exported to cloud storage (Box, Dropbox, Google Drive, OneDrive as available from the source configuration) and re-linked in Gorgias against the corresponding Ticket Message. We handle attachment size limits by splitting oversized batches across multiple import jobs. Inline images within message bodies migrate as embedded references within the message body content.
Dossier Inbox
Chat Widget Sessions
Gorgias
Ticket (channel: live-chat)
1:1Website chat widget sessions from Dossier Inbox map to Gorgias Tickets with channel set to live-chat. These sessions are exported separately from email conversations because they carry a distinct source flag and conversation metadata (e.g. page URL, chat widget ID). We preserve the original chat start timestamp and any chat-specific attributes as custom ticket fields in Gorgias.
Dossier Inbox
Email Threads
Gorgias
Ticket (channel: email)
1:1Email conversations from Dossier Inbox Mailbox Accounts map to Gorgias Tickets with channel set to email. The original subject line becomes the Ticket subject. Thread grouping is preserved by mapping the Dossier Inbox thread ID to a Gorgias external_id field for reference and deduplication if the customer runs a subsequent delta migration.
Dossier Inbox
Conversation Metadata
Gorgias
Ticket Custom Fields
lossyDossier Inbox conversation metadata (assigned team member, label set, mailbox source, created timestamp, last updated timestamp) migrates to standard and custom fields on the Gorgias Ticket. We map created_at to Ticket created_at and updated_at to a custom timestamp field if the customer requires full audit history in the destination.
Dossier Inbox
Internal Notes
Gorgias
Ticket Internal Note
1:1If Dossier Inbox stores internal note threads within a conversation, we identify them by sender matching an internal team member and export them separately. Internal notes import into Gorgias as Ticket internal messages that are visible to agents but hidden from customers. We flag any conversation containing internal notes for explicit review during scoping.
Dossier Inbox
Slack Integration (routing reference)
Gorgias
Slack Integration (rebuild)
lossyDossier Inbox integrates with Slack for notification routing. This configuration does not migrate because it is a platform-specific integration. We deliver a written inventory of the Slack channels and notification rules configured in Dossier Inbox so the customer's admin can rebuild equivalent routing in Gorgias using the Gorgias-Slack integration, which requires re-authentication and re-configuration post-migration.
| Dossier Inbox | Gorgias | Compatibility | |
|---|---|---|---|
| Conversations | Ticket1:1 | Mapping required | |
| Messages | Ticket Message1:1 | Mapping required | |
| Contacts | Customer1:1 | Mapping required | |
| Mailbox Accounts | Inboxlossy | Mapping required | |
| Team Members | Agent1:1 | Mapping required | |
| Labels and Tags | Taglossy | Mapping required | |
| Attachments | Attachment1:1 | Mapping required | |
| Chat Widget Sessions | Ticket (channel: live-chat)1:1 | Mapping required | |
| Email Threads | Ticket (channel: email)1:1 | Fully supported | |
| Conversation Metadata | Ticket Custom Fieldslossy | Fully supported | |
| Internal Notes | Ticket Internal Note1:1 | Fully supported | |
| Slack Integration (routing reference) | Slack Integration (rebuild)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Dossier Inbox gotchas
Message storage limits create billing surprises on Standard
No documented public API limits migration tooling options
Chat widget and email conversations use separate sync channels
Gorgias gotchas
AI Agent adds outcome-based fees on top of billable ticket costs
Overage billing for tickets scales nonlinearly
API rate limits restrict bulk export throughput
Agent data visibility cannot be restricted by role for GDPR use cases
Knowledge Base translations require separate API calls per locale
Pair-specific challenges
Migration approach
Discovery and export method confirmation
We audit the Dossier Inbox workspace for conversation volume, message count, attachment count, distinct mailbox accounts, team member list, and label vocabulary. We confirm the available export method (admin export, product-supported data bundle, or manual CSV extraction) and obtain the necessary admin credentials. We also verify the Gorgias workspace is provisioned, the Shopify integration is active if required, and the customer admin has created the initial Agent accounts matching the Dossier Inbox team members.
Gorgias channel and tag configuration
We configure Gorgias Inbox channels (email, live-chat) to match the source channels identified in discovery. We create Tag records corresponding to every Dossier Inbox label in the destination workspace. We configure any required Gorgias integration connections (Shopify, Slack) so that post-migration routing is ready. This step runs in parallel with export preparation and produces a written channel and tag map for customer sign-off before data extraction begins.
Data extraction and transformation
We extract conversations, messages, contacts, team members, and attachments from Dossier Inbox using the confirmed export method. Chat widget sessions and email conversations are extracted as separate datasets and tagged with a channel source flag. We parse the export bundle, deduplicate contacts by email, and build the transformation mapping for each object. Attachments are exported to temporary cloud storage and the download URLs are preserved for re-linking during import.
Sandbox import and reconciliation
We run a full import into the Gorgias sandbox environment using production-like data volume. The customer's support lead spot-checks 25-50 random Tickets against the Dossier Inbox source, verifying subject accuracy, message ordering, contact linkage, and tag assignment. We correct any mapping errors and re-run validation until reconciliation passes. This step prevents correction cycles in production and gives the customer confidence in the migration result before cutover.
Production import and delta migration
We run the production migration into the live Gorgias workspace. Contacts import first, then Conversations as Tickets with Messages attached, then Attachments re-linked to the correct Ticket Messages. We apply tags based on the label map. After the initial import window, we run a delta scan of Dossier Inbox for any conversations modified during the migration window and import those as a final delta batch. We emit row-count reconciliation reports at each phase.
Cutover and handoff
We freeze Dossier Inbox writes during cutover and run a final delta migration of any records modified during the final window. We deliver the Routing and Automation Rebuild Inventory documenting the Dossier Inbox triage behaviors that require manual rebuild in Gorgias Rules and Macros. We support a three-day hypercare window where we resolve any post-import reconciliation issues raised by the support team. We do not rebuild automations or macros inside the migration scope.
Platform deep dives
Dossier Inbox
Source
Strengths
Weaknesses
Gorgias
Destination
Strengths
Weaknesses
Complexity grading
Moderate Helpdesk migration. 4 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dossier Inbox and Gorgias.
Object compatibility
4 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Dossier Inbox: Not publicly documented.
Data volume sensitivity
Dossier Inbox doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Dossier Inbox to Gorgias migration scoping. Not seeing yours? Book a call.
Walk through your Dossier Inbox to Gorgias migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Dossier Inbox
Other ways to arrive at Gorgias
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.