Current service and contract information
Bring the service scope, notice and renewal dates, known exit obligations and a list of other providers. Have the relevant owner review the contract if its requirements are unclear.
IT services
An IT provider change needs agreement on access, documentation, support ownership and the conditions for taking over each service. Subnet can work with your team and, where cooperation is available, the outgoing provider to plan the handover. The sequence depends on your environment, contracts and readiness.
You may be changing providers because support no longer fits, responsibilities are unclear or your organisation needs a different mix of capability. Before setting a cutover date, establish what your current arrangement covers and what the new one needs to do.
Some services may transfer with little technical change. Others may depend on a licence, account, backup arrangement or management tool controlled by the outgoing provider. Those dependencies need to be understood before support ownership changes.
Bring the service scope, notice and renewal dates, known exit obligations and a list of other providers. Have the relevant owner review the contract if its requirements are unclear.
List the important applications, infrastructure, subscriptions and domains. Identify who owns each account and who currently has administrative access. Share credentials only through an agreed secure method.
Collect available configuration records, support history and the list of unresolved issues or active projects. Missing information should be recorded as a gap to resolve, rather than treated as complete.
Identify critical operating periods, change restrictions and the people who can approve decisions. Include the staff who can confirm whether the new support arrangements work in practice.
PEER selected Subnet through a competitive tender, valuing transparent pricing and a whole-of-service approach. Its published case study describes managed-service support beginning in 2023, alongside PEER’s solo IT resource.
Watch PEER’s selection clip Read the PEER storyEvery environment is different, but there are common items that should be captured during an IT provider transition.
Subnet can help you identify what is missing and prioritise the information required for a safer handover.
PLAN WITH SUBNET
These activities provide a starting point for a transition discussion. Their sequence, overlap and timing are agreed for your organisation, including where the outgoing provider can help and where information is incomplete.
Agree what support will cover, the people involved, incumbent notice obligations and the business constraints that affect the change.
Coordinate the access, contacts and records that can be provided. Agree secure transfer methods and record anything missing.
Compare available documentation with the environment and the proposed service. Assign the gaps that need clarification.
Plan how your people will request help, how support responsibilities change and which tools are introduced under the agreed scope.
Identify remediation and improvement work that needs its own scope, approval or timing, rather than assume it is included in the monthly service.
Record responsibilities, outstanding actions, documentation and escalation contacts so the continuing service has clear owners.
This is a planning guide, not a fixed delivery timetable, formal readiness gate or interruption-free guarantee. Any change window, service-start decision, acceptance criteria and billing arrangements need to be agreed for the engagement.
Changing providers and improving the environment are related decisions, but they do not always have the same scope. A transition can reveal work that needs a separate project, such as replacing unsupported systems, redesigning a network or correcting long-standing configuration issues.
Yes. Transition support from an incumbent provider is part of how Subnet works with organisations moving to its managed IT service, Foundations. The plan is built around your environment: what your current arrangement covers, what needs to be handed over and who approves each step. The sequence, overlap and timing are agreed for your organisation rather than set to a standard timetable.
There is no useful standard duration without reviewing the environment and existing arrangements. Access, documentation, contract dates, licensing and the amount of work being transferred all affect the plan. Agree readiness criteria as well as a target date.
It can. Notice and renewal dates and any exit obligations can affect the sequence and timing of a handover. Bring those dates and the service scope to the first discussion, and ask the person who owns the contract, or your own adviser, to confirm what the terms mean for you. Subnet plans around the dates you provide and does not assume them.
The transition can include coordination with the outgoing provider where authorised and available. Agree who requests information, approves access and owns open items. The plan needs to account for any limits on cooperation or the information available.
It depends on how each one was set up, so it should be checked item by item before support ownership changes. Some services may rely on a licence, account, backup arrangement or management tool controlled by the outgoing provider. Ownership, transfer or replacement, and any cost, need explicit decisions rather than assumptions.
Not necessarily. First distinguish the support change from any technology changes the environment needs. If a tool, licence or system cannot remain in place, its replacement and impact should be identified and agreed before that part of the handover.
Identify the gaps early and agree how they will be investigated. Prioritise the information needed to support critical systems, manage authorised access and understand recovery arrangements. Missing documentation may change the scope or timing of the transition.
Backup is treated as a named dependency of the handover. Early in the planning, the teams identify where backups are held, who controls the backup platform and what recovery arrangements exist today, then agree how access and responsibility move. No recovery outcome is assumed until that is understood.
That depends on the changes needed. Some handovers primarily change support ownership; others involve systems, tools or access changes. The plan should identify possible interruptions, agreed change windows and recovery actions for the affected services.
Agree that decision as part of the handover. Confirm the replacement access and remaining dependencies first, then have the authorised owner remove or change access at the agreed point. Avoid leaving the timing to assumption.
EXPLORE FURTHER
BEFORE WE TALK
You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.
The historical case study records coordination with the council’s internal staff and previous providers. The customer relationship ended in 2023. Speaker roles and service arrangements reflect the original period, not a current relationship.
Read the historical Berri Barmera storyLET’S TALK
Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.