Technical reading library · owner-reviewed technical guides
Specific migration decisions, not dozens of duplicate keyword pages.
Choose the workload that is actually changing. Each full guide covers risks, decision tables and Microsoft source links. These documents are now approved by the owner for publication; check current vendor requirements before any production change.
What affects Microsoft 365 migration pricing?
Mailbox count is the visible number in a migration quote. The expensive variables are hidden in data, permissions, devices and the support window.
Read technical guide ↗02Google Workspace to Microsoft 365 migration services
A Google-to-Microsoft move succeeds when the business still knows where to find its people, conversations and documents on Monday morning.
Read technical guide ↗03Microsoft 365 tenant-to-tenant migration
Two Microsoft 365 tenants can look similar and still have incompatible identities, domains, holds and sharing policies.
Read technical guide ↗04Exchange to Microsoft 365 migration
An Exchange Server move to Microsoft 365 should be selected by source version, directory dependence and coexistence needs, not a universal 'mailbox copy' recipe.
Read technical guide ↗05IMAP to Microsoft 365 mailbox migration
An IMAP mailbox move is useful when the requirement really is email. It isn't a shortcut to complete calendar, contact or collaboration migration.
Read technical guide ↗06Google Drive to SharePoint migration services
The problem is not moving folders. It is preserving who owns business documents, who can open them and which Google files work after conversion.
Read technical guide ↗07SharePoint migration services
SharePoint migration is an information-architecture and permissions decision before it is a copy job. The destination must be usable by the right people after the transfer.
Read technical guide ↗08Cross-tenant Exchange Online mailbox migration
Moving an Exchange Online mailbox between Microsoft 365 tenants is not a CSV import. Check licensing, target recipient attributes and source preservation before scheduling a move.
Read technical guide ↗09Failed Microsoft 365 migration recovery
A failed migration does not tell you what failed. Diagnose the affected workload before restarting batches or changing live DNS again.
Read technical guide ↗Unreviewed research briefs are deliberately absent from this directory. A plan for a topic is not the same as a complete technical article.
Need a workbook rather than an article?
Use free migration worksheets and templates to record prerequisites and acceptance, or request a scoped migration review.