Migrate your Chatwoot data

Conversations are the core unit in Chatwoot. Each has a status (open/resolved/pending), priority, assignee, team, inbox, and labels. We migrate conversations as complete objects including their message arrays, timestamps, and custom_attributes. Round-robin assignment logic must be explicitly re-applied at the destination.

Contacts store name, email, phone, and custom_attributes. Standard attributes auto-update; custom ones require schema mapping. We export all Contact records and re-import them, preserving any Contact Labels as tag arrays on the destination record.

Messages belong to Conversations and carry content, sender_type (agent/customer), attachments, and private notes. We preserve message order by created_at timestamp. Attachments are stored as URLs and must be re-hosted or linked depending on destination storage capabilities.

Inboxes represent channels (Website Live Chat, Email, WhatsApp, Facebook, Twitter, API). Channel configuration (webhook URLs, page tokens, WhatsApp templates) does not transfer between platforms. We migrate inbox structure but channel credentials must be reconfigured at the destination.

Agents are user accounts tied to email, name, role, and availability status. Roles are limited on lower tiers. We map Agents to destination user accounts and preserve role assignments. Passwords cannot be exported and must be reset at the destination.

Teams are available only on Business and Enterprise tiers. They group agents and route conversations. If the source is on Hacker or Startups, no Teams exist to migrate. We create matching Team structures and reassign agent-team memberships at the destination.

Labels are string tags applied to Conversations. They are simple key-value records. We export the full label taxonomy and re-apply labels to migrated conversations. Label color and display metadata are preserved where supported by the destination.

Custom Attributes attach to Conversations or Contacts and can be text, number, dropdown, or checkbox. Schema must be created at the destination before import. Values are migrated as raw data; downstream automation rules referencing them must be rebuilt.

Canned Responses are pre-written reply templates with shortcut codes. We export the full set including content and shortcut triggers. They map cleanly to most destination platforms as template or snippet objects.

Automation Rules trigger on Events (conversation created/updated) and execute Actions (assign, label, send email). They require Business tier or higher. Rule logic is platform-specific and must be rebuilt at the destination; we export the rule definitions as documentation for manual reconstruction.

Help Center Articles are published knowledge base content. This feature requires Startups tier or higher. Articles have title, body (markdown), category, and locale. We export the full article tree and re-publish it, though category structure may require manual recreation depending on destination schema.

SLA Policies define first-response and resolution time targets per priority level and are Enterprise Edition only. We export policy definitions and compliance metrics but cannot migrate the live SLA clock state. SLA alerts and business-hours configuration must be reapplied manually.

Integrations include Slack, Webhooks, and third-party bots. Webhook URLs, Slack channel mappings, and bot tokens are credentials-bound and will not function at the destination. We document integration configurations so they can be re-entered manually at the destination.

Reports (CSAT, conversation metrics, agent performance) are derived data calculated at query time from conversation and message records. We do not export report snapshots. The underlying Conversations and Messages are migrated so reporting can be regenerated at the destination from historical data.