Migrate from Heyday AI to HubSpot Service Hub

Heyday Customer profiles map to HubSpot Service Hub Contacts. We extract customer identifiers, email addresses, phone numbers, and any custom profile properties from Heyday's admin interface or connected e-commerce platform exports. Heyday-specific custom properties are preserved as HubSpot custom contact properties so the customer has a complete audit trail. If Heyday Customer records include loyalty tier or order history flags sourced from e-commerce integrations, these map to HubSpot contact properties or a custom Contact Object.

Heyday pulls product catalogue data from connected e-commerce integrations rather than holding products natively. We extract the product references visible in Heyday's order-tracking and FAQ responses and map them to HubSpot Products if the customer licenses Sales Hub or CRM Pro, or as custom Contact properties or a Product Custom Object if Service Hub is the primary destination. Product-specific attributes (SKU, price tier, category) are preserved as custom fields.

Order tracking queries in Heyday resolve against connected e-commerce platforms rather than Heyday holding order data natively. We preserve order reference numbers, customer order IDs, and order status values as HubSpot contact properties or as records in a custom Order object. These references enable support agents to look up order context without accessing the original e-commerce platform directly from HubSpot.

Heyday human agent accounts and assignment rules map to HubSpot Service Hub Users. We extract agent names, email addresses, and any Heyday-specific roles (bot manager, escalation handler, social inbox responder) via Hootsuite admin APIs where accessible. Agent roles map to HubSpot User roles and team assignments. A reconciliation queue identifies any Heyday agent without a HubSpot User match for admin provisioning before the user import phase.

Heyday conversation tagging schemas vary by implementation and may include channel-specific labels, intent tags, or priority flags. We extract the full tagging taxonomy from Heyday and map it to HubSpot contact properties as multi-select picklist fields. Tags used for content classification map to HubSpot Topics with TopicAssignment records. The customer selects the tag strategy during scoping, and tag hierarchies are flattened to single-level picklists in HubSpot.

Historical conversation threads from Heyday cannot be exported via a documented public API and require manual extraction or Hootsuite backend coordination. Where conversation data is accessible, we map individual conversation threads to HubSpot Tickets, with the original messages preserved as internal Ticket notes or comments. Channel metadata (social channel, message timestamp, customer identifier) is preserved as custom Ticket properties. If conversation export is not feasible, we document the data boundary and advise archiving at the source.

Heyday connects to 20+ e-commerce platforms and social channels. We audit the active integrations and map them to HubSpot equivalents: Shopify, WooCommerce, and BigCommerce map to HubSpot native e-commerce integrations or Shopify integration connectors; social channels (Facebook Messenger, Instagram, WhatsApp) map to HubSpot Social Inbox channels. We deliver a written integration inventory documenting which channels are active in Heyday and their HubSpot equivalents for the customer's admin to reconnect.

Heyday FAQ automation flows, keyword triggers, and routing logic are configured inside the conversational flow builder and are not exposed as data. These do not migrate as code. We perform a discovery session to document every active automation flow with its trigger conditions, decision branches, and actions, and deliver a written automation inventory specifying the recommended Breeze Agent conversation design or HubSpot workflow equivalent. The customer's admin rebuilds these in HubSpot Service Hub post-migration.

Heyday's trained bot responses and knowledge base used for FAQ deflection cannot be exported as structured data. We document the FAQ topics, keywords, and response logic visible in Heyday's bot builder during discovery and deliver a specification for rebuilding them as Breeze Agent topics or HubSpot Knowledge Base articles. The customer's support team reviews and refines the knowledge base content in HubSpot post-migration.

Heyday's social messaging channel connections (Facebook Messenger, Instagram Direct, WhatsApp Business, social DMs) map to HubSpot Social Inbox channels. We identify which social channels are active in Heyday, map them to HubSpot's equivalent social tool connections, and deliver a channel reconnection checklist for the customer's admin. Direct message history that is Heyday-specific requires separate export from the social platform itself.

Heyday live chat and video shopping session metadata (customer identifier, agent assigned, session timestamp, resolution status) maps to HubSpot Conversations inbox records. Individual message content from live chat sessions requires extraction from Heyday's admin interface where accessible, and maps to HubSpot Conversation thread messages. Video shopping session metadata maps to custom Conversation properties or a custom object.

Heyday custom customer properties built inside the platform (beyond standard name, email, phone) map to HubSpot custom Contact properties. We perform schema discovery against the customer's Heyday instance where Hootsuite admin API access is available, extract the full property list, and create matching custom properties in HubSpot before Contact migration. Properties without a clear HubSpot equivalent are flagged for the customer to decide whether to keep, archive, or drop.