Choose the migration path that matches your source
A Microsoft 365 migration is a project, not the same as ongoing tenant support. Moving Google Workspace, consolidating tenants and replacing an Exchange environment require different preparation. Mail, files, permissions, devices and integrations should each be listed explicitly; a mailbox move is not proof that every business workload has moved.
| Source or business change | Planning focus | Scope to confirm |
|---|---|---|
| Google Workspace | Gmail and Drive inventory, identities and permissions | Mail, calendars, contacts, personal and shared files |
| Another Microsoft 365 tenant | Source/target ownership, domains and user mapping | Mailbox, OneDrive, SharePoint and other workload-specific moves |
| Exchange or another email platform | Supported method, identity and mail-flow dependencies | Data types, coexistence, DNS changes and application email |
| File shares or other file platforms | Destination structure, permissions and unsupported items | Data volume, file exceptions and business validation |
Ask for a scoped project price and written acceptance checks
Users, data volume, permissions, coexistence, source constraints, tooling and support needs determine migration effort. Your quote should separate delivery fees, subscriptions, migration licenses, remediation and ongoing support. The published free-migration offer is conditional on eligibility and its managed IT agreement; it is not a blanket offer for every migration. Review those terms before relying on it.
Review published plans and pricing and record missing proposal details in the free MSP comparison worksheet.
How to plan the engagement
- Inventory users, mailboxes, files, domains, permissions and integrations; record exclusions.
- Agree licenses, access approvals, target configuration and the migration method.
- Run a pilot and define cutover communication, change windows and fallback criteria.
- Validate the agreed workloads, record exceptions and complete the documented handover.
Questions buyers ask
What is included in Microsoft 365 migration services?
The agreed scope can include discovery, destination preparation, pilot migration, cutover, validation and handover. Confirm every workload and data type, as well as licensing, permissions and post-move support, in the proposal.
How long does a Microsoft 365 migration take?
Timing depends on users, data volume, source access, identity, permissions, testing and change windows. We discuss a schedule after those dependencies are understood rather than promising one duration for every project.
Do you handle Google Workspace and tenant-to-tenant migrations?
Yes. We scope those as distinct migration paths because their prerequisites and workload handling differ. The dedicated pages explain what information to prepare.
Is migration included in a managed IT agreement?
Only if the written agreement or an eligible published offer includes the required scope. Larger or more complex migrations and out-of-scope work need a separate project quote.
Related services and decision guides
- Google Workspace to Microsoft 365 migration
- Microsoft 365 tenant-to-tenant migration
- Ongoing Microsoft 365 support after migration
- Read the conditional migration offer
Technical references
Microsoft distinguishes tenant-to-tenant and external-platform migration paths. Consult the workload documentation when defining a project's supported method and prerequisites. Microsoft 365 migration overview.
Page updated 2026-09-28. CloudTechForce is based in Columbus, Ohio; other listed locations are service areas. Company details and team information are available for your review. Service coverage and commitments are defined in the written agreement.
Request a migration proposal
Source and target platforms, user count, approximate mail/file volumes, domains, shared data, deadline and any current-provider contract constraints.
Tell us which published plan you are considering, or describe the project you need quoted. We will use your requirements to discuss the appropriate scope.