Migrate from Euphoric.ai to Gorgias

Euphoric.ai Conversations map directly to Gorgias Tickets. Each conversation's full message thread migrates as a chronological list of messages attached to the ticket. The original channel (email, WhatsApp, Telegram, Viber, voice) migrates as the ticket channel field value. The conversation created_datetime and last_message_datetime map to Gorgias created_datetime and last_message_datetime respectively. Closed, Snoozed, and Open statuses map to their Gorgias equivalents. Unassigned conversations land in the Gorgias unassigned queue for manual routing.

Euphoric.ai Contact records (name, email, phone) map to Gorgias Customer records. The contact's primary email becomes the Customer email field and serves as the dedupe key on import. Phone number migrates to the Customer phone field. Any custom fields on the Euphoric Contact (tier-dependent) map to Gorgias custom fields on the Customer object, creating or extending the schema as needed before import.

Euphoric.ai Labels (Open, Snoozed, Closed, and any custom labels) map to Gorgias Tags on the ticket. Each label applied to an Euphoric conversation generates a corresponding tag on the Gorgias ticket. Label names are preserved exactly so that tagging logic can be replicated in Gorgias Rules post-migration.

Euphoric.ai Assignee IDs resolve by email match against Gorgias User records. We extract the agent email from each assigned conversation and map to the Gorgias User with the matching email. If no matching User exists in the destination, the ticket lands in the unassigned queue and the customer provisions the user before requesting a supplemental import pass.

Euphoric.ai Shared Inboxes (tier-gated: 1 on Standard, 5 on Plus, 20 on Pro) do not map to a direct Gorgias equivalent because Gorgias uses a flat ticket queue with Views rather than inbox-level containers. We collapse each Euphoric Inbox into a tag on the ticket (e.g., tag: inbox-email, tag: inbox-whatsapp) so channel origin is preserved. The customer configures Views in Gorgias to replicate their routing logic using these tags as the filter criteria.

Call Logs migrate only for Euphoric.ai accounts on Plus ($30/seat) or Pro ($45/seat) plans. Standard Plan ($13/seat) has no call feature and zero records to migrate. We confirm the plan tier during scoping before scheduling Call Log extraction. Call records attach to the corresponding ticket timeline as internal notes with call duration, direction (inbound/outbound), and timestamp preserved. Note: Gorgias has no native phone channel, so call logs appear as historical timeline entries rather than live channel data.

EuphoricGPT-generated conversation summaries are read-only metadata in Euphoric.ai — there is no API or UI path to edit or delete them. We carry them as internal Notes on the migrated Gorgias ticket, prefixed with [AI Summary - Euphoric.ai] so agents can distinguish original AI context from Gorgias-generated content. If the customer enables Gorgias AI features post-migration, summaries may be regenerated, resulting in duplicate summarization for migrated tickets.

Euphoric.ai Response Templates (name, body content, and channel filters) migrate as a structured inventory — template name, body, and applicable channel — delivered as a CSV and JSON export. We do not create active Gorgias Macros during migration because template logic (auto-apply vs. manual insert) requires admin configuration in the destination. The customer uses the inventory to recreate Macros in Gorgias Settings > Macros. Channel filter values map to Gorgias channel-type restrictions on the macro.

Euphoric.ai Knowledge Base Articles migrate to Gorgias Help Center Articles with category structure and internal/external visibility flags preserved. Article body content migrates as HTML. We extract the article category hierarchy and recreate it as Help Center categories in Gorgias. Published articles are published in the destination; draft articles remain drafts. Articles linked to conversations for AI-assisted replies are noted in the export for the customer to re-link post-migration.

Euphoric.ai Agents (shown as Assignees on conversations) map to Gorgias Users by email resolution. Agent display names, active/inactive status, and role assignments carry over. We create a user-mapping table during scoping and flag any Euphoric.ai agent without a matching Gorgias User for the customer to provision before production migration.

Euphoric.ai Reporting is aggregate and ephemeral — calculated on demand from conversation and call data rather than stored as independent records. There are no report configuration exports, saved filters, or dashboard layouts available in the product. Historical reporting data cannot be reconstructed from migrated records alone. We deliver a written summary of the Euphoric.ai reporting structure (tickets per channel, average handle time, CSAT if available) as a reference for the customer to reconfigure equivalent reports in Gorgias Analytics.

Each message in an Euphoric.ai conversation thread (from customer and from agent) migrates as a Gorgias Message attached to the ticket. Message body, sender type (customer/agent), timestamp, and attachments migrate directly. Message ordering is preserved by timestamp so the full conversation chronology is intact on the Gorgias ticket.