Migrate Your Email Support

How do you migrate your email support from Groove?

Groove routes email through forwarding rules or a Gmail OAuth shared mailbox. Migrating means redirecting your forwarding to a new platform's inbound address, revoking Gmail OAuth access, and updating any white-label DNS records — Groove's stored conversations stay in Groove and need a separate JSON export.

The forwarding-based architecture means your customer-facing email ([email protected]) lives at Gmail, Outlook, or another provider. Groove only receives forwarded copies and sends replies through SendGrid (Valimail, 2026). Switching platforms is therefore a forwarding-rule swap, not a mailbox migration.

Two paths exist depending on your setup: forwarding from Gmail, Outlook, Google Groups, Yahoo, or cPanel, or Groove's direct Gmail OAuth shared mailbox connection. IMAP and Microsoft direct mailbox connections were retired in September 2024 — Groove pushed all customers to forwarding-only (help.groovehq.com, 2024). Document which method each inbox uses before changing anything; the disconnect steps differ for forwarding versus OAuth.

Which email providers does Groove support?

Groove supports forwarding from Gmail, Outlook (Microsoft 365), Google Groups, Yahoo, GoDaddy, Zoho, and cPanel-hosted email, plus a direct Gmail OAuth integration for shared mailboxes (help.groovehq.com, 2024). IMAP and direct Microsoft 365/Outlook mailbox connections were deprecated in September 2024.

The forwarding model is identical across providers: each Groove shared inbox gets a unique address ([email protected]), and you configure your mail provider's native forwarding feature to copy incoming mail there. Replies from agents go out through Groove's SendGrid infrastructure but appear to come from your domain when SPF and DKIM are configured.

The Gmail OAuth path differs. Groove connects directly to a Gmail shared mailbox using Google's OAuth scope, eliminating the forwarding hop. This makes both incoming and outgoing mail flow through Gmail itself — better for deliverability, but tightly coupled to one Google account. Revoking the OAuth grant in your Google Account security settings is what cuts the link.

How do you export email conversations from Groove before switching?

Owners and Admins request a JSON conversation export from SettingsCompanyMoreExports. Groove processes exports in a shared FIFO queue — small accounts finish in minutes, larger accounts can take up to 72 hours (help.groovehq.com, 2024). No CSV format is offered.

Only one export request can be active at a time. When ready, Groove emails a download link backed by a short-lived Amazon S3 signed URL that cannot be shared with other users. The file is GZIP-compressed JSON matching Groove's v1 Tickets API "full" conversations format, which includes ticket metadata, every message in each thread, customer contact details, tags, and custom field values.

Knowledge base articles, Instant Replies (canned responses), and Rules (if-then automation) are not part of the export. Copy these manually or pull them through Groove's API before cancelling — they are otherwise lost when the account closes.

How do you update forwarding rules when leaving Groove?

At your email provider's admin panel, replace Groove's inbound address with your new platform's forwarding address. The exact path varies per provider, but the change takes effect almost immediately — within seconds for most providers, up to a few minutes for Outlook Exchange.

For Gmail: SettingsSee all settingsForwarding and POP/IMAPedit forwarding address. For Outlook/Microsoft 365: Exchange Admin CenterMail flowRules (or per-mailbox forwarding under RecipientsMailboxes). For Google Groups: Group SettingsEmail optionscustom routing. For cPanel: EmailForwardersedit destination. For Yahoo and Zoho: Mail SettingsFilters or Forwarding (provider-specific).

If you used Gmail OAuth instead of forwarding, head to your Google AccountSecurityThird-party apps with account access and revoke Groove's permission. This severs Groove's mailbox access immediately and stops new mail from appearing in the Groove inbox.

What happens to Groove's white-label DNS records (SPF, DKIM)?

Groove's white-label email runs on SendGrid, which means SPF includes and DKIM CNAME records point to SendGrid's infrastructure (Valimail, 2026). When switching platforms, remove those records and replace them with your new platform's authentication entries.

The records you'll find in your DNS zone typically include: an SPF include:sendgrid.net directive added to your TXT record, two or three CNAME records for DKIM (em-prefixed hostnames pointing to sendgrid hosts), and optionally a custom return-path subdomain. EasyDMARC, OnDMARC, and Valimail documentation all reference these patterns for Groove customers (easydmarc.com, 2025).

DNS changes take up to 48 hours to fully propagate. To minimise downtime, add your new platform's records first, verify they validate, then remove the Groove/SendGrid records the next day. If you run a DMARC policy of p=reject, lower it to p=none during the cutover so legitimate mail isn't blocked.

Can a new platform import Groove's historical email conversations?

Most platforms do not natively import Groove's v1 Tickets JSON format. The pragmatic approach is to keep your Groove export as a searchable archive while new conversations start fresh on the new platform — or use a third-party service like Help Desk Migration (help-desk-migration.com) for automated transfer.

Help Desk Migration's Groove service maps conversations, customers, tags, and custom fields into target platforms including Zendesk, Freshdesk, and Intercom on a per-record-priced model. It runs against Groove's API rather than the JSON export, so you don't need to time the export carefully.

For self-serve migrations, the JSON archive is enough. Customers reach out again when they need help, agents search the archive locally, and the new platform handles incoming mail from day one. Converge takes this approach — $49/month flat rate for up to 15 agents, starting with a clean inbox, with the Groove archive serving as historical reference.