Migrate from Heyday AI to Intercom

Heyday customer profiles, which are synced from connected e-commerce platforms, map to Intercom Contacts. We extract customer records via Heyday's admin export or Hootsuite's backend where API access is available, then map each profile to the Intercom Contact schema using email as the dedupe key. Custom customer properties built inside Heyday that do not map to standard Intercom Contact attributes migrate as custom attributes. During import, phone number validation in Intercom should be disabled in workspace settings (Settings > Your Workspace > People Data > Phone) if any source records contain non-standard formats.

Heyday conversation threads and message history map to Intercom Conversations, but this is the highest-risk object in this migration. Heyday does not publish a standalone public API for conversation export. We coordinate with Hootsuite's backend team or use the customer's Heyday admin UI to extract whatever message history is available manually, then structure it as conversation records in Intercom. If Hootsuite support is unwilling or unable to assist, we flag this as a data-loss risk and migrate only the most recent N months of accessible conversations. The customer should request a data export from Hootsuite before migration scoping begins.

Heyday product catalogue data pulled from e-commerce integrations maps to an Intercom Custom Object named Product. Heyday stores product references rather than the product data itself, so the primary migration goal is preserving product IDs, names, SKUs, and prices in a form that Intercom's Custom Actions can retrieve at conversation time. Note that Intercom Custom Objects are primarily accessible within bot flows, not visible in standard filters, reports, or the Inbox view without a bot or custom action referencing them.

Heyday order-tracking queries rely on e-commerce platform integrations rather than holding order data natively. We migrate order references and identifiers as an Intercom Custom Object named Order, with a lookup relationship to the related Contact. This allows Intercom's Fin AI Agent to surface order context during conversations when configured with a Custom Action that fetches order status from the customer's e-commerce platform API. The order data itself stays in the e-commerce system; we map the reference and link.

Heyday human agent accounts and assignment rules can be listed via Hootsuite admin APIs where accessible. We map agent identities to Intercom Admins and Agents, resolving by email match. Intercom assigns roles (admin, agent, teammate) during provisioning. Any Heyday agent without a matching Intercom user goes to a reconciliation queue for the customer's admin to provision before conversation assignment migration begins.

Conversation tagging schemas used in Heyday map to Intercom Tags. Tag names and hierarchies vary by Heyday implementation, so we extract the full tagging convention during discovery, map each tag to an equivalent Intercom Tag, and flag any tags that represent routing or SLA priority (which map to Intercom's Team or Inbox assignment rather than a Tag). Tags used for conversation classification in Heyday should be reviewed against Intercom's conversation states and routing rules post-migration.

Heyday connects to 20+ e-commerce and social messaging apps via its integration layer. During migration we identify which integrations are active and document their equivalents in Intercom. E-commerce connectors map to Intercom Custom Actions that call the platform API directly. Social messaging channels (WhatsApp, Instagram Direct, Facebook Messenger) map to Intercom's native channel integrations, which require reconfiguration rather than data migration.

Heyday FAQ automation flows and keyword triggers are configured inside Heyday's conversational flow builder and are not exposed via a public API. We document every observed automation rule, keyword trigger, and routing condition during the discovery phase as a written specification. These specifications are handed off as input to the customer's team for rebuilding in Intercom's Fin AI Agent knowledge base and workflow rules. The Heyday FAQ content itself (the answers the bot surfaced) should be extracted as text and imported as Intercom Help Center articles.

Heyday bot training data and intent configurations cannot be exported programmatically. We extract any bot response templates, FAQ answer text, and knowledge-base content visible in the Heyday admin UI and structure it as Intercom Help Center articles and Fin AI Agent resources. The customer reviews and curates this content for accuracy before publishing, since the content may reference Heyday-specific terminology or Hootsuite-specific branding that requires updating for Intercom.

Heyday conversation summary fields such as resolution status, conversation duration, agent assignment history, and customer satisfaction ratings migrate as Intercom Conversation Part records of type 'note' attached to the relevant Conversation. Intercom's standard conversation data model preserves these attributes natively, but any custom metadata from Heyday (such as order reference or shipping status flags) requires custom conversation attributes that we create during schema setup.