ServiceNow migration cutover plan: data, integrations and risk controls
A practical ServiceNow migration cutover plan helps reduce risk, protect service continuity, validate integrations and support confident ITSM modernisation.
Read more →ITSM consulting · Migration
ITSM migration: move to the right tool without losing your data or your users
An ITSM migration moves years of tickets, knowledge and configuration data from one platform to another while your service desk keeps running. SMC Consulting plans what to move, maps and cleans it, tests it, and runs both tools in parallel before cutover, from any tool to any tool, backed by 40+ migrations delivered.
180ITSM implementations
40+ITSM migrations
25+years in IT service management
They trust us on their ITSM projects
When it is time to change ITSM tool
Four situations come back in almost every migration we run:
- The cost is running away. Licences, modules and seats piling up: your tool costs more than it returns in operational value.
- Contract renewal is coming up. The moment to reassess the market is before you sign another three years on a tool you merely tolerate.
- A merger or acquisition. Two ITSM tools to consolidate: the opportunity to choose, on objective criteria, the one that will serve the combined organisation.
- The team works around the tool. Tickets by email, follow-up in a spreadsheet: when the tool is bypassed, it no longer fits. You need to choose one that does.
A change of tool is not always the answer. If the platform covers your needs and the problems come from configuration, processes or adoption, optimising your service desk is faster and cheaper. And if the target tool is not chosen yet, start with ITSM tool selection.
Migration risks and how we remove them
Data loss
Every object is mapped and every test load is reconciled by counts and samples, so nothing disappears between the two tools.
SLA gaps
Open tickets keep their priority and SLA clock across the cutover, and both tools run in parallel until the new one is proven.
User resistance
Agents test the new tool before go-live and are trained by role; users get a portal that looks familiar on day one.
Broken integrations
Directory, email, monitoring and other connections are rebuilt and tested before the old tool is switched to read-only.
What we migrate
Tickets and history
Open tickets in full, plus the closed history you decide to keep, with notes, attachments and timestamps.
Knowledge base
Articles cleaned, deduplicated and re-categorised, so self-service works from the first day.
CMDB and assets
Configuration items, relationships and asset records, reconciled with your discovery sources.
Users, groups and permissions
Agents, teams, roles and requesters, aligned with your directory and single sign-on.
Workflows, SLAs and catalogue
Rebuilt on the target platform's standard rather than copied as they are, which is where most of the value of a migration lies.
Integrations and reports
Connections to email, monitoring and business tools, plus the dashboards your managers rely on.
Our ITSM migration method
The same five steps whatever the source and the target. For a step-by-step guide, read how to migrate to a new ITSM system.
Audit and decision
Why you are moving, what the target is (or how to choose it) and what must not break. Deliverable: a confirmed target and migration scope.
Data scoping
Open versus closed tickets, history window, knowledge base, CMDB, users and attachments. Deliverable: a data scope and a migration plan with dates.
Mapping and cleansing
Fields, categories, statuses, groups and SLAs mapped to the target; duplicates and obsolete records removed. Deliverable: a signed mapping document.
Test migrations and parallel run
Repeated test loads reconciled by counts and samples, then a parallel run with your agents. Deliverable: a test report you approve.
Cutover and hypercare
A planned cutover with the old tool switched to read-only, then hypercare until the new tool runs on its own. Deliverable: go-live and a post-migration review.
Assess your migration in 30 minutes
A senior consultant reviews your source tool, data volumes and deadlines with you and gives you a first view of scope and risks. Free, no commitment.
ITSM migration checklist
- A clear reason to move, and a target tool chosen against your requirements
- The end date of your current contract, and a cutover date well before it
- A decision on history: what to migrate, what to archive
- An inventory of integrations, automations and reports in the old tool
- A field and status mapping signed off by the process owners
- Knowledge articles cleaned before they move, not after
- At least one full test load, reconciled by counts and samples
- A parallel run plan and a fallback option
- Agent training and user communication scheduled before cutover
- The old tool kept read-only for audits and look-ups
Common migration paths
From ServiceNow
Usually driven by cost or complexity. We extract tickets, knowledge and CMDB data and rebuild the workflows on a lighter target platform.
From TOPdesk
Often a move towards stronger ITIL coverage or ESM. Operator groups, call types and the self-service portal need careful mapping.
From Cherwell
Cherwell customers: we plan the migration of history and rebuild custom forms on the target platform's standard, for a supported future.
From Zendesk
Teams that outgrew a customer-service tool: Zendesk tickets and articles go through migration to a platform with real ITIL processes.
From Freshservice
We move Freshservice data to the platform you choose; for HaloITSM there is a dedicated migration path.
From Jira Service Management
Often when IT support needs more than a development-centred tool. Projects, request types and SLAs are mapped to ITIL processes.
Migrate, optimise or choose first?
Optimise your current tool
The platform covers your needs but the service desk does not perform. Fix configuration, processes and adoption without moving.
Choose the target first
You know you are leaving but not where to. A short, structured selection avoids migrating twice.
Migrate
The target is chosen and the old contract has an end date. We plan the move from data scoping to hypercare.
Migrating to HaloITSM?
HaloITSM is our pick for most mid-size and large organisations, and a frequent target for the migrations we run. For the specifics, see migrating to HaloITSM and, if you are coming from Freshservice, Freshservice to HaloITSM migration and our Freshservice to HaloITSM migration guide.
Our advice is independent. If you choose HaloITSM, we can also supply the licences as its certified partner, and we tell you so up front.
Book your free ITSM audit
30 minutes with a senior ITIL v4 certified consultant: where your service desk stands, what to fix first and what this project would take on your platform.
- Free and without commitment
- A senior consultant contacts you within one working day to schedule the call
ITSM migration: frequently asked questions
How long does an ITSM migration take?
From a few weeks for a simple move with open tickets and a knowledge base, to several months when years of history, a CMDB and many integrations are involved. The data scoping step gives you a firm schedule before anything moves.
Can we keep our ticket history when we change ITSM tool?
Yes. Most organisations bring across all open tickets and a defined window of closed history, with notes and attachments, plus the knowledge base, CMDB and users. Older history can be kept in a searchable archive rather than migrated, which keeps the new tool clean. We decide this with you during data scoping.
Do you push us towards one particular tool?
No. The target is chosen against your requirements, and we migrate to the platform you choose. Our advice is independent. If you choose HaloITSM, we can also supply the licences as its certified partner, and we tell you so up front.
Should we migrate or optimise our current tool?
Optimise first if the tool covers your needs and the problems come from configuration, processes or adoption: it is faster and cheaper. Migrate when the tool itself is the limit: cost, contract, a merger or missing capabilities. See service desk optimisation; the free audit tells you which case you are in.
What about the migration once the tool is chosen?
We handle it: history and workflows carried over, parallel run, planned cutover, training. 40+ migrations delivered. Choice and deployment under one roof.
Which tools do you migrate from?
ServiceNow, TOPdesk, Freshservice, Jira Service Management, EasyVista, Ivanti and other ITSM platforms, plus Cherwell and Zendesk, which we migrate customers away from. The target can be any of the 10 platforms we work with.
Plan your ITSM migration before the contract ends
Book your free 30-minute audit. A senior consultant reviews your source tool, data and deadlines and gives you a first view of scope and risks.
Latest insights
SMC Consulting becomes a Lansweeper Solution Partner to deliver a smarter foundation for modern IT operations
SMC Consulting joins the Lansweeper partner ecosystem to connect asset discovery with HaloITSM, ServiceNow and Freshservice for a complete, current CMDB.
Read more →
CSRD & IT: measuring IT asset carbon footprint without a heavy toolchain
Discover how Green ITAM helps measure your IT asset carbon footprint, improve CSRD IT readiness, connect asset data, and support credible sustainability reporting.
Read more →