What are the first steps when moving to managed IT services?

A successful move to managed IT services begins with a controlled transition plan: establish what must remain stable, identify the information the provider needs, agree how decisions will be made, and set out how responsibility will transfer. The aim is to move ongoing IT management into a defined operating model without creating uncertainty for staff or exposing the organisation to avoidable risk.

1. Confirm the business case and desired outcomes

Before selecting or onboarding a provider, clarify why the organisation is considering managed IT services. The reasons may include reducing the burden on internal staff, strengthening cyber security, improving consistency, supporting growth, or obtaining specialist knowledge that is not available in-house. These aims should be translated into practical outcomes, such as better control of access, more consistent device management, clearer ownership of technology decisions or improved visibility of risks.

This prevents the transition from becoming focused only on technical tasks. A provider needs to understand which business activities depend on technology, which risks are unacceptable and what the organisation considers a successful service.

2. Establish the starting position

The provider and business should agree the current position before changes are made. This includes reviewing existing support arrangements, contracts, licences, warranties, suppliers, security controls, backup arrangements and any known technical limitations. Existing documentation should be checked for accuracy rather than assumed to be complete.

This stage also helps identify matters that could affect the transition, including unsupported equipment, expired licences, undocumented administrator accounts, legacy applications and services managed by third parties. These issues do not always prevent a move to managed IT services, but they should be recorded and assigned an appropriate action.

3. Decide what will be included

Managed IT services can cover different combinations of support, infrastructure, networks, cloud platforms, security, backup, user administration and strategic advice. The business should decide which functions are included from the start and which remain with internal staff or another supplier.

The service description should be specific enough to avoid assumptions. It may need to address:

• which offices, sites, devices and systems are within scope;
• which types of user request the provider will handle;
• which activities require approval before work begins;
• which third-party suppliers remain responsible for particular systems;
• how projects and improvements are separated from routine service management; and
• which tasks are excluded or charged separately.

A clear boundary makes it easier to prioritise work and prevents gaps between the provider, internal staff and other suppliers.

4. Agree governance and escalation

Define who can request work, approve changes, authorise expenditure and make decisions when a technical issue affects business operations. This is particularly important where the organisation has multiple sites, several senior stakeholders or systems with different owners.

The transition plan should include named roles for service ownership, security decisions, major changes and supplier coordination. It should also explain how disagreements, unresolved risks and serious incidents are escalated. These arrangements give the service a practical decision-making structure rather than relying on informal contacts.

5. Prepare access securely

A managed service provider will usually need controlled access to systems and administrative tools. Access should be granted using individual accounts, least-privilege permissions and multi-factor authentication where supported. Shared administrator credentials should be avoided, and any existing credentials that are no longer required should be removed or changed.

Keep a record of who has access, why it is needed and how it will be reviewed. The provider should also understand the organisation’s requirements for privileged access, remote administration, logging and approval of sensitive changes. Security should be built into the onboarding process rather than added after technical access has been issued.

6. Plan the transition in stages

Moving every responsibility at once can make it difficult to identify the cause of a problem. A staged transition is often easier to control. For example, the provider may first establish access and service records, then take responsibility for defined support functions, followed by infrastructure management, monitoring or improvement work.

Each stage should have an owner, a target completion point, dependencies and an acceptance check. The plan should also state what happens if a task cannot be completed as expected. This provides a clear route for dealing with incomplete documentation, unavailable suppliers or technical work that needs to be postponed.

7. Protect continuity during the handover

Existing support arrangements should not be withdrawn until the replacement responsibilities are understood and workable. Open issues, planned changes, recurring faults and known risks should be transferred with enough context for the new provider to act on them.

Where another supplier or an internal IT employee is involved, agree how information will be exchanged and when responsibility changes. Important handover material may include support histories, network information, renewal dates, security alerts, backup records and details of business-critical applications. The objective is to prevent knowledge being lost between the old and new operating arrangements.

8. Set up service management processes

Before the service is fully operational, agree how requests, incidents, changes and problems will be recorded and tracked. Staff should know how to raise an issue, what information to provide and which matters need management approval.

The provider and business should also agree how service information will be reviewed. Useful reporting may include outstanding issues, recurring causes, security actions, infrastructure risks, completed changes and items requiring a business decision. Reporting should support prioritisation, not simply record activity.

9. Communicate the change to staff

Employees need clear instructions about what is changing and what is not. Communication should cover the correct support route, any changes to account or device procedures, security expectations and the role of the internal contact who coordinates with the provider.

It is also useful to explain why informal workarounds, unapproved applications and direct approaches to individual technicians may create risk or delay. Consistent communication helps the new support model become part of normal business practice.

10. Review the transition after handover

The first review should examine whether the agreed service boundaries are workable, whether important information is still missing and whether any risks have emerged. It should also identify improvements that were deferred during onboarding.

Managed IT services should be treated as an ongoing operating relationship rather than a one-off installation. Regular reviews allow the arrangement to reflect changes in staff, sites, applications, security requirements and business priorities. S2 Technology Group can help organisations structure this transition around practical controls, clear ownership and a support model that can develop with the business.