Cutting over from your current tool | ITSM Groundwork

Moving from one ITSM tool to another is less about technology than about timing and habits. A clean cutover for a mid-market team usually takes a few weeks of preparation and one decisive switch, followed by a month of close attention.

What data should you bring across?

Be selective. Bring what people use; archive the rest:

Open tickets: migrate them, or let them close in the old tool while new work starts in the new one. For most teams, a short overlap is simpler than migrating open work.
Knowledge articles: review and bring the current ones. A migration is a good moment to retire stale content.
Catalog design: rebuild your request types from the forms you wrote, improving them as you go rather than copying old fields.
Users, groups and roles: usually synced from your directory.
Configuration and asset records: bring them only if they are current; otherwise start the small service map from the previous lesson.
Ticket history: keep it in a read-only export or the old tool for reporting and audits, rather than forcing years of records into the new platform.

When should you switch?

Pick a quiet day early in the week, away from month-end, payroll and major releases. Announce the new intake path a week ahead, redirect the support email address on the day, and put a banner on the old portal pointing to the new one.

How do you run the first month?

Freeze new automations for the first two weeks so you can see how the core setup behaves. Hold a short daily check in week one and a weekly review after that, looking at three things: tickets arriving outside the new intake path, tickets with no category or the wrong category, and SLA breaches. Fix routing and forms based on what you see.

When can you retire the old tool?

Keep it read-only until the first month of reporting is complete and any open tickets are closed. Check the licence terms before renewal dates; annual billing is common across the platforms in this comparison, so a cutover just before a renewal avoids paying twice.

Does a trial help with cutover?

Yes, if you use it for a real dry run. Several platforms let you start before paying: monday service, Freshservice and Zendesk offer 14-day trials, SysAid a free trial with no credit card, Halo (formerly HaloITSM) a trial (30 days with all modules when we read its page in September), and Jira Service Management a free plan for up to three agents. Use the trial to rebuild your top five catalog items and route a day's worth of sample tickets before you commit.

What about forced moves?

Sometimes the vendor sets the timeline. Atlassian's 23 September 2026 post gives 28 March 2029 as the Data Center end-of-life date, which affects teams running Jira Service Management self-managed. A deadline years away is still a reason to plan the move on your terms.