Migrate from Euphoric.ai to Intercom

Euphoric.ai Conversations migrate as Intercom Conversations preserving full message thread chronology, timestamps, sender identity (agent vs. customer), and channel origin. We map the Euphoric conversation status (Open, Snoozed, Closed) to Intercom's Open, Snoozed, and Closed states. AI-generated Summaries from Euphoric attach as read-only internal notes on each conversation because they are locked metadata with no edit path in the source. If Intercom auto-generates Fin Summaries post-migration, conversations may carry duplicate summarization, which we flag before cutover.

Euphoric.ai Contact records (name, email, phone, custom attributes) map to Intercom Users. Email address serves as the dedupe key. Phone numbers migrate as the contact's phone attribute; if Intercom's phone validation is enabled in the destination workspace, we request customers disable it in Settings > Your Workspace > People Data > Phone before migration to prevent invalid phone numbers from blocking contact import. Custom contact attributes from Euphoric migrate as custom attributes on Intercom Users.

Euphoric.ai Knowledge Base Articles map directly to Intercom Help Center Articles, preserving article body, section and collection categorization, and internal and external visibility flags. We extract multilingual article translations and import them into the equivalent Intercom collection structure. During migration, we rewrite all internal cross-links between articles to match Intercom's URL structure so that hyperlinks within migrated articles remain functional in the destination help center.

Euphoric.ai Labels (Open, Snoozed, Closed, and any custom labels) migrate as Tags in Intercom. Tags apply to migrated conversation threads preserving the full Euphoric label taxonomy. We carry the complete label vocabulary into Intercom so that reporting and filtering by tag reflects the original categorization without requiring agents to relearn a new taxonomy.

Euphoric.ai Assignees (agent IDs on conversations) map to Intercom Teammates by email address lookup. If a destination Teammate record does not exist for a given Euphoric assignee, we land the conversation as Unassigned and flag it in the reconciliation report. The customer's admin provisions missing Teammates in Intercom before the production migration phase begins.

Euphoric.ai Response Templates migrate as Saved Replies in Intercom. We export template name, body content, and channel filter applicability and deliver them as a reference list for the customer's admin to recreate in Intercom's Saved Replies UI. The conditional logic around auto-apply versus manual-insert does not transfer because Intercom's Saved Replies operate as operator-inserted content without a native auto-apply trigger equivalent; any automation around template usage must be rebuilt as an Intercom Rule or Custom Action.

Euphoric.ai Inboxes (tier-gated at 1, 5, or 20) map to a combination of Intercom Inbox Teams and Channels. We normalize multi-inbox Euphoric configurations by collapsing inbox boundaries into Tags to preserve channel origin, while mapping the routing structure to equivalent Intercom Inbox teams. Teams that used one Euphoric inbox per channel (Email Inbox, WhatsApp Inbox, Phone Inbox) will find Intercom's channel-first model provides more flexible routing without the tier-based inbox ceiling.

Euphoric.ai Call Logs are Pro-tier-only ($45/seat) and represent call transcripts and disposition data from Built-in Phone Support. Intercom's standard tiers do not include native call logging; Intercom Voice is a separate capability. We migrate available Call Log records as custom attribute notes on the associated conversation in Intercom. Teams that rely on call recording and call analytics should evaluate Intercom Voice or a telephony integration partner before migration begins.

Euphoric.ai AI-generated conversation summaries are locked metadata outputs that cannot be edited or deleted in the source. We attach them as read-only internal notes on migrated Intercom conversations so that agents retain the AI-provided context without requiring re-reading of full thread history. Intercom generates its own AI Summaries on conversations through Fin, which may result in two summary layers on the same conversation. We document this duplication for the customer's admin to decide whether to suppress Fin summarization on historical imports.

Euphoric.ai reporting data is aggregate and ephemeral, calculated on demand from Conversations and Call Logs rather than stored as independent records. No report configuration exports exist. We deliver a written description of the existing Euphoric reporting structure (metrics, date ranges, filters) as a reference for the customer's admin to configure equivalent Intercom Inbox reports and Fin AI outcome dashboards post-migration.