Migrate your REVE Chat data

The primary object in REVE Chat. We export full conversation transcripts including timestamps, agent attribution, customer messages, and system events. Chat history retention varies by plan: 90 days on Starter, 365 days on Growth, unlimited on Enterprise. We flag the tier's retention window during scoping so customers can request extended history before migration if needed.

Each visitor interaction generates a session record with source channel, device info, page context, and outcome. We preserve session metadata and link sessions to the parent Conversation. Note that session limits are per-plan and a temporary buffer applies when limits are exceeded before conversations roll to live chat.

Agent records include display name, email, role (admin, supervisor, agent), and online/offline/busy status. We migrate agent profiles and preserve role assignments. The seat ceiling per plan (Free=1, Starter=10, Growth=25, Enterprise=unlimited) is flagged during scoping to prevent migration into a plan that cannot accommodate the team size.

Chatbot flows built in the Visual Flow Builder include trigger conditions, decision branches, and response actions. We export the flow logic but note that the Visual Flow Builder is a proprietary editor—destination platforms without a compatible flow builder will require manual reconstruction or approximation of the automation logic.

Saved reply templates with shortcut triggers. We migrate canned responses and their shortcut keys intact. Note that some canned response fields are plan-gated on the source side, which we verify against the plan tier before migration.

Ticket records include status (open, pending, resolved, closed), priority, assignee, tags, and linked conversation. We migrate tickets with full field fidelity and preserve links to originating conversations. REVE Chat's ticketing is secondary to the conversation stream, so ticket data density may be lower than dedicated helpdesk platforms.

REVE Chat reporting is conversation-centric (response time, agent activity, session counts) rather than ticket-centric. We export available metrics and note that cross-object reporting (e.g., ticket resolution time vs. conversation metrics) does not exist in REVE Chat and therefore cannot be reconstructed in the destination system.

Department records control routing and agent assignment. We preserve department configurations and linked routing rules so conversations continue routing correctly after migration.

Customer profiles include name, email, phone, company, custom labels, and chat history. We migrate profiles with all standard fields. Custom labels (customer labeling feature) are preserved as key-value pairs and mapped to equivalent fields in the destination system.

Files and images shared within conversations are exported alongside transcript records. We preserve attachment URLs pointing to REVE Chat's storage; customers should confirm whether they want to download assets to their own storage before migration to avoid link rot.

Voice bot and audio call records exist as session subtypes with duration, direction, and outcome. We migrate call metadata but note that the voice channel requires separate infrastructure validation in the destination platform before call history can be operational.

Social channel records are linked to Conversations and preserve message content, channel source, and customer profile. We flag that Instagram, WhatsApp, Viber, and Telegram may be add-ons on lower tiers, so channel availability in the destination platform should be confirmed during planning.