How to Migrate from Re:amaze to Free Email Ticketing
Learn how to export Re:amaze data, pick a free ticketing tool, import history, set up automation, and cut over smoothly — all without per‑agent fees.
On this page
Moving off Re:amaze is straightforward when you break the work into clear stages. By the end of this guide you’ll have a fully functional free email ticketing system running with your historic tickets, contacts, and automation intact. You’ll need admin access to Re:amaze, a domain you can configure for email forwarding, and a free ticketing account ready to receive data.
1. Prepare Your Re:amaze Data
- Export tickets – Use Re:amaze’s CSV export to pull all open, closed, and archived conversations. Include ticket ID, subject, status, tags, assignee, timestamps, and any custom fields.
- Export contacts – Download the customer list with email, name, company, and any notes. This preserves context for future replies.
- Gather attachments – Re:amaze does not bundle files in the CSV. Download important attachments separately or note their ticket IDs for later upload.
- Document workflow rules – List auto‑assignment rules, macros, SLAs, and any tag‑based routing you currently use.
Why it matters: A complete export prevents gaps in history and ensures the new system can replicate your routing logic. Common mistake: Forgetting attachments or custom fields, which later appear as missing information in the new inbox.
2. Choose a Free Email Ticketing Tool
Evaluate candidates on:
- Cost – truly free for unlimited agents (no per‑seat fees).
- Core features – shared inbox, automatic email‑to‑ticket conversion, ticket status tracking, team collaboration, and AI reply suggestions.
- Setup time – account creation and email forwarding should take minutes.
NeuraDesk meets all of these criteria: it offers a shared inbox, AI reply suggestions, automatic email‑to‑ticket conversion, and ticket status tracking at no cost, with a flat‑rate plan only if you later need advanced reporting.
Why it matters: Selecting a tool that matches your current workflow reduces re‑training. Common mistake: Picking a “free tier” that caps agents or tickets, forcing a later migration.
3. Set Up the New System
- Create an account – Sign up (no credit card required) and invite your agents.
- Configure email forwarding – In your DNS, add a forwarder (e.g., support@yourdomain.com → your‑inbox@provider.io) or set up an SMTP relay if you prefer to keep the original address.
- Verify the domain – Complete the SPF/DKIM steps the provider supplies so replies land in the shared inbox, not spam.
- Create statuses and tags – Mirror the status list (New, Open, Pending, Closed) and tag taxonomy you documented from Re:amaze.
Why it matters: Proper email routing guarantees that every incoming message becomes a ticket instantly. Common mistake: Skipping domain verification, which causes bounced replies and lost tickets.
4. Import Historical Data
- Prepare the CSV – Align column headers to the new system’s import template (ticket ID, subject, status, assignee, tags, created‑at, updated‑at).
- Map custom fields – If you used custom fields in Re:amaze, create matching fields in the new tool before importing.
- Run a test import – Import a batch of 20‑30 tickets first. Verify that statuses, assignees, and tags appear correctly.
- Full import – Once the test passes, import the remaining data. Attachments can be uploaded manually or via API if the platform supports it.
Why it matters: Historical tickets give agents context and preserve reporting continuity. Common mistake: Importing without a test run, leading to mis‑mapped statuses that are hard to fix later.
5. Configure Automation and Rules
- Auto‑assignment – Re‑create the round‑robin or skill‑based rules you used before.
- Macros / saved replies – Transfer common responses; NeuraDesk’s AI reply suggestions can augment these with context‑aware drafts.
- SLA timers – Set response and resolution targets that match your previous commitments.
- Tag‑based routing – Apply the same tag logic so “billing” tickets go to the finance queue, etc.
Why it matters: Automation keeps workload balanced and response times consistent. Common mistake: Over‑automating early; start with the essentials and add complexity after the team is comfortable.
6. Test and Train the Team
- Send test emails – From a personal address, email the support address and confirm a ticket appears, is assigned, and triggers the correct macro.
- Run a sandbox sprint – Have each agent handle a few test tickets end‑to‑end (reply, change status, add internal note).
- Document the new UI – Create a one‑page cheat sheet covering ticket list filters, reply shortcuts, and AI suggestion acceptance.
- Collect feedback – Note any missing fields or workflow friction before the full cut‑over.
Why it matters: Hands‑on practice prevents a flood of questions on launch day. Common mistake: Assuming the UI is “intuitive enough” and skipping formal walkthroughs.
7. Switch Over and Monitor
- Update DNS – Point the production support address to the new forwarding destination.
- Disable Re:amaze inbound – Turn off email ingestion in Re:amaze so no new tickets land there.
- Communicate the change – Inform customers (brief banner or auto‑reply) that replies now come from the new system.
- Monitor the first week – Check ticket volume, assignment accuracy, and AI suggestion relevance daily. Adjust rules as needed.
- Decommission Re:amaze – After confirming zero inbound mail for 48 hours, export any final logs and close the account.
Why it matters: A controlled cut‑over avoids lost emails and gives you a safety window to catch issues. Common mistake: Cutting DNS over before confirming the new inbox receives mail reliably.
A well‑planned migration keeps your support history intact and your team productive from day one. Try NeuraDesk free
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free