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 · Implementation
ITSM implementation: scoping, configuration and adoption on the platform you choose
ITSM implementation is where a good tool choice becomes a working service desk, or does not. SMC Consulting scopes a first release you can actually deliver, configures the platform's standard capabilities first and prepares your agents and users from week one, so go-live is the start of adoption rather than the end of the project.
180ITSM implementations
40+ITSM migrations
25+years in IT service management
They trust us on their ITSM projects
Why ITSM implementations slip
Implementation projects rarely fail on technology. They slip for three reasons we see in almost every project we are asked to rescue:
- Scope creep. Every workshop adds one more workflow, one more form, one more exception, and the first release keeps moving.
- Customisation that becomes debt. Each step away from the platform's standard makes the next upgrade harder, until upgrades stop.
- Adoption left until go-live. A perfectly configured tool that agents work around is a failed project. Training and communication have to start in the first week, not the last.
Our method is built to prevent all three: a frozen first release, standard first, and adoption work from the start.
How we keep an ITSM implementation on track
A first release you can deliver
Scoping freezes a V1 scope. Everything else goes into a V2 roadmap agreed openly with your teams, instead of creeping into the first release.
Standard first
We configure the platform's native capabilities and customise only where it creates real business value, documented and reversible.
Adoption from week one
Agents test what we build at every sprint; training by profile and internal communication are planned with the project, not after it.
The team you meet delivers
The ITIL v4 certified consultants who scope your project configure it and stay through stabilisation. We do not hand your project to a third-party subcontractor.
What we deliver in an ITSM implementation
Project plan and governance
Workstreams, schedule, steering committee, RACI and resourcing, agreed with your IT leadership within two weeks.
ITIL v4 process design
Incident, request, problem and change management, the service catalogue and service levels, designed for how your teams actually work.
Platform configuration
Forms, workflows, assignment rules, SLAs, portal and dashboards, built on the platform's standard and demonstrated at every sprint.
Integrations and data
Directory and SSO, email, monitoring and collaboration tools, plus the import of users, assets and the history you decide to keep.
Training and communication
Training by role for agents and team leads, short guides for end users and a communication plan for the launch.
Go-live and stabilisation
An orchestrated cutover, 30 days of hypercare and a review of the baseline KPIs with your service desk manager.
Our ITSM implementation plan, phase by phase
The overall duration depends on the scope of your first release. It is fixed in the project plan, phase by phase, before configuration starts, and every phase ends with a deliverable you sign off. Implementing HaloITSM? See HaloITSM implementation for the platform specifics.
For the steering around it (planning, risks, reporting to management), see our ITSM project management and PMO support.
Free 30-minute scoping
Scope, volumes, critical integrations, internal constraints and target milestones. Deliverable: an outline V1 scope and a quote.
Project plan in 2 weeks
Workstreams, detailed schedule, governance, RACI and resourcing, aligned with your teams' availability. Deliverable: a plan validated by your IT leadership.
Configuration, standard first
ITIL v4 processes configured on the platform's native capabilities; customisations are rare, justified and documented. Deliverable: a configured environment, demonstrated at every sprint.
Acceptance and adoption
Testing with your agents, training by profile, internal communication. Deliverable: signed acceptance and trained teams.
Go-live and 30-day stabilisation
Orchestrated cutover, hypercare, tracking of the baseline KPIs and handover to your teams. Deliverable: a KPI review after 30 days.
Scope your implementation in 30 minutes
A senior consultant reviews your scope, integrations and constraints with you and tells you what a realistic first release looks like. Free, no commitment.
ITSM implementation checklist
- Named process owners for incident, request, problem and change
- A service catalogue written in your users' words
- Priorities, categories and SLAs agreed with the business
- Assignment groups and escalation rules that match your organisation
- A CMDB scope: which configuration items, from which sources
- The data to bring across: open tickets, history, knowledge articles
- Integrations: directory and SSO, email, monitoring, collaboration tools
- A knowledge base seeded with the most frequent requests
- A self-service portal tested with real users
- Agent training by role and a short guide for end users
- A cutover plan with a fallback option
- A hypercare team and the KPIs you will review after 30 days
Rescue: your ITSM project has stalled
Diagnose
A short, factual diagnosis of the real state of the project: configuration debt, open backlog, blocking points, and how much of the work can be kept.
Re-scope
A realistic first release your teams can go live with, and the rest moved to a roadmap everyone agrees on.
Resume or restart
Depending on the diagnosis, we take over the steering, reinforce the team in place, or restart from the platform's standard. Costed before you decide.
When organisations bring us in to implement
The tool is chosen, now it has to work
ServiceNow, HaloITSM, TOPdesk or another platform: you need a realistic plan, a team that knows it, and a fast start.
You are moving from another tool
Data to carry over, processes to rebuild and a cutover to orchestrate without interrupting support.
Your team lacks capacity or platform expertise
Your IT department steers; our consultants reinforce the project team on site or remotely, for as long as you need.
Which platform? We implement HaloITSM and advise on 10
HaloITSM is our pick for most mid-size and large organisations, and we implement it as its certified partner: see HaloITSM implementation. We are also a ServiceNow implementation partner, and we implement the other platforms below when they are the right fit.
- HaloITSM: Our pick · certified partner
- ServiceNow ITSM: Implementation partner
- Freshservice: We advise, implement and migrate
- Jira Service Management: We advise, implement and migrate
- TOPdesk: We advise, implement and migrate
- EasyVista Service Manager: We advise, implement and migrate
- Ivanti Neurons for ITSM: We advise, implement and migrate
- Xurrent (formerly 4me): We advise, implement and migrate
- GLPI: We advise, implement and migrate
- ManageEngine ServiceDesk Plus: Not yet delivered by SMC Consulting
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.
Not chosen your tool yet? Start with ITSM tool selection.
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 implementation: frequently asked questions
How long does an ITSM implementation take?
It depends on the scope of the first release, the number of integrations and how much data you bring across. We fix the duration in the project plan, within two weeks of the start, and commit to it phase by phase. A focused first release goes live sooner than a project that tries to deliver everything at once.
What are the phases of an ITSM implementation?
Scoping, project plan, configuration, acceptance and adoption, then go-live and 30 days of stabilisation. Each phase ends with a deliverable you sign off, as described in the plan above.
What does a first release (V1) usually cover?
Incident and request management, change management, the service catalogue, SLAs and basic reporting, standard integrations (directory and SSO, email), agent training and go-live. A full CMDB, several entities or complex integrations are costed separately at scoping.
We already have an integrator. Can you work alongside them?
Yes. We work as full project lead, as team reinforcement, or as quality assurance alongside an integrator. The scoping session defines the collaboration model that fits your organisation.
Our ITSM project has derailed. Can you take it over?
Yes, regularly. We start with a short diagnosis of the real state of the project, then propose a costed recovery plan: we take over the steering, reinforce the team in place, or re-scope from the platform's standard.
Which platforms do you implement?
The 10 platforms we work with: HaloITSM, ServiceNow ITSM, Freshservice, Jira Service Management, TOPdesk, EasyVista Service Manager, Ivanti Neurons for ITSM, Xurrent (formerly 4me) and GLPI. ManageEngine ServiceDesk Plus is not yet delivered by SMC Consulting. If your tool is already chosen we implement it; if not, we can help you choose too.
Start your ITSM implementation on solid ground
Book your free 30-minute audit. A senior consultant reviews your scope and constraints and tells you what a realistic first release looks like.
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 →