Tenant migration / practical scope
Decide what must still work on Monday.
An estimate based only on mailboxes can miss the work that makes a migration expensive: identity, shared data, delegated permissions, non-human mail senders and the people who approve the cutover. A useful project scope names every affected workload and the test that proves its outcome.
Request a written migration scopeChoose the route by source, destination and workload
For Google Workspace to Microsoft 365, plan mail, calendars, contacts, My Drive, Shared Drives and identity changes separately. For a tenant split or merger, distinguish Exchange cross-tenant mailbox prerequisites from SharePoint and OneDrive movement. For an IMAP migration, do not assume calendars, contacts, shared access and server-side rules come with the copied mail.
Google Workspace to Microsoft 365 migration services
Moving from Google Workspace requires a plan for Gmail, Google Drive, shared drives, calendars and account identities, not merely changing MX records.
Read the technical workstream ↗02Microsoft 365 tenant-to-tenant migration
Tenant consolidation involves more than copying mailboxes. Identity, domain release, Teams, SharePoint and coexistence all need sequencing.
Read the technical workstream ↗03Exchange to Microsoft 365 migration
An Exchange environment can contain hybrid relationships, public folders, transport rules, distribution groups and archives outside the obvious mailbox count.
Read the technical workstream ↗04IMAP to Microsoft 365 mailbox migration
IMAP can move email messages, but it does not itself transfer calendars, contacts, tasks or platform configuration.
Read the technical workstream ↗05Google Drive to SharePoint migration services
A shared drive does not map cleanly to an individual folder. Destination sites, libraries, owners and access models must be designed first.
Read the technical workstream ↗06SharePoint migration services
SharePoint migrations can involve existing sites, file servers, Google drives or third-party platforms. Source and destination permissions govern the design.
Read the technical workstream ↗07Cross-tenant Exchange Online mailbox migration
Moving Exchange Online mailboxes between tenants requires target identity preparation and may be blocked by legal holds or unsupported configurations.
Read the technical workstream ↗08Failed Microsoft 365 migration recovery
Migration failures require root-cause diagnosis before restarting batches or repeating cutovers.
Read the technical workstream ↗Delivery evidence
Four things to insist on in a migration proposal
Workload inventory
Source, destination, object count, permissions, shared resources, integrations and explicit exclusions.
Prerequisite register
Licences, recipient mapping, domain ownership, retention holds and the decision-maker for each blocker.
Pilot acceptance
Representative mailbox, calendar, user sign-in, team file-sharing and external mail-flow tests, each with a recorded result.
Cutover controls
Change window, approval process, exception handling, recovery approach and aftercare boundaries.
Illustrative: a shared-folder surprise
A company might have 20 staff mailboxes but also a finance Shared Drive owned by a team, recurring meeting-room bookings and a CRM that sends invoice emails. Moving personal inboxes does not decide who owns those files, how guest sharing will work or whether the application sender is correctly authenticated after DNS changes. The proper first deliverable is a dependency map and a pilot, not a guarantee that everything transfers identically.
Microsoft documents its Google-to-Microsoft migration workstreams and separate cross-tenant Exchange licensing and recipient prerequisites. Both must be checked for the customer's actual configuration before implementation.
This is an independent Pearl Lemon Group service website, not a Microsoft or Google partner claim. Team availability, licences, delivery scope and prices are confirmed only after discovery.
Discuss the source and destinationBuyer's questions
Common migration questions
These answers clarify scope and limitations; they are not a proposal for a specific tenant or a claim of approved vendor credentials.
Can a whole Microsoft 365 tenant be moved in one operation?
No single Exchange batch moves everything a business thinks of as its tenant. Exchange mailbox content, OneDrive, SharePoint sites, Teams collaboration, custom domains, application connections and Entra identity require different preparation and acceptance tests. Start with a source-to-destination inventory and decide which workloads belong to the project. Read the tenant-to-tenant planning guide before promising a cutover.
What if some mailboxes are on legal or retention hold?
Microsoft's native cross-tenant mailbox migration has documented hold restrictions. A held mailbox is not simply an account to skip and delete later. The organisation's legal or compliance owner needs to review preservation requirements, alternative methods and approval of any change. Put these users into an exception register before the first migration wave, and verify the current Microsoft prerequisites.
Will IMAP migration also move contacts, calendars and shared access?
Do not assume so. IMAP is a mail-message access protocol and does not reproduce Microsoft 365 identities, Outlook sharing rights, calendar resources or contact folders as a complete business migration. Those need a separate discovery and migration route. A supplier should explain what will be rebuilt, what will not transfer and how representative users will check the result. Compare the IMAP-specific limitations.
Can you guarantee there will be no downtime or no user disruption?
Not without detailed technical assessment, and even then an absolute guarantee would be misleading. DNS propagation, source throttling, client profiles, authentication policies and dependencies outside the migration tool can create interruptions. A credible project defines a pilot, communications, change freeze, monitoring and a business-approved go/no-go plan. The goal is to manage measurable risks rather than promise an outcome the facts cannot support.
How can I obtain a meaningful migration price?
Provide the source and target, approximate mailboxes and total data, shared drives or SharePoint sites, identity changes, any legal holds, target date and expected support. Ask for separate lines for licences, discovery, migration, file permissions, aftercare and exclusions. Our migration pricing framework helps compare proposals, but no fixed fee or delivery window is offered without verifying actual scope and capacity.