Migrate Your Email Support

Converge Team

• Updated March 12, 2026

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

Migrating Email Support from Dixa

Dixa uses a forwarding-based email system. You create email addresses ending in @email.dixa.io and configure your company email to forward to those addresses. Migrating away means redirecting that forwarding to your new platform.

How Dixa Handles Email

Dixa's email setup works in two parts. First, you create an email address in Settings → Email → Add email, which generates an identifier like [email protected]. You can optionally add a sender name and signature. Second, you set up forwarding from your actual company email (e.g., [email protected]) to this Dixa address. For outbound emails using your own domain, Dixa requires DNS configuration — at minimum a DKIM record, with SPF and DMARC recommended. After DNS setup, you must contact Dixa Support to verify the domain and update sender email addresses. Dixa also supports SPF alignment for organizations with strict DMARC policies.

Step 1: Document Your Email Configuration

Before switching, go to Settings → Email and note: which Dixa email addresses are active, which company addresses forward to them, any custom email domains you've configured (check Email domains section), email signatures, email templates, and email flows (routing logic for incoming emails). Also document any email-specific automations you've built in Dixa's automation system.

Step 2: Set Up Email on Your New Platform

On your new platform, configure your email channel. If using Converge, you have two options: Gmail integration (via service account with domain-wide delegation — no DNS changes needed) or custom domain email (via Mailgun inbound routing, which requires MX record updates). Recreate your email signatures as part of the setup.

Step 3: Redirect Forwarding

Update your email forwarding rules to point to your new platform instead of @email.dixa.io. This is the migration "switch" — once forwarding changes, new emails go to your new platform. If you configured DNS records for Dixa (DKIM/SPF), you can remove the Dixa-specific records and add any new DNS records required by your new platform. DNS changes can take up to 24 hours to propagate.

Step 4: Migrate Templates and Workflows

Dixa's email templates and quick responses don't export automatically. Copy each template's content and recreate them in your new platform. In Converge, use Quick Replies with variable support for personalized responses. Also recreate any email-specific routing logic — Dixa uses email flows for routing, while Converge uses auto-routing rules.

Tip: Consider running both platforms in parallel for a few days. Keep Dixa active to handle replies on existing email threads, while new incoming emails route to your new platform. This prevents customers from losing context mid-conversation.