Cloud 9 Creative

Import Under 30GB, Migration Manager for Admins: Move Google Drive to OneDrive

by | Sep 12, 2026 | AI

Administrator reviewing cloud migration status

Use OneDrive’s built-in import for a single personal account under roughly 30GB, Migration Manager if you’re an IT admin moving a whole Google Workspace domain into Microsoft 365, and a third-party tool only when permissions, metadata, or reporting fidelity really matter. All native routes copy files rather than move them, and Google Docs, Sheets, and Slides convert to Word, Excel, and PowerPoint formats automatically. Check your OneDrive storage quota and run a small test batch before committing to a full transfer.

TL;DR:

  • Native OneDrive import is ideal for personal accounts under 30GB and requires checking storage and testing small batches before full transfer.
  • Google Takeout offers better structure preservation but involves manual ZIP extraction and limits support for shared or large files.
  • Migration Manager is suitable for organizations with Google Workspace domains, providing integrated, automated transfer with compliance tools, but struggles with complex permissions.
  • Third-party tools are necessary when detailed permission mapping, metadata preservation, or ongoing sync are critical, often at a higher cost.
  • Conducting a pre-migration assessment and small test runs helps prevent permission issues, API throttling, and data loss during large-scale moves.
Cloud9
Simplify Your Digital Migration
Cloud9 helps established businesses replace fragmented digital systems with integrated cloud services, automation, and practical support.

Table of Contents

Comparing the main ways to move files to OneDrive

Four routes cover almost every situation. Each trades speed against control differently.

  • OneDrive import: free, no download, built into the web and mobile app. Best for single personal accounts moving a modest amount of data.
  • Google Takeout → Add to OneDrive: free, preserves folder hierarchy inside ZIP files. Better than the direct import when structure matters and you don’t have admin access.
  • Migration Manager (Microsoft 365 admin): free with a Microsoft 365 licence, built for organisation-wide moves from Google Workspace.
  • Third-party migration tools: paid, add scheduled sync, permission mapping, and dry-run reporting that native tools skip.

Decide by account type first: personal accounts rule out Migration Manager entirely, since it needs Google Workspace admin credentials. If folder structure and permissions fidelity both matter and you’re moving hundreds of users, skip straight to Migration Manager or a specialist tool. If you’re an individual with under 15 to 30GB and don’t care about pixel-perfect folder mirroring, try OneDrive import first. It takes minutes to test and costs nothing to fail.

How does OneDrive’s built-in import work?

Before starting, sign into OneDrive, check your available storage against your Google Drive’s total size, and back up anything genuinely irreplaceable. OneDrive’s free tier often isn’t large enough for a full personal library, so confirm headroom before you begin.

  1. Open OneDrive on the web or in the mobile app and look for the “Import from Google Drive” or “Add cloud files” option.
  2. Sign into your Google account when prompted and grant OneDrive read access.
  3. Select the files and folders to bring across, or choose to import everything.
  4. Start the transfer and monitor progress; large libraries can take hours depending on file count and size.

The import copies individual files and folders, but it does not bring across Google Drawings, Forms, Sites, or Maps, and it typically skips anything sitting in your “Shared with me” view, since you don’t own that content. Google Docs, Sheets, and Slides convert to .docx, .xlsx, and .pptx respectively during the copy.

Pro Tip: Run the import on a single small subfolder first. If it completes cleanly and the converted documents open correctly, you can re-run the process on the rest with confidence instead of finding a formatting problem halfway through a 200GB transfer.

When should you use Google Takeout instead?

Takeout suits personal accounts without admin access, or anyone who cares more about preserving exact folder hierarchy than about speed. Where the direct import can flatten or reorganise content, Takeout exports your Drive as a structured archive first.

  1. Go to Google Takeout and select only Google Drive from the list of products.
  2. Choose “Add to OneDrive” as the delivery method rather than downloading a link.
  3. Pick your maximum archive size (smaller sizes mean more ZIP files for large libraries) and set the export as a one-off.
  4. Once delivered, unzip the archive inside OneDrive and tidy up the folder structure.

Expect ZIP files that need manual extraction and a bit of housekeeping afterwards, which costs time even though the transfer itself is free. Takeout shares the same blind spot as direct import: files in “Shared with me” won’t be included, and very large drives may split across multiple ZIP archives that need reassembling.

Is Migration Manager the right choice for IT teams?

Migration Manager fits Google Workspace domain admins moving an entire organisation into Microsoft 365, not individuals switching one account. Microsoft enables a lite version of the tool by default for small and medium business organisations with limited licences, and it scales up to full enterprise migrations from there.

  • Install and authorise the Microsoft 365 Migration App inside the Google Workspace admin console.
  • Connect your Google Workspace tenant to the Microsoft 365 admin centre.
  • Run a scan across user drives to confirm what’s ready to migrate.
  • Review the “ready to migrate” report, then trigger “copy to migration” followed by the actual migrate step.

The advantage is native integration: content lands in OneDrive or SharePoint with a workflow built to work alongside Microsoft’s own governance tools, including Purview for compliance tracking. Where Migration Manager falls short is complex permission structures, custom metadata mapping, or advanced validation reporting, all of which point towards a specialist tool instead.

Do you need a third-party migration tool?

Third-party tools earn their cost when native options run out of road: complicated access control lists, metadata that needs to survive the move intact, or a genuine need for detailed before-and-after reporting.

  • Scheduled and delta sync, so ongoing changes keep flowing after the initial bulk move.
  • Dry-run modes that estimate file counts and flag naming problems before you commit.
  • Granular permission mapping between Google’s sharing model and OneDrive’s.
  • Detailed migration reports for audit and governance purposes.

