Migrate Your Email Support

Converge Team

• Updated March 12, 2026

How to migrate your email support workflows, templates, and history from Reamaze without losing data.

Migrating Email Support from Re:amaze

Re:amaze handles email through a forwarding-based system. When you create an email channel, Re:amaze assigns an address like [email protected], and you set up forwarding from your existing email provider to route messages into Re:amaze's inbox. Migrating away means redirecting that forwarding to your new platform.

How Re:amaze Handles Email

Each email channel in Re:amaze receives a unique address (e.g., [email protected]). You configure your email provider (Gmail, Office 365, GoDaddy, cPanel, Zoho) to forward incoming support emails to this address. Replies from Re:amaze are signed by @reamaze.com by default, though you can configure Custom SMTP for Gmail or Office 365 to send replies from your own domain. If you set up Custom SMTP, you'll have additional DNS records (SPF including _spf.reamaze.com) that need cleanup after migration.

Step 1: Document Your Email Configuration

Go to Settings → Email channels in your Re:amaze dashboard. For each email channel, note: which external email address forwards to it, whether Custom SMTP is enabled (Gmail or Office 365), any SPF record entries you added for Re:amaze (include:_spf.reamaze.com), and which team members are assigned as notification recipients. Also check if you've configured email-specific workflow automations that trigger on email conversations.

Step 2: Update Forwarding Rules

Go to your email provider and update the forwarding destination from Re:amaze's address to your new platform's inbound address. Gmail/Google Workspace: Settings → Forwarding and POP/IMAP → change forwarding address. Office 365: Exchange admin center → Mail flow rules → update the redirect target. GoDaddy: Email Forwarding section → update the destination. Google Groups: If using a Google Group for shared inbox, update the group's forwarding settings.

Step 3: Clean Up DNS Records

If you added Re:amaze to your SPF record (e.g., include:_spf.reamaze.com), remove it from your domain's DNS TXT records after migration to keep your SPF record clean. If you configured Custom SMTP with DKIM signing through Re:amaze, remove those DKIM DNS records as well. Your new platform will provide its own DNS requirements for email deliverability.

Step 4: Recreate Email Templates

Re:amaze's Response Templates (saved replies/canned responses) can be exported via the REST API at GET /api/v1/response_templates. Export these before canceling your account, then recreate them as Quick Replies or templates on your new platform. If you used Re:amaze's dynamic variables in templates (customer name, conversation subject, etc.), map them to your new platform's variable syntax.

Note: Email forwarding changes are typically instant for most providers. However, if you modified DNS records (SPF, Custom SMTP, DKIM), allow up to 48 hours for propagation. Consider running both platforms in parallel during this window — forward to both Re:amaze and your new platform temporarily to avoid missed emails.