Migrate from REVE Chat to HubSpot Service Hub

REVE Chat Conversations map to HubSpot Tickets as the destination record. The conversation transcript (all customer and agent messages with timestamps) migrates as threaded Ticket Replies in HubSpot's conversation inbox. Subject line is derived from the first customer message or a configurable subject template. Status, priority, and assignee migrate from the linked REVE Chat Ticket record. If the REVE Chat account has conversations without a corresponding Ticket, we create a standalone Ticket with the conversation content preserved.

Each REVE Chat Chat Session generates a visitor interaction record with source channel, device info, page context, and outcome. Session metadata migrates as custom ticket properties on the linked HubSpot Ticket: session_source, device_type, page_url, and session_outcome. This preserves the session context that agents used for routing and prioritization in REVE Chat without creating duplicate records in HubSpot.

REVE Chat Tickets map directly to HubSpot Tickets. Status (open, pending, resolved, closed) maps to HubSpot Ticket status values. Priority maps to HubSpot Ticket priority (low, medium, high, urgent). Assignee maps to HubSpot User via email resolution. Tags migrate to HubSpot Ticket tags. Any linked conversation in REVE Chat is preserved as the primary Ticket Replies thread. Custom fields on REVE Chat tickets migrate as HubSpot custom ticket properties of equivalent type.

REVE Chat Agent records (display name, email, role: admin, supervisor, agent) map to HubSpot Users. We resolve by email match against the HubSpot portal. Role assignments (admin, supervisor, agent) map to HubSpot User roles. The REVE Chat seat ceiling (Free=1, Starter=10, Growth=25, Enterprise=unlimited) is verified against the destination HubSpot plan during scoping; any agent count exceeding the destination plan triggers a flag before migration begins. Agents without a matching HubSpot User go to a reconciliation queue for manual provisioning.

REVE Chat Customer profiles (name, email, phone, company, custom labels) map to HubSpot Contacts. Custom labels migrate as key-value custom properties on the Contact. Chat history for each customer links to the Contact record via the migrated Ticket. If the HubSpot portal also contains Companies, the REVE Chat company field maps to the HubSpot Company lookup on Contact.

REVE Chat canned responses (saved reply templates with shortcut triggers) migrate to HubSpot Snippets in the Knowledge Library. Shortcut triggers migrate as Snippet shortcut keys. Snippets are scoped to individual users by default in HubSpot; during migration we apply a shared Snippet library configuration so the team has access without manual redistribution. Some canned response fields are plan-gated on the source side, which we verify against the source plan during scoping.

REVE Chat Departments control routing and agent assignment. We map department configurations to HubSpot Teams, preserving the routing logic as best as possible within HubSpot's team-based inbox routing. Note that REVE Chat's skill-based and department-based routing may require reconfiguration in HubSpot's inbox settings post-migration.

Chatbot flows built in REVE Chat's Visual Flow Builder include trigger conditions, decision branches, and response actions. The Visual Flow Builder uses proprietary logic that cannot be exported in a machine-readable format compatible with HubSpot. We do not migrate chatbot flows as code. We deliver a written inventory of every active chatbot flow with its trigger, conditions, decision tree, and response actions, which the customer's admin uses to rebuild in HubSpot's workflow builder or Breeze AI. This inventory is produced during the scoping phase.

REVE Chat reporting is conversation-centric (response time, agent activity, session counts). HubSpot Service Hub reporting is ticket-centric (CSAT, first response time, resolution time by pipeline and team). These are different analytical models with no direct field mapping. We deliver a written inventory of every REVE Chat report with its metrics and dimensions, which the customer's admin rebuilds as HubSpot ticket reports. We do not migrate reports as code or as configured dashboard objects.

Files and images shared within REVE Chat conversations are exported alongside transcript records. Attachment URLs pointing to REVE Chat storage are preserved as links within the migrated Ticket Replies. Customers should confirm whether they want to download and re-upload files to HubSpot's file storage or retain the REVE Chat-hosted URLs. If re-upload is required, we flag the file count and total size during scoping and adjust the migration scope accordingly.

Voice bot and audio call records in REVE Chat (session subtype with duration, direction, and outcome) map to HubSpot Call records via the HubSpot Conversations API. We migrate call metadata (duration, direction, outcome) as Call object properties. Note that the voice channel requires separate infrastructure validation in HubSpot if the customer uses REVE Chat's native voice capability; we confirm voice channel status during scoping and flag whether a HubSpot calling plan add-on is required.

Social channel messages (Facebook Messenger, Viber, WhatsApp, Telegram) migrate as HubSpot Conversations in the social channel inbox. Channel source is preserved as a conversation property. Note that Instagram, WhatsApp, Viber, and Telegram may be add-ons or tier-gated on REVE Chat Starter, and HubSpot's Conversations inbox supports Facebook Messenger and Instagram Direct natively with additional channels via integrations. We confirm channel availability against both platforms during scoping and flag any channel records that may not transfer to HubSpot's supported channel set.