Moving a data centre, refreshing a network or rolling out new laptops changes the services your users depend on. SMC Consulting provides senior project managers for IT infrastructure projects, who plan and control the work and build in what generic project managers leave out: change management, CMDB updates and a clean service transition.
An IT infrastructure project replaces or moves the technical base your services run on: servers and storage, networks, cloud platforms, workplaces. The technical plan is rarely the hard part. The risks sit at the edges: a change nobody approved, a dependency nobody mapped, a CMDB that still describes the old platform, a service desk that learns about the cutover from the first calls.
Our project managers run infrastructure projects as IT service management projects too. They work with your change process, keep the configuration data current and prepare the service desk for go-live. For the governance across several projects, see PMO consulting for IT and ITSM projects.
Project managers who have run infrastructure projects before and know the questions to ask on day one.
One project manager for one project, or project management as a service across several, for as long as you need.
On site in Belgium, Luxembourg and France, or remote, in French, Dutch and English.
Change, configuration and service transition are part of the plan, not an afterthought.
Tell us the scope and the date; we come back with a project manager profile and how we would plan it.
Servers, storage and applications moved to a new data centre or hosting provider, wave by wave.
Workloads moved to AWS, Azure or Google Cloud, with the dependencies mapped before anything moves.
Switches, firewalls, Wi-Fi and WAN links replaced site by site, with change windows agreed in advance.
New laptops and devices deployed with Intune and Autopilot, users informed and the service desk ready.
An inventory of what you own and what depends on what, built from discovery tools rather than spreadsheets.
A move from one ITSM platform to another, planned so the service desk keeps working.
Every cutover goes through your change process, with impact assessed and a back-out plan agreed before the window opens.
The configuration items and their relationships are updated as the project moves them, so incidents after go-live are diagnosed on the new reality.
Runbooks, knowledge articles and a hypercare period agreed with the service desk before the first user calls.
Three phases, each with clear deliverables. Our post on change management in ITSM explains how changes are assessed and approved along the way.
Change, CMDB and service transition are IT service management (ITSM) practices; we plan them into the project instead of adding them at the end.
Scope, dependencies, schedule, budget, risks and the change windows, agreed with the teams and suppliers involved.
Progress, budget, quality and risks followed every week; every technical change through your change process.
Cutover, CMDB updated, runbooks and knowledge handed over, hypercare with the service desk, then a formal close.
With a migration or refresh to deliver next to daily operations, and no project manager free to run it.
Who need one person accountable per project and one view across them.
Whose infrastructure changes must leave an up-to-date asset inventory behind.
They plan and run a project that changes the technical base of your IT: a data centre move, a cloud migration, a network refresh, a workplace roll-out. They manage scope, schedule, budget, risks and suppliers, and make sure each change goes through your change process and ends with a service your teams can support.
Yes. We provide senior project managers for one project, on site in Belgium, Luxembourg or France or remotely, from kick-off to closure, or project management as a service across several projects.
Every cutover is a change: impact assessed, dependencies checked, approval obtained, back-out plan ready, and a review afterwards. We plan the change windows with your teams and suppliers at the start of the project. See change management in ITSM.
We update the configuration items during the project, then hand over ownership and rules: who maintains which class of CI, from which source. Where possible, discovery tools keep it current automatically; see cloud CMDB and dependency mapping and IT asset management.
Start with the free 30-minute ITSM audit, or talk to a consultant about the scope and the date.
Learn how the ServiceNow MCP server connects AI agents to governed ITSM workflows, Action Fabric and secure enterprise automation, plus readiness steps for 2026.
Read more →
Learn how a HaloITSM Lansweeper integration connects discovery data to HaloITSM, enabling cleaner CMDB records, faster triage, and better change decisions.
Read more →
A practical ServiceNow migration cutover plan helps reduce risk, protect service continuity, validate integrations and support confident ITSM modernisation.
Read more →
