Export Your Data
Converge Team
Part of the Reamaze migration guide
Learn how to export your customer data, conversation history, and contacts from Reamaze before migrating to a new platform.
How to Export Your Data from Re:amaze
Re:amaze provides a CSV export for customer contacts through its Contacts tab and a REST API for retrieving conversations, messages, articles, and response templates. There is no single "download everything" button — you'll use different methods depending on the data type.
Step 1: Export Customer Contacts (CSV)
In your Re:amaze dashboard, click the Contacts tab in the right-hand navigation menu. To export a subset, click "Filter Contacts" at the top — you can filter by country, tags, or custom fields. Once your filter is set (or skip filtering to export everything), click "Export Contacts." Re:amaze processes the export as a background job and sends you an email notification when the CSV file is ready to download. The CSV includes names, email addresses, phone numbers, and any custom data fields you've collected. Contacts in Re:amaze are account-scoped (not brand-scoped), so this export covers contacts across all brands in your account. This feature is available on all plans, including Starter. Most CSV report exports are also available from the bottom of each report page in the dashboard.
Step 2: Export Conversations and Messages (REST API)
Re:amaze's REST API provides endpoints for programmatic data retrieval. Use GET /api/v1/conversations (scoped per brand via https://{brand}.reamaze.io/api/v1/conversations) to list conversations — results are paginated at 30 per page and can be filtered by status, tag, origin (channel), and date range. Then use GET /api/v1/conversations/{slug}/messages to retrieve individual message threads, or GET /api/v1/messages to fetch all messages across conversations. Authentication uses HTTP Basic Auth with your login email as the username and your API token as the password (found in Settings → Developer → API Token). Each Re:amaze user has their own API token, and requests are rate-limited per token per minute — you'll receive HTTP 429 responses if you hit the limit. Unlike contacts, conversations are brand-scoped, so you need to query each brand's subdomain separately. For large exports, build a script that paginates through all conversations and saves the JSON responses.
Step 3: Export Response Templates
Re:amaze's API exposes response templates (saved replies) via GET /api/v1/response_templates. The endpoint supports keyword search and pagination, so you can retrieve your entire template library programmatically. Export these so you can recreate them as Quick Replies on your new platform. If you have a large library of canned responses, the API is significantly faster than copying them one by one from the Re:amaze dashboard.
Step 4: Export FAQ/Knowledge Base Articles
FAQ articles can be retrieved via GET /api/v1/articles (filterable by status: published, draft, or internal) and individual articles via GET /api/v1/articles/{slug}. Results include article titles, body content, status, and topic associations. Articles are scoped to specific topics within your help center, so export by topic if you want to preserve the organizational structure. If you've built an extensive help center in Re:amaze, export all articles so you can repurpose the content — either as FAQ entries in your new chat widget or as standalone documentation on a separate docs site.
Step 5: Document Workflows, Cues, and Bot Configurations
Re:amaze's Workflows (automation macros), Cues (proactive messages), and chatbot configurations (Hello Bot, FAQ Bot, Order Bot, custom bots) cannot be exported via the API or UI. Screenshot or manually document each workflow's trigger conditions and actions, each Cue's targeting rules and message text, and any chatbot conversation flows. If you trained Re:amaze's AI Agent with custom context or FAQ data, save the original source materials — the AI Agent training configuration itself isn't exportable. Contact Notes (GET /api/v1/notes) and Satisfaction Ratings (GET /api/v1/satisfaction_ratings) are exportable via the API if you need historical quality data.
Tip: Note which third-party integrations are active in your Re:amaze account (Shopify, BigCommerce, Stripe, Klaviyo, etc.) and their configurations. These connections won't transfer — you'll set up equivalent integrations on your new platform separately. Also note any custom SPF or SMTP configurations you've set up for email deliverability, as you'll need to clean up DNS records (remove include:_spf.reamaze.com) after migration.
Need the full migration guide?
This page covers export your data specifically. For the complete step-by-step migration process:
Read the complete Reamaze migration guide →Ready to try Converge?
$49/month flat. Up to 15 agents. 14-day free trial, no credit card required.
Start Free Trial