Pricing usually follows one of two shapes: per-gigabyte packs for one-off jobs, or subscription tiers for ongoing sync. Advanced features like automated retry logic or granular ACL mapping tend to sit behind the paid tiers rather than free plans. Before signing anything, check where the vendor processes and stores your data, whether that meets UK or EU data residency expectations, and what the contract says about deletion after the job finishes.

Pro Tip: Ask any vendor for a written data handling policy before uploading a single file. A tool that can’t answer where your data sits during migration isn’t one you want holding company records, even briefly.

What should you check before you start migrating?

A short pre-migration audit avoids most of the failures that derail a transfer halfway through.

  1. Run a file count and rough data volume estimate on the source Google Drive, and check your OneDrive quota can absorb it.
  2. Scan for forbidden characters and excessively long file paths, both of which will cause silent failures during bulk transfer.
  3. Decide upfront how you’ll handle “Shared with me” content, since it generally can’t migrate without the owner transferring or re-sharing it.
  4. Map how Google’s sharing permissions will translate into OneDrive’s model, and test that mapping on a handful of files.
  5. Batch large migrations rather than running everything at once, since bulk operations can trigger API throttling that slows or stalls transfers.
Issue Fix before migrating
Long file paths or names Shorten paths and remove unsupported characters
“Shared with me” items Ask owners to transfer ownership or re-share directly
Permission mismatches Test mapping on a small batch first
Bulk transfer throttling Split into batches, run during off-peak windows

Set a realistic timeline and tell affected staff when the migration window opens, particularly if file access will be briefly interrupted.

How do you confirm the migration actually worked?

Validation is the step most people skip, and it’s the one that catches the problems that matter.

  • Compare file counts between source and destination rather than assuming the job finished cleanly.
  • Open a sample of converted Google Docs, Sheets, and Slides files to confirm formatting survived the .docx, .xlsx, and .pptx conversion.
  • Check that sharing links and permissions on migrated files actually point to the right people.
  • Reconfigure any sync clients pointing at the old Google Drive location so they now target OneDrive.
  • Keep original Google Drive files untouched for a defined hold period rather than deleting immediately, since Migration Manager copies rather than moves data.
  • Archive the migration report for governance and audit purposes before you clear out old Takeout ZIP files.

When does a managed migration make more sense than DIY?

Large-scale moves, strict compliance requirements, or genuinely complicated permission structures usually tip the balance towards managed help rather than a weekend of manual clicking.

  • Domain-wide migrations covering hundreds of users benefit from a structured migration playbook rather than ad hoc admin console work.
  • Dry runs before the real transfer catch naming issues and permission mismatches while they’re still cheap to fix.
  • Expect a scoped engagement: an assessment of your current Google Workspace and Microsoft 365 setup, a defined timeline, validation checkpoints, and a formal handover once migrated data is confirmed accurate.

Cloud9 works across both Google Workspace and Microsoft 365 environments, which matters when a migration touches both sides of the fence rather than a clean one-way switch.

Speed, fidelity, and governance: the real trade-off

Native tools are fast and free, which suits anyone moving a personal account with nothing sensitive attached. Once permissions, compliance, or hundreds of users enter the picture, the maths changes: a botched bulk migration costs far more in cleanup than a managed path would have cost upfront. Test everything on a small batch first, always. Governance concerns justify paying for help more consistently than raw storage size ever does.

— Rob

Get a scoped assessment before you migrate at scale

Running a domain-wide Google Drive to OneDrive migration without a dry run is how permission errors and throttled transfers turn a weekend job into a fortnight of firefighting. Cloud9 runs a proper pre-migration assessment first, tests on a controlled batch, and validates the result against your original file counts and permissions before calling the job done.

Cloud9

That matters most for organisations with complex sharing structures, compliance obligations, or Google Workspace domains running into the hundreds of users, where a missed permission mapping or an unnoticed throttling failure can sit undiscovered for weeks. Cloud9’s cloud migration support covers the assessment, the dry run, the actual migration, and the handover, so nothing gets left half-copied. If your organisation is weighing up a full move from Google Workspace to Microsoft 365, request a scoped assessment and get a realistic timeline before you touch a single file.

Sources

Before running anything at scale, it’s worth reading the primary documentation rather than relying on secondhand summaries.

Test every method on a small batch in your own admin console before scheduling a full migration window.

FAQ

Is there a way to transfer Google Drive to OneDrive?

Yes. Use OneDrive’s built-in import for personal accounts, Google Takeout’s “Add to OneDrive” delivery option to preserve folder structure, or Migration Manager for organisation-wide moves from Google Workspace.

Is there a way to sync Google Drive and OneDrive on an ongoing basis?

Native import tools handle one-off transfers rather than continuous sync; for ongoing delta sync between the two platforms, you generally need a third-party migration tool with scheduled sync built in.

Which is safer, OneDrive or Google Drive?

Both platforms use encryption and standard access controls, and safety in practice depends more on how your organisation configures sharing permissions and admin oversight than on the platform itself.

How can I migrate my Google Drive to Microsoft 365?

Individuals can use OneDrive’s import feature or Google Takeout, while organisations should use Migration Manager in the Microsoft 365 admin centre, connecting it directly to their Google Workspace domain to copy content at scale.