Office 365 Migration to Google
Budget: $250 – $750 USD
I am preparing to leave Office 365 behind and run the entire stack on Google Workspace. The move covers three core workloads:
• Email: All Outlook / Exchange Online mailboxes, calendars, contacts and aliases must land in Gmail with zero-loss and minimal downtime.
• File Storage: Every OneDrive file—versions, sharing permissions and metadata included—needs to appear in the right Google Drive locations (My Drive or shared drives as appropriate).
• Collaboration Sites: Current SharePoint sites and libraries have to be re-created or migrated into equivalent Google Workspace options (Shared Drives, Google Sites, or Drive-based folders) while preserving structure and access rights.
You may use native Google Workspace Migration tools, MigrationWiz, GAM, or any proven method; just outline your plan so I can approve it before execution. Please stage the work in a test workspace first, provide a rollback strategy, then run the live cut-over during an agreed maintenance window.
Acceptance will be based on:
– 100 % mailbox, file, and permission parity verified by spot-checks I perform.
– A post-migration report summarising steps taken, issues found, and final data counts.
– A brief hand-off session (recorded) showing me where everything now lives and how to manage it going forward.
If this sounds straightforward to you, let’s discuss timelines and any prereqs you need from my side.
• Email: All Outlook / Exchange Online mailboxes, calendars, contacts and aliases must land in Gmail with zero-loss and minimal downtime.
• File Storage: Every OneDrive file—versions, sharing permissions and metadata included—needs to appear in the right Google Drive locations (My Drive or shared drives as appropriate).
• Collaboration Sites: Current SharePoint sites and libraries have to be re-created or migrated into equivalent Google Workspace options (Shared Drives, Google Sites, or Drive-based folders) while preserving structure and access rights.
You may use native Google Workspace Migration tools, MigrationWiz, GAM, or any proven method; just outline your plan so I can approve it before execution. Please stage the work in a test workspace first, provide a rollback strategy, then run the live cut-over during an agreed maintenance window.
Acceptance will be based on:
– 100 % mailbox, file, and permission parity verified by spot-checks I perform.
– A post-migration report summarising steps taken, issues found, and final data counts.
– A brief hand-off session (recorded) showing me where everything now lives and how to manage it going forward.
If this sounds straightforward to you, let’s discuss timelines and any prereqs you need from my side.
Related categories:
.NET
Project Management
C# Programming
Sharepoint
Microsoft
Office 365
Technical Documentation
Data Backup