Migrate your Fluent Support data

Tickets are the primary object in fs_tickets with fields for customer_id, agent_id, mailbox_id, product_id, priority, status, title, content, and source. We migrate Tickets 1:1 along with their conversation threads preserved as chronological entries in the conversation log.

Customer records are WordPress users with profile data including contact info and privacy settings. We map WordPress user IDs to the destination CRM contact schema and preserve any customer-specific custom field values attached to tickets.

Each Ticket has one or more conversation entries stored in the conversation log. We preserve the full back-and-forth between customer and agent including timestamps, author type (customer vs agent), and message content. Attachments embedded in conversations are migrated as file references.

Agents are WordPress users with assigned support roles and permissions. We map source Agent IDs to destination Agent IDs and reassign open Tickets to the correct agent at the destination during migration.

Mailboxes define incoming channel sources (email, portal) and are tied to the specific WordPress site's domain and email routing. We flag Mailbox associations as requiring manual reconfiguration at the destination since email routing rules and sender addresses are site-specific.

Fluent Support supports conditional custom fields on ticket submission forms. We extract custom field definitions and their values per ticket, but conditional visibility logic (field X shown only if field Y = value Z) cannot be transferred as structured rules and must be rebuilt in the destination system.

Workflows define sequences of tasks triggered manually or automatically by conditions. We catalog workflow definitions and identify which triggers (ticket created, status changed, agent assigned) map to the destination system's automation engine. Automated actions must be recreated manually at the destination.

Tickets carry priority fields (priority and client_priority) with values like normal, high, or low. We map these directly to destination priority fields with configurable value translation if the destination uses different labels.

Tickets can be tagged to a Product with a product_id and product_source. The product_source references a specific WordPress plugin or integration (e.g., Fluent Forms). We map product associations to the destination's product/catalog object where available, otherwise flag them as custom text.

Tickets and customers support tagging for categorization. We migrate tags as flat key-value arrays and map them to the destination's tagging system or custom property depending on what the target supports.

Fluent Support generates personal and team performance reports (Resolve Stats, Response Stats, Ticket Stats) from aggregated ticket data. These reports are computed views rather than stored records and do not export as discrete data objects. We recommend taking screenshots of key reports before migration for historical reference.

Files attached to tickets and conversations are stored in the WordPress media library or plugin-specific upload directories. We extract attachment URLs and file metadata and migrate files to the destination's storage with references updated in the conversation record.