Migrating Ticketing Systems
The new system went live on a Saturday. On Monday the desk discovered that the old system's categories had been imported as a single field called "legacy_category". Every migrated ticket now showed the migration date as its creation date. The requesters' replies to old tickets were arriving in the old mailbox, which nobody was watching. By Wednesday the desk was running both systems. It would continue to do so until the following spring. Then someone finally switched the old one off and discovered three hundred tickets that had never left it. None of this was the new system's fault. The migration had been planned as a weekend and it was, in fact, a project.
This series is the project. It covers why ticket system migrations go wrong, in five recognisable patterns. It covers what to migrate and what to leave behind, because not everything deserves the trip. It covers remapping categories, statuses and fields with a table rather than a hope. Then comes the cutover plan, and why it should be a quiet Tuesday rather than a brave Saturday. It covers retraining users and technicians without a course. And it covers keeping the history without keeping the old system alive for a year. The old system holds everything the desk has learned. Move it carefully, read it once, and then let it go.
Articles in This Series
- Why Ticket System Migrations Go Wrong: The Five Patterns
History lost, categories mangled, users retrained badly, two systems running for a year; the five failure patterns, the early sign of each, and the migration risk list. - What to Migrate and What to Leave Behind
Open tickets always, recent closed tickets usually, the old archive read-only, the knowledge base rewritten rather than copied, the templates rebuilt, and the data inventory. - Remapping Categories, Statuses and Fields
The mapping table from old to new, and the Other bucket. Covers what to do when the new tool has a fixed status set, the field with no home, and the mapping table to copy. - The Cutover Plan, and Why It Should Be a Tuesday
Freeze, export, import, verify, switch the mailboxes, announce; the rollback written before the switch; why a quiet weekday beats a weekend; and the cutover runbook. - Retraining Users and Technicians Without a Course
The one-page what-changed for users, the desk-side first week for technicians, the new acknowledgment, the portal link in every signature, and the what-changed page. - Keeping History Without Keeping the Old System Alive
The read-only archive, the export that can be searched, the question nobody asks after month six, the day the old system is switched off, and the archive decision sheet.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.