Migrating From Your Old Help Desk Without Losing Your History
Switching help desks feels risky for one reason: history. Years of conversations, customer records, templates and notes live in the old tool, and the fear of losing them keeps teams on platforms they have outgrown. A migration done in the right order takes a week of part-time effort and loses nothing. Here is the order that works.
STEP 1: INVENTORY WHAT ACTUALLY MATTERS
Not everything deserves to migrate. Sort your old tool into four buckets:
- MUST KEEP: contact and company records, open conversations, recent conversation history (often 12-24 months is plenty), attachments customers might reference
- NICE TO KEEP: closed conversations older than a year, internal notes, reporting exports
- REBUILD, DO NOT MIGRATE: canned responses, tags and views - these deserve a fresh design anyway (old tag jungles are never worth carrying)
- DO NOT MIGRATE: spam, test data, duplicate contacts from three imports ago
Deciding this first turns an overwhelming archive into a finite checklist.
STEP 2: PICK THE CUTOVER STYLE
Two options, honestly different:
- BIG BANG: migrate contacts and history, switch all channels on one day. Faster, more intense, fine for small volumes.
- PARALLEL RUN: new tool live for new conversations while the old one stays readable for a week or two. Slower, calmer, the right call for most teams.
STEP 3: START WITH EMAIL
Email is the channel that migrates most cleanly, and it is usually where your history lives. Connect your mailboxes via forwarding, your own domain, or IMAP import - the import option pulls years of history into the workspace so old threads sit beside new ones. Do email first, verify search works across the imported history, then move the other channels.
STEP 4: REBUILD THE WORKING SET
Migrate the skeleton, rebuild the habits:
- Import contacts and companies; deduplicate once, properly
- Write the 10-20 canned responses you actually use (a migration is the best audit your template library will ever get)
- Recreate tags as a small, intentional set - five to seven that report, not fifty that confuse
- Re-set working hours, first-response targets and assignment rules
STEP 5: RUN THE PARALLEL WEEK
For one week: new conversations in the new tool, old tool in read-only. Watch for three things - anything arriving in a channel you forgot to connect, customer replies threading incorrectly, and whether your team misses a feature enough to matter. Fix channel gaps immediately; note feature wants for later.
STEP 6: TELL CUSTOMERS - MINIMALLY
Good news: customers do not need a migration announcement. As long as your email addresses stay the same and replies keep arriving, the change is invisible. The one exception: if you change support addresses or a widget, a short note is polite. "Same address, faster replies" is enough.
STEP 7: DECOMMISSION CLEANLY
- Export a final full archive from the old tool and store it where your retention policy says
- Confirm with the vendor what happens to your data after cancellation, and when it is deleted
- Cancel at the right point in the billing cycle
- Keep admin access to the old account until the archive is verified restorable
STEP 8: VERIFY, THEN RELAX
The migration file should end with three checks: search across imported history returns old conversations; every channel delivers to the new queue; the archive opens outside the vendor's tool. Once those pass, close the project.
The migration guide from a live help desk is at https://onsitesai.com/learn/migrate-help-desk.html and the cloud setup walkthrough - workspace, widget, channels, team - is at https://onsitesai.com/docs/cloud-setup.html. The software is free for your first three seats, so the parallel week costs nothing.
#HelpDesk #Migration #CustomerSupport #SharedInbox #SaaS #CX


Comments
Post a Comment