How to Migrate from HubSpot to Free Email Ticketing
Learn how to export HubSpot tickets, set up automatic email-to-ticket conversion, and train your team on a free shared inbox that keeps support running smoothly.
On this page
Moving off HubSpot Service Hub means you can stop paying per‑agent fees while keeping a complete ticket history. Before you start, make sure you have admin access to HubSpot, control over your support email domain, and a free ticketing account ready to receive data.
1. Export Your HubSpot Ticket Data
- Open the tickets view in HubSpot and apply any filters you need (date range, pipeline, owner).
- Use the export option to download a CSV file. Include standard fields — ticket ID, subject, status, priority, created date, closed date, owner, and any custom properties you rely on.
- If you have attachments, note that HubSpot’s CSV export does not include them; you will need to download attachments separately or accept that they stay in HubSpot.
Why it matters: a complete CSV gives the new system a faithful record of every conversation, so agents can search history without switching tools. Common mistake: forgetting to export custom fields that your workflows depend on, which leads to missing context after import.
2. Prepare Your New Email Ticketing System
- Create an account in your chosen free platform and verify ownership of the support email domain (add the required DNS records).
- Set up a shared inbox that all agents will use. Configure the inbox to accept mail from your existing support address.
- Enable automatic email‑to‑ticket conversion so every incoming message becomes a ticket instantly.
Why it matters: proper domain verification prevents delivery failures and ensures the new inbox can send replies on your behalf. Common mistake: skipping SPF or DKIM setup, which causes emails to land in spam or be rejected.
How to Set Up a Free Email Ticketing System for a Small Team walks through the DNS steps in detail.
3. Import Historical Tickets
- In the new system, locate the CSV import tool. Map each HubSpot column to the corresponding field (subject, status, priority, assignee, timestamps).
- Run a test import with 10‑20 rows. Verify that status values line up (e.g., HubSpot “Closed” → new system “Resolved”).
- Once the test looks correct, import the full file. Monitor the progress log for any rows that fail.
Why it matters: preserving ticket history lets agents reference past interactions without leaving the new inbox. Common mistake: mismatched status or priority values, which creates a confusing backlog that must be cleaned manually.
Import Existing Support Emails into a Free Ticketing System covers field‑mapping tips for a smooth import.
4. Set Up Automatic Email‑to‑Ticket Conversion
- In your email host (Google Workspace, Microsoft 365, or another provider), create a forwarding rule that sends every message addressed to support@yourdomain.com to the unique inbox address supplied by the ticketing system.
- Send a test email from an external address. Confirm it appears as a new ticket with the correct requester and thread.
- Adjust any spam‑filter settings that might block the forwarded mail.
Why it matters: new customer emails become tickets instantly, so nothing slips through the cracks during the transition. Common mistake: creating a forwarding loop by also forwarding tickets back to the original address.
How to Implement Email-to-Ticket Conversion in a Free Tool explains the forwarding configuration for common providers.
5. Train Your Team on the New Workflow
- Walk agents through the shared inbox layout: ticket list, conversation view, status buttons, and internal notes.
- Show how AI reply suggestions can draft responses, and how to insert them with a single click.
- Practice assigning tickets, changing statuses, and using keyboard shortcuts for common actions.
Why it matters: a short, hands‑on session reduces resistance and speeds up adoption. Common mistake: assuming the interface is self‑explanatory; agents often miss time‑saving features like bulk status changes.
6. Switch Over and Monitor
- Update the MX or forwarding records so all future support mail lands in the new inbox.
- Change any public contact forms, chat widgets, or documentation to point to the new support address.
- Keep the HubSpot forwarding active for 48 hours as a safety net, then disable it once you confirm zero missed messages.
- Review ticket volume, response times, and any bounce reports during the first week.
Why it matters: a controlled cutover lets you catch configuration issues before they affect customers. Common mistake: leaving the old forwarding rule enabled indefinitely, which creates duplicate tickets.
A clean cutover keeps response times steady and your history searchable. Try NeuraDesk free to see how simple the switch can be: try NeuraDesk free.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free