Helpdesk migration

Migrate from Dossier Inbox to Gorgias

Field-level mapping, validation, and rollback between Dossier Inbox and Gorgias. We move data and schema; workflows are rebuilt natively in Gorgias.

Dossier Inbox logo

Dossier Inbox

Source

Gorgias

Destination

Gorgias logo

Compatibility

67%

8 of 12

objects map 1:1 between Dossier Inbox and Gorgias.

Complexity

CModerate

Timeline

1-2 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Dossier Inbox logo

Dossier Inbox

What's pushing teams away

  • Teams outgrow the message storage limits and find the per-user, per-message pricing model becomes expensive as their support volume increases.
  • The platform is designed for small teams, so organizations scaling beyond 5–10 users report that inbox management features lack the routing, SLA, and reporting tools available in dedicated helpdesk platforms.
  • Limited public documentation and API details make it difficult for technical teams to self-serve integrations, automation, or data extraction without vendor involvement.

Choosing

Gorgias logo

Gorgias

What's pulling them in

  • Shopify-native integrations pull order details, shipment status, and return data directly into the ticket view, eliminating the need for agents to switch between apps.
  • Unlimited user seats mean growing support teams do not trigger billing changes; pricing scales only on billable ticket volume.
  • AI Agent automates responses to high-volume queries like order status and returns, measurably reducing the number of billable tickets each month.
  • Omnichannel inbox consolidates email, live chat, Facebook, Instagram, WhatsApp, SMS, and voice into a single threaded view.
  • SOC 2 Type II certification and GDPR-aligned data handling satisfy enterprise procurement requirements for customer support platforms.

Object mapping

How Dossier Inbox objects map to Gorgias

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

maps to

Gorgias

Ticket

1:1
Mapping required

Dossier 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

maps to

Gorgias

Ticket Message

1:1
Mapping required

Individual 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

maps to

Gorgias

Customer

1:1
Mapping required

Dossier 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

maps to

Gorgias

Inbox

lossy
Mapping required

Dossier 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

maps to

Gorgias

Agent

1:1
Mapping required

Dossier 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

maps to

Gorgias

Tag

lossy
Mapping required

Dossier 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

maps to

Gorgias

Attachment

1:1
Mapping required

File 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

maps to

Gorgias

Ticket (channel: live-chat)

1:1
Mapping required

Website 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

maps to

Gorgias

Ticket (channel: email)

1:1
Fully supported

Email 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

maps to

Gorgias

Ticket Custom Fields

lossy
Fully supported

Dossier 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

maps to

Gorgias

Ticket Internal Note

1:1
Fully supported

If 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)

maps to

Gorgias

Slack Integration (rebuild)

lossy
Fully supported

Dossier 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.

Gotchas + challenges

What specifically takes care here

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 logo

Dossier Inbox gotchas

High

Message storage limits create billing surprises on Standard

High

No documented public API limits migration tooling options

Medium

Chat widget and email conversations use separate sync channels

Gorgias logo

Gorgias gotchas

High

AI Agent adds outcome-based fees on top of billable ticket costs

High

Overage billing for tickets scales nonlinearly

Medium

API rate limits restrict bulk export throughput

Medium

Agent data visibility cannot be restricted by role for GDPR use cases

Low

Knowledge Base translations require separate API calls per locale

Pair-specific challenges

  • No publicly documented API means export relies on product-supported methods

    The research did not surface a publicly documented REST API for Dossier Inbox with published endpoints or rate limits. Without a confirmed API, data extraction relies on product-supported export methods available within the platform, which may require the customer's admin credentials. We confirm export capabilities during discovery scoping and use the highest-permission method available. If the export produces CSV or JSON bundles, we parse and transform them before importing into Gorgias via the Gorgias REST API.

  • Chat widget and email conversations use separate sync channels

    Website chat widget sessions and email conversations are distinct source channels in Dossier Inbox. If they are exported as separate bundles or require separate access credentials, we handle them as independent export jobs. We apply channel-specific mapping rules in Gorgias so that chat sessions land in live chat queues and emails in email queues rather than mixing thread types. Mixing channels during import would cause routing confusion and duplicate customer records.

  • Message storage cap may limit export completeness

    The Dossier Inbox Standard plan caps messages at 2,000 across the organization, with overage charges that apply per user. If the customer's account is at or near the cap, some messages may not be accessible for export. We scope the full message count during discovery and flag any conversations that fall outside the accessible window. The customer may need to upgrade the Dossier Inbox plan temporarily or accept that archived messages beyond the cap cannot be migrated.

  • Dossier Inbox labels do not automatically exist in Gorgias

    Dossier Inbox conversation labels (e.g. billing, shipping, refund) need to be recreated as Tags in Gorgias before migration runs. We export the label vocabulary and create corresponding Tag records in Gorgias during the pre-migration setup phase. If a label name exceeds Gorgias tag length limits, we sanitize to a compatible format and document the mapping for the customer's review.

  • Automations, routing rules, and macros do not migrate

    Dossier Inbox has no automation builder or macro system to migrate. Gorgias macros, automated rules, and routing configurations require manual rebuild post-migration. We deliver a written inventory of the triage behaviors that existed in Dossier Inbox (label assignments, team routing patterns) so that the customer's admin can rebuild equivalent logic in Gorgias Rules and Macros. This document is included in the standard migration handoff package.

Migration approach

Six steps for a successful Dossier Inbox to Gorgias data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Dossier Inbox logo

Dossier Inbox

Source

Strengths

  • Consolidates Gmail, Outlook 365, and website chat into a single shared team inbox.
  • Standard plan includes file sync with Box, Dropbox, Google Drive, and OneDrive at per-user pricing.
  • Integrations with Slack, Asana, and HubSpot provide cross-tool workflow connectivity for small teams.
  • Per-conversation labeling and team member assignment support basic triage workflows.

Weaknesses

  • Message storage is capped on Standard, with overage charges that scale per-user, which can surprise growing teams.
  • No public API documentation found in the research, limiting self-service migration and automation options for technical teams.
  • Designed for small teams, so enterprise features such as SLA tracking, advanced routing rules, and multi-brand support are absent or limited.
Gorgias logo

Gorgias

Destination

Strengths

  • Shopify and BigCommerce integrations surface order, return, and shipment data natively inside every ticket.
  • Unlimited agent seats remove per-user licensing friction as support teams grow.
  • AI Agent reduces billable ticket volume through automated resolution of high-frequency queries.
  • SOC 2 Type II certified with GDPR-aligned data handling for enterprise procurement readiness.
  • Omnichannel inbox aggregates email, live chat, Facebook, Instagram, WhatsApp, SMS, and voice into a single threaded view.

Weaknesses

  • Ticket-volume pricing with overage fees creates unpredictable monthly costs during seasonal traffic spikes.
  • Custom reporting is shallow; raw event-level data export for BI tooling is not natively supported.
  • Knowledge Base, Macros, and Rules lack simple export tooling, making competitive migrations complex.
  • GDPR compliance limitations mean customer data cannot be hidden from agents by role, blocking use by teams with freelance staff.
  • Performance and glitch reports emerge in G2 reviews at higher ticket volumes.

Complexity grading

How hard is this migration?

Moderate Helpdesk migration. 4 of 7 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Dossier Inbox and Gorgias.

  • Object compatibility

    C

    4 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Dossier Inbox: Not publicly documented.

  • Data volume sensitivity

    B

    Dossier Inbox doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Dossier Inbox to Gorgias migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Dossier Inbox to Gorgias data migrations

Answers to the questions buyers ask most during Dossier Inbox to Gorgias migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between one and two weeks for workspaces under 5,000 conversations and 10,000 messages with no complex label rewriting. Migrations with higher message counts (over 50,000 records), attachment-heavy threads, or multiple mailbox accounts requiring separate channel configuration move to three to five weeks because of export parsing time, tag vocabulary setup, and the sandbox reconciliation cycle.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Dossier Inbox.
Land in Gorgias, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day