Skip to content

A direct IT practice — Canadian professional firms

White Glove Book a white-glove intro
Menu

Provider transition

Change IT providers without losing ownership of the environment.

A careful transition separates business authority, secure access transfer, documentation, vendor dependencies, and post-handover stabilization.

Before notice is given

Understand what the business owns.

Inventory domains, Microsoft 365 administration, devices, backups, applications, vendor contracts, documentation, and renewal dates. Do not request or transmit credentials through the website.

Authority

Name who can approve access, cost, contract changes, and communications.

Dependencies

Identify services controlled by the incumbent, the business, or another vendor.

Timing

Map notice periods, renewals, planned changes, and business dates that should not carry avoidable risk.

The handover

Transfer access and knowledge with a visible acceptance list.

A transition should track requested artifacts, responsible party, receipt, validation, and unresolved gaps rather than relying on one final meeting.

Access

Use approved secure channels for administrative handoff and rotate access when control changes.

Knowledge

Collect environment notes, vendor routes, device records, recurring issues, and known exceptions.

Validation

Confirm the business can administer essential services and reach providers before closing the former relationship.

After transition

Stabilize before redesigning everything.

Separate urgent ownership gaps from improvements that deserve a planned project. The first review should leave a prioritized record, not manufacture certainty.

First

Restore administrative ownership, support routes, and visibility of critical renewals.

Then

Address recurring user friction, device condition, lifecycle gaps, and vendor ambiguity.

Later

Scope migrations, broad security work, replacement programs, or policy changes separately.

Start with what the business owns, what the current provider controls, and the date that matters.

Book a white-glove intro

Prepare a useful introduction

Describe the interruption, the change ahead, and how your team prefers to be kept informed. A short note is enough to begin a service-fit conversation.

Required fields are marked with an asterisk (*).

Never include passwords, keys, recovery codes, or account-access details.

Read the privacy policy to understand how this request will be handled.