Migrate Your Email Support

Converge Team

• Updated March 12, 2026

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

Migrating Email Support from HappyFox

HappyFox handles email through forwarding: you set up your email provider (Gmail, Outlook, or custom SMTP) to forward incoming messages to your HappyFox mailbox address (typically [email protected]). HappyFox supports unlimited mailboxes across all plans, with each mailbox mapped to a category for ticket routing. Migration means redirecting that email flow to your new platform.

Step 1: Document Your Email Configuration

In HappyFox, go to Manage >> Channels >> Email and note all configured mailboxes. Record which email addresses forward to which HappyFox category (e.g., support@, billing@, sales@). Check if you've configured DKIM authentication for your custom domain (available on Team+ plans) and whether you're using custom email addresses for outgoing replies. Also note any email notification rules or auto-responders you've set up.

Step 2: Choose Your Email Method in the New Platform

Depending on your new platform, you'll typically have two options: Gmail integration (for Google Workspace users) via service account with domain-wide delegation, or custom domain email via inbound routing services like Mailgun. If you're currently using Google Workspace with HappyFox's forwarding, the Gmail integration path is simpler — no forwarding rules needed.

Step 3: Update Forwarding Rules

Go to your email provider (Gmail, Outlook, or your mail server) and update the forwarding rules that currently point to @yourcompany.happyfox.com. Point them to your new platform's inbound address instead. If using custom domain email with MX records, update the MX records to route through your new platform's email service. DNS changes typically propagate within minutes to hours.

Step 4: Migrate Templates and Canned Responses

HappyFox's Canned Actions (macros) combine template responses with ticket actions. Export or screenshot your canned action text and recreate them as quick replies in your new platform. If you use ticket templates for standardized ticket creation, document those as well. HappyFox's email notification templates (under Manage >> Notifications) should also be noted so you can recreate similar customer-facing email responses.

Step 5: Handle In-Flight Conversations

After redirecting email forwarding, existing open tickets in HappyFox will stop receiving new replies. Resolve or close active tickets in HappyFox before the cutover, or plan a parallel period where you check both platforms. Customer replies to old HappyFox ticket notification emails will still go to HappyFox unless you update the reply-to headers in your new platform to match the addresses customers already have in their email threads.

Note: If you're using HappyFox's multi-brand helpdesk (Team plan: 5 brands, Pro: 15 brands, Enterprise: 25 brands), each brand may have separate email configurations and custom domains. Plan the migration brand by brand to avoid disruption across all support addresses simultaneously.