Migrate your Re:amaze data

Conversations are the central ticket object in Re:amaze. Each has a subject, category, message thread, assignee, status, and timestamps. The API exposes /conversations with full message history. We migrate conversation body, author identity, timestamps, internal notes, and attachment references as separate message records.

Re:amaze contacts are customer records with name, email, and computed attributes (browser, location, last seen). The Contacts API returns all fields and supports CSV export with segment filtering. We pull contacts with their full attribute set including computed properties and merge in custom field values from the embedded forms data.

Custom fields are created within the embed builder (Contact Form, Shoutbox, Lightbox) and their values are stored as contact attributes. There is no separate Custom Field definition API, so we discover them by reading a sample of contact records and extracting their keys. Value mapping is required since dropdown field options in Re:amaze may differ from the destination schema.

Tags are created by admins and applied by agents on conversations. There is no tag hierarchy or tag-specific API. We export all tags as a flat string list per conversation and re-create them at the destination, preserving any naming conventions the team uses for automation triggers.

Quick Answers are canned response templates grouped by category. They have a title, content body, and optional shortcode. We export the full content including any HTML formatting, then recreate the category structure at the destination helpdesk using its canned response or template feature.

Re:amaze FAQ articles are searchable, category-grouped, and embeddable. The API surfaces articles with their content, category, and publish status. We migrate articles preserving the category hierarchy and re-publish them at the destination using its KB or article feature.

Re:amaze multibrand lets a single account host multiple brands with separate inboxes, contacts, and reporting. Each brand has a unique subdomain. We scope each migration pass to one brand via the brand-scoped API endpoint. If the destination does not support multibrand natively, we create separate workspaces or tag records by brand.

Agents have a name, email, role (admin, agent), avatar, and availability status. We export all agent profiles including their role. We map agent emails to users at the destination and preserve role-based permissions as closely as the destination schema allows.

Re:amaze integrations with Shopify, BigCommerce, Magento, and other e-commerce platforms are configured in-app and store their connection state server-side. Integration credentials, webhook URLs, and OAuth tokens cannot be exported and must be re-configured manually at the destination platform.

Conversation messages and contact profiles may include file attachments. We export attachment URLs and metadata. Where Re:amaze stores attachments behind signed URLs or on their CDN, we download and re-upload to the destination's attachment storage. File size and type restrictions at the destination may require archiving older large files.