Skip to content
M365 CareMicrosoft 365, managed monthly Book a scoping call
Menu

IT projects and rollouts

A migration has a start, and monthly care picks up at the finish.

Recurring administration keeps a live tenant healthy. It is not the right shape for a migration, an office move, or a new-site rollout—those need their own scope, their own finish line, and a clean handoff back into monthly care once the dust settles.

Book a scoping call

How a project actually moves

Four steps from trigger to handoff.

Scoped, delivered, then folded back in.

  1. Step 01

    Identify the trigger

    A migration, acquisition, office move, or new-site setup surfaces as something bigger than routine upkeep.

  2. Step 02

    Scope it separately

    The work gets its own written deliverables, timeline, and price—not an assumption folded into the per-user monthly plan.

  3. Step 03

    Deliver against the plan

    The project runs to its stated finish line: data moved, identities provisioned, the new site or system live.

  4. Step 04

    Hand back to monthly care

    The resulting configuration, new shared work, and any new owners get folded into the recurring plan with names attached.

What this is—and is not

A handoff, not a hidden add-on.

Projects are scoped and priced on their own—then care picks up what they leave behind.

This isn't a description of a migration running for free inside a recurring retainer, and it isn't a claim to a particular project methodology or delivery certification. It's a plain account of the mechanics: a defined piece of work gets its own scope and price, gets delivered against agreed deliverables, and then the environment it leaves behind—new shared sites, new access decisions, a new office's device baseline—becomes part of what monthly care maintains going forward.

The alternative is worse for everyone: a migration quietly absorbed into routine administration with no clear finish line, no agreed price, and no moment where responsibility formally changes hands.

Three representative triggers

Different projects, the same handoff.

A tenant-to-tenant migration

Two Microsoft 365 environments become one, typically after an acquisition or restructuring, with mailboxes, files, and identities moved deliberately.

A new office or site

A new location needs its own network handoff, device baseline, and access setup before it's treated as part of the regular tenant.

A legacy system moves in

An on-premises application or file share is retired in favour of a Microsoft 365-native replacement, changing what the recurring plan now covers.

Before a project starts, make this explicit

Five things worth agreeing in writing.

  • The deliverables and the finish line, stated plainly enough that "done" isn't a judgment call
  • The price, agreed separately from the per-user recurring plan
  • Who owns the decision if the scope needs to change mid-project
  • What happens to the environment once the project ends—specifically, what joins monthly care and what doesn't
  • A named date when the handoff is confirmed complete

Continue from here

See where recurring care picks up.

Compare service shapes What we manage each month Starting care Book a scoping call

A practical first step

Send us the recurring Microsoft 365 work that keeps falling through the cracks.

contact@m365care.com

Email M365 Care directly to discuss recurring tenant administration, scope, or fit.

M365 Care
Independent Microsoft 365 tenant administration for growing teams.

Not affiliated with or endorsed by Microsoft Corporation.

M365 Care is an independent IT provider and is not affiliated with Microsoft. Microsoft and Microsoft 365 are trademarks of the Microsoft group of companies.