Best Practices Migrating from Re:amaze to Free Shared Inbox

Moving off Re:amaze doesn’t have to break your support flow. Follow these practical migration practices to keep tickets, tags, and team collaboration intact in a free shared inbox.

NNeuraDesk TeamNovember 19 20263 min read
On this page

Migrating from Re:amaze to a free shared inbox can feel like a big project, but a structured approach keeps the transition smooth and preserves the context your team relies on. The following practices walk you through each phase, from data extraction to post‑launch monitoring, so you can move without losing tickets, tags, or automation logic.

Audit and export your Re:amaze data

Start by listing every data type you need: tickets, customer profiles, tags, custom fields, macros, and any reporting snapshots. Use Re:amaze’s export tools or API to pull a complete CSV or JSON dump. Verify row counts against the UI to catch missing records early. Store the export in a secure, version‑controlled location so you can re‑run the import if something goes wrong.

Map Re:amaze fields to shared inbox structure

Create a mapping table that pairs each Re:amaze field (status, priority, assignee, custom tags) with the equivalent field in your new shared inbox. Pay special attention to status values — Re:amaze may use “Open”, “Pending”, “Closed” while the target tool could use “New”, “In Progress”, “Resolved”. Document any fields that have no direct counterpart; you may need to recreate them as custom tags or notes after import.

Set up shared inbox folders and tags before import

Configure the folder hierarchy and tag taxonomy in the new inbox first. Mirror the categories your team already uses (e.g., “Billing”, “Technical”, “Feature Request”) so agents can filter immediately. For guidance on folder design, see Best Practices Organizing Shared Inbox Folders for Teams. Pre‑creating these structures prevents a scramble to reorganize thousands of imported tickets later.

Import tickets in batches and verify

Break the full dataset into manageable batches — for example, 1,000 tickets per run. After each batch, spot‑check a random sample: confirm that subject, body, attachments, timestamps, and mapped fields appear correctly. Log any discrepancies and adjust the mapping before the next batch. This incremental approach limits the impact of errors and makes rollback easier.

Recreate automation rules and macros

Re:amaze macros, auto‑replies, and routing rules rarely transfer automatically. Re‑build the most critical workflows first: auto‑assign based on tag, SLA reminders, and canned responses for common questions. If your new inbox supports AI reply suggestions, enable them to speed up first‑response time. For tips on prioritizing incoming work, refer to Best Practices Prioritizing Tickets in a Free Shared Inbox.

Train the team on the new workflow

Run a short hands‑on session covering the new folder layout, tag usage, ticket assignment flow, and any new collaboration features such as internal notes or @mentions. Provide a one‑page cheat sheet that maps old Re:amaze actions to the new equivalents. For onboarding guidance, see Best Practices for Onboarding New Agents to a Shared Inbox.

Monitor and iterate after go‑live

During the first two weeks, track key metrics: first‑response time, ticket reopen rate, and agent satisfaction. Hold a brief daily stand‑up to surface friction points — missing tags, misrouted tickets, or confusing statuses. Adjust folders, tags, or automation rules as needed. Continuous refinement ensures the new shared inbox becomes a stable foundation rather than a temporary fix.

Try it free at NeuraDesk.

Found this useful? Share it with your team.

Join teams already using NeuraDesk

Ready to get started?

Create your workspace and try NeuraDesk for free.

Sign up free