A team copies its Google Drive into SharePoint and sees a completed migration task. Then a department cannot open its working folder, an external partner's link stops working and a spreadsheet behaves differently after conversion. The files arriving is only one part of the move. Permissions, links and daily work need their own acceptance checks.
Microsoft Migration Manager supports moving Google Workspace content into Microsoft 365 destinations, including SharePoint. Use the native tool for the supported transfer and build your migration plan around its documented boundaries. The inventory, testing and cutover controls below are recommended engineering practices, not a promise that every Google feature has an identical destination behavior.
Start with a drive and destination inventory
List the personal and shared drive paths in scope, their business owners and the SharePoint locations that will receive them. A folder name alone is not a sufficient destination decision. Record the site, document library and any target folder, along with the team responsible for approving the result.
Keep personal working content and shared departmental content distinct in the mapping. A department owner should confirm where shared material belongs. Do not let an automatically suggested path make that business decision. In the standard Migration Manager workflow, source paths are automatically mapped to exactly matching destination paths, and administrators must review them.
Use the Google Workspace entry under Microsoft 365 admin center migration resources to start. Arrange authorized access to both environments before connecting. Microsoft's overview identifies SharePoint or OneDrive admin, Migration Administrator or Global admin access for the destination and an authorized Google Workspace administrator for the source. Choose the least privileged role suitable for the work.
Scan first, then investigate the item reports
The standard workflow connects Google, scans selected drives, adds ready drives to the migration list, reviews destinations, maps identities and starts migration. Migration Manager Lite presents a different guided flow. It still includes task selection, destination assignment, identity mapping and migration settings, rather than presenting all the standard stages separately.
Use scan reports to investigate transfer problems before the full run. Keep a separate exception list with an owner and disposition for each issue. Some content may need another preservation method. Other items may be intentionally excluded after the business owner reviews them.
Define what happens to each content type
| Source content | Documented migration behavior | Recommended acceptance check |
|---|---|---|
| Google Docs, Sheets and Slides | Converted to Word, Excel and PowerPoint formats | Open important documents and test their working behavior |
| Google Drawings | Converted to PNG files by default | Decide whether an image preserves the needed use |
| Google Sites and Maps | Not migrated from Google Drive | Agree a separate preservation or replacement plan |
| Google Forms | Supported with a Forms destination configured | Assign the destination user and test the resulting form |
| Shortcut files | Skipped in Google migrations | Inventory important navigation paths separately |
Do not classify every Google-native file as unsupported. Docs, Sheets and Slides have a conversion route. Also do not assume conversion proves equivalent behavior. Ask users to test the formulas, layouts and collaboration patterns they actually depend on. Record the result against the original item, not just a screenshot of the target folder.
Review destinations before the first transfer
A migration task needs a destination, and Microsoft says the destination cannot be modified once migration to it starts. Review the mapping before that first run. For large mappings, Migration Manager supports uploading destinations through a CSV template and validating them. Rows with blank destination paths are skipped in validation, so a clean validation report does not explain a blank mapping.
There is a specific permission exception at a SharePoint document library root. Source root-folder permissions are not migrated when the library itself is the destination. Microsoft's guidance is to create a folder inside the library and use that folder when those root permissions need to move.
Keep this destination register under change control during the migration. A late site or folder redesign can create new work even when the transfer settings remain unchanged. Resolve the structure before the final copy rather than reorganizing both environments while people are still editing.
Separate identity mapping from permission settings
Map Google users and groups to the intended Microsoft 365 identities. For shared drive groups, Microsoft recommends recreating a Microsoft 365 group with the same membership and mapping the source group to it. Review actual membership as part of approval rather than trusting a similar group name.
File-level permission migration is off by default. Without it, destination files inherit their parent folder permissions. Folder and file controls are separate decisions, so successful identity mapping alone does not prove that individual file restrictions survived.
Migration Manager does not recreate external sharing links or automatically share content with external collaborators. Keep an approved list of required external access and recreate it deliberately in the destination. Test both allowed and denied access using representative accounts. Include someone outside the owning department to check that restricted content did not become broadly visible.
Choose version and delta behavior deliberately
The default version setting copies only the most recent file version. If older versions matter, configure File versions in Project Settings or the applicable task settings before migrating. Verify the required history at the destination before retiring the source. Do not treat a current file copy as proof that its older versions were transferred.
After an initial completed task, selecting Migrate again starts a delta sync. Default behavior considers new or modified source files. A destination file with a newer modification time is not overwritten, even if the source also changed. Renaming source or destination paths can create additional copies instead of the structure you expect.
Permission-only changes may not transfer in the default mode because permissions update when the corresponding file transfers. The option to transfer all files and overwrite destination files can carry those changes, but it also overwrites destination edits. Have an owner approve that tradeoff before choosing it.
Run a cutover checklist people can verify
- Approve the scope, destinations, access map and unresolved exclusions.
- Test a representative transfer with document owners and restricted users.
- Agree when source and destination editing must stop for the final reconciliation.
- Run the chosen delta process without changing paths during the transfer.
- Review item errors, required version history, converted files and external access.
- Switch working links and integrations only after the owners accept the results.
Keep source access available for the agreed validation period. Migration Manager copies rather than deletes source data, but your own retirement process can still make recovery difficult. Plan the reference access and any subsequent edits before changing user instructions. Our data migration work covers reconciliation and application handoffs alongside the transfer.
How Remqa can help with the migration
Remqa can help map drive content to SharePoint destinations, organize exceptions and build checks around files, access and the final working process. The project can include integration changes and user acceptance tests rather than stopping at a completed task. Explore our migration services or bring a sample drive and target library to an engineering call. Agree what a successful move means before starting the full copy.