Cloud migration / technical planning
Move what matters. Know what won't move.
Moving mailboxes is only part of a business migration. Identity, permissions, shared files, calendars and people need an equally clear plan. Start with the source, target and risks that actually apply to your organisation.
Independent Pearl Lemon Group service website. Not affiliated with Microsoft or Google. Quotes require technical review.
High-intent migration work
Choose the right migration path.
Not every move uses the same method. The source, destination and workload determine what can be automated and what needs review.
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.
Scope this migration ↗02Microsoft 365 tenant-to-tenant migration
Tenant consolidation involves more than copying mailboxes. Identity, domain release, Teams, SharePoint and coexistence all need sequencing.
Scope this migration ↗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.
Scope this migration ↗04IMAP to Microsoft 365 mailbox migration
IMAP can move email messages, but it does not itself transfer calendars, contacts, tasks or platform configuration.
Scope this migration ↗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.
Scope this migration ↗06SharePoint migration services
SharePoint migrations can involve existing sites, file servers, Google drives or third-party platforms. Source and destination permissions govern the design.
Scope this migration ↗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.
Scope this migration ↗08Failed Microsoft 365 migration recovery
Migration failures require root-cause diagnosis before restarting batches or repeating cutovers.
Scope this migration ↗Free evidence-led tools
Don't rely on a successful transfer count alone.
Use separate tools for scope, migration safety and business sign-off. No account credentials or tenant exports required.
Check critical prerequisites
Cross-tenant readiness matrix ↗Agree what counts as done
Downloadable acceptance template ↗Plan the transfer
Illustrative bulk-copy estimator ↗Controlled change
A cutover is a business decision, not just a button.
Discover every workload
Count users, shared resources, licences and important integrations.
Map accounts and ownership
Identify target owners, permissions and unsupported items.
Stage and test the move
Choose representative pilots and review migration logs.
Cut over and reconcile
Test user access, mail flow, calendars and shared files against signed-off criteria.
The things tools can miss
Specific workstreams, not unreviewed topic lists.
These playbooks are designed around the questions an accountable IT owner should ask before agreeing a change window.
Planning and risk
What affects Microsoft 365 migration pricing?↗Technical and buyer guides
Exchange to Microsoft 365 migration↗Google Drive to SharePoint migration services↗Cross-tenant Exchange Online mailbox migration↗Practical worksheets
Migration effort estimator↗Illustrative migration risk
A copied mailbox does not prove a working team.
A change from Google Workspace to Microsoft 365 can carry separate decisions for mail, calendars, personal Drive files and Shared Drives. For a tenant split or merger, target MailUser attributes, cross-tenant licences and retention holds can prevent Exchange moves even when a source mailbox exists.
Before promising a migration date, map real dependencies and approve a test sample. See Microsoft's cross-tenant prerequisites and the illustrative copy-time estimator.
A useful first deliverable
Agree the Monday-morning acceptance tests.
For a team with shared calendars, mail delegation and externally shared documents, count users and mailboxes but also inventory the business behaviours that must work after cutover. A pilot should verify the correct access, shared documents, third-party mail senders and sign-in for representative staff. An exception report should name the owner of unsupported items instead of hiding them in a successful batch total.
Microsoft distinguishes Google-to-Microsoft workload stages from cross-tenant mailbox prerequisites. We would confirm each against the customer's platform and licences before scoping delivery.
Bring the facts, not the passwords
Get a scope that can be evaluated.
Tell us the systems you are moving, approximate users and data size, and the deadline. We'll need to review delivery capacity, licences and the actual workload before agreeing commercial terms.