Migrate from Heyday AI to Gorgias

Heyday Conversation threads and message history are not accessible via a documented public API. We work with the customer to extract conversation data from Heyday's admin UI, which supports manual CSV or screen-based export for recent periods. Historical conversation volume, date range availability, and export completeness depend on the customer's specific Hootsuite contract and Heyday configuration. We map each conversation thread to a Gorgias Ticket, preserving the channel of origin (chat, Instagram DM, Facebook DM) as a tag, and conversation timestamps as Ticket created_at and last_message_at. We flag that Heyday conversation export completeness cannot be guaranteed without Hootsuite backend involvement and document the extraction scope in the migration manifest.

Heyday Customer profiles may be synced from connected e-commerce platforms such as Shopify, Magento, or WooCommerce. We map customer records to Gorgias Customer, preserving name, email, phone, and any e-commerce platform identifiers as external_id references. Custom customer properties built inside Heyday (such as customer tier, lifetime value, or preference flags) are mapped to Gorgias Customer attributes or stored as JSON in a custom field if the attribute does not map to a typed Gorgias field. We use email as the dedupe key during import.

Heyday pulls product catalogue data from connected e-commerce platform integrations rather than holding product data natively. We extract product references (product name, SKU, price, image URL) from Heyday's integration configuration or from the product context carried in Heyday conversation messages, and map these to Gorgias Product records. Heyday-specific product attributes or AI recommendation logic do not carry forward; we note that product data should be sourced directly from the connected e-commerce platform at the destination if completeness is critical.

Heyday Order records are references pulled from e-commerce platform integrations (Shopify, Magento, WooCommerce) used to answer order-tracking queries within the chatbot. We preserve order references (order number, status, line items, tracking information) as they appear in Heyday's conversation context and map them to Gorgias Order objects linked to the corresponding Customer. The primary source of truth for orders remains the e-commerce platform; Heyday's order context is preserved as linked reference data within Gorgias Tickets for agent visibility.

Heyday FAQ automation flows, keyword triggers, and routing logic are configured inside Heyday's conversational flow builder and are not exposed via a public API. These workflows do not migrate. We document every observed automation during the discovery phase: trigger conditions, branching logic, routing rules, FAQ response content, and escalation paths. We deliver a written Automation Rebuild Specification mapping each Heyday automation to a Gorgias Macro (for one-click agent responses) and a Gorgias Automation Rule (for ticket routing and auto-assignment). The customer's admin implements the rebuild in Gorgias settings.

Heyday FAQ automation responses are tied to specific question patterns and are not stored as standalone content objects with independent export access. We extract visible FAQ response text from Heyday's conversational flow configurations during the discovery site walkthrough, then split each FAQ response into a standalone Gorgias Help Center Article. Articles are organized by category matching Heyday's topic structure, and each article is tagged with the original automation flow name for traceability.

Heyday human agent accounts and assignment rules are managed via Hootsuite admin APIs where accessible. We extract agent identities (name, email, role, status) from Heyday's admin panel and map them to Gorgias User accounts. Heyday-specific roles such as Bot Manager or Social Team Member are mapped to the closest Gorgias role (Agent, Admin, or Supervisor) and noted in the mapping manifest. Agents without a matching email in the destination Gorgias workspace are held in a reconciliation queue for the customer's admin to provision before user assignment migration runs.

Conversation tagging schemas in Heyday vary by implementation and may include channel tags, priority flags, intent labels, and team routing tags. We extract the full tagging taxonomy from Heyday's admin configuration and map each tag to a Gorgias Tag. Tag names are preserved verbatim where they match Gorgias's character constraints; names that exceed limits are shortened and documented in the tag mapping reference. Tag hierarchies (if any exist in the customer's Heyday configuration) are flattened into a single-level tag list in Gorgias.

Heyday connects to over 20 applications including Shopify, WooCommerce, Magento, Instagram, Facebook, and other social channels. During discovery we audit every active Heyday integration and document its current configuration (auth credentials, sync scope, data flow direction). We then map each active integration to its Gorgias equivalent: the Shopify integration is replaced by Gorgias's certified Shopify app, email channels map to Gorgias IMAP/SMTP or email forwarding rules, and social channels (Instagram, Facebook) map to Gorgias's Facebook and Instagram channel integrations. We flag any Heyday integrations that have no Gorgias equivalent (such as platform-specific social listening tools) for the customer's admin to evaluate as standalone tools post-migration.

Heyday bot training data and FAQ knowledge used to power the conversational AI is not exposed as an exportable dataset. We document every trained intent, entity, and response variation observed in Heyday's bot configuration during the discovery phase and deliver this as a Bot Training Specification document. The customer's admin uses this document to populate Gorgias AI Agent's knowledge base with source content, including Help Center articles, product FAQs, return policies, and order management procedures. We do not import training data directly; the specification enables manual knowledge transfer.

Heyday provides chatbot analytics including conversation volume, deflection rate, resolution rate, and agent handling time. We extract any available reporting data from Heyday's analytics dashboard during the discovery phase, noting the metrics available and the time range covered. We map these metrics to Gorgias Reporting equivalents: conversation volume maps to Ticket count, deflection rate maps to the ratio of AI-resolved to total tickets, and agent handling time maps to First Response Time and Resolution Time reports. We deliver a Reporting Migration Summary that lists every Heyday metric and its Gorgias reporting equivalent, noting that custom Heyday analytics dashboards must be rebuilt in Gorgias Report Builder.

Heyday's channel configuration covers chat widgets embedded on the brand's website, Instagram Direct Message routing, Facebook Messenger routing, and live video shopping. We document each active channel in Heyday: the widget installation code, channel connection status, and routing rules applied per channel. We map these to Gorgias channel equivalents: the website chat widget maps to Gorgias Chat Widget (installed via JavaScript snippet), Instagram DM maps to Gorgias Instagram Channel, Facebook Messenger maps to Gorgias Facebook Channel, and email support maps to Gorgias Email Channel. Live video shopping has no direct Gorgias equivalent; we flag this for the customer's admin to decide whether a separate tool is required.