How to Move Files from OneDrive to Google Drive Without Downloading Them

Four practical methods, the three things that silently break during the move, and how to prove nothing was lost.

Updated September 2026 · About 8 minutes

The obvious way to move a cloud account is to download everything and upload it again. It works until the numbers get real: 300 GB of OneDrive will not fit on a 256 GB laptop, and even when it fits, you pay for the same bytes twice — once down, once up.

You do not have to do that. Both Microsoft and Google expose APIs, so a transfer tool can read a file from one and write it to the other, streaming it through your network connection without ever writing it to your disk. This guide covers the four options that actually exist in 2026, what each one costs, and the parts of the migration that no tool handles for you.

The four options, compared

Before you start: 15 minutes that save you a weekend

Every failed migration I have seen failed at the edges, not in the middle. Write down these four things first, in a spreadsheet:

1. Top-level folders, with size and file count. In OneDrive on the web, this is the folder list plus the size column. You will compare against these numbers at the end — it is the only honest way to know the transfer finished.
2. Everything currently shared. OneDrive → Shared → Shared by you. Shared links do not migrate. Anything on this list is a message you will have to send someone later.
3. Google-native files living in Drive already. Google Docs, Sheets and Slides are not real files; they only exist inside Drive. They do not move to OneDrive, and they do not come back as themselves.
4. What you are not taking. Installers, old exports, duplicate backups, screenshots from 2019. Deleting before a move is the cheapest speed-up available — cutting 30% off the total takes ten minutes and removes 30% of everything that can go wrong.

If this is a work account and you are leaving the company, the rules are different before the technical question even comes up: "I made it" is not the same as "I may keep it." Copy only what you are allowed to keep, get the permission in writing from your manager, and do it weeks before your last day rather than on it. A dedicated guide for that case is in progress.

Method 1 — Download and re-upload (only for small moves)

Install both sync clients, let OneDrive download the folders you want, then drag them into the Google Drive folder and wait for the upload. It is the only method that needs no third-party tool, and it is genuinely fine under about 5 GB.

What to watch for if you do it anyway:

• Files must be fully downloaded, not "online-only" placeholders. In File Explorer, right-click the folder → Always keep on this device, and wait for the solid green checkmarks. Copying placeholders gives you 0 KB files.
• Turn off sleep during the transfer. Set the display to sleep, not the machine.
• Windows path length still bites: deeply nested folders can fail at 260 characters. Move the folder near the root of the drive first.

Method 2 — rclone (free, and the fastest if you are comfortable in a terminal)

rclone is an open-source command-line tool that speaks to both providers. It streams file contents through your machine's memory and network, not your disk, so free disk space is irrelevant.

Set up both ends once:

rclone config
# n) New remote → name: onedrive  → storage: onedrive  → follow the browser login
# n) New remote → name: gdrive    → storage: drive     → follow the browser login

Look before you leap, then copy:

# See what is there, and how big it is
rclone size onedrive:Work
rclone lsd  onedrive:

# Dry run first — prints what WOULD be copied, transfers nothing
rclone copy onedrive:Work gdrive:Work --dry-run

# The real thing
rclone copy onedrive:Work gdrive:Work \
  --progress \
  --transfers=8 \
  --drive-chunk-size=64M \
  --log-file=migration.log --log-level INFO

Three flags matter more than the rest:

• copy, not sync. copy adds to the destination and never deletes. sync makes the destination match the source — including deleting things at the destination. Use sync only when you understand exactly that.
• --transfers=8 is a reasonable starting point. Higher is not faster once the provider starts rate-limiting you; if you see 403 or "user rate limit exceeded" in the log, lower it.
• --drive-chunk-size=64M speeds up large-file uploads to Google at the cost of memory (each transfer holds one chunk).

If the run stops — laptop sleeps, Wi-Fi drops, API quota — just run the same command again. rclone compares each file and skips what already arrived, so a resumed run is cheap.

Afterwards, verify with the tool itself:

rclone check onedrive:Work gdrive:Work --size-only --one-way

Method 3 — Web migration services

MultCloud, CloudFuze and cloudHQ run the transfer on their own servers. The advantage is real: you can close your laptop and the job keeps running, and they handle scheduled, repeating sync between clouds.

The trade-offs are equally real, and worth stating plainly before you sign up:

• They hold your OAuth tokens. Access to both accounts sits on their infrastructure until you revoke it. For a corporate tenant this is usually a conversation with IT, not a personal decision.
• The pricing is a subscription — around $9.90/month at the low end — for what is often a one-week job. Remember to cancel.
• Free tiers are capped in GB per month, and the cap is usually below what a real migration needs.

Method 4 — A desktop transfer app

This is the middle ground between rclone and a subscription service: a normal application with checkboxes that talks to both APIs directly from your machine. Nothing lands on your disk, the tokens stay in your own OS keychain, and there is no monthly bill.

The three things that break, whichever method you pick

1. Sharing and permissions do not travel

A share is a property of the file object at the provider, not of the bytes. Every OneDrive link keeps pointing at the OneDrive copy, and the new Drive copy starts private. Plan for it: share the new copies, send the new links with a sentence saying when the old ones stop working, and keep the old side readable for 30 days.

2. Google-native files have no OneDrive equivalent

Going the other direction (Drive → OneDrive), Google Docs must be exported to .docx/.xlsx/.pptx — most tools do this automatically, and formatting drifts in complex documents. Coming to Drive, your .docx and .xlsx files stay .docx and .xlsx unless you convert them deliberately; Docs and Sheets open them in Office-compatible mode, so there is no reason to convert anything during the move.

3. Names, versions and hidden files

• Version history stays behind. Only the current version transfers. If an old version matters, download that version before you start.
• Google Drive permits two files with the same name in one folder; Windows and OneDrive do not. Coming from OneDrive this is harmless; going back the other way it creates surprises.
• .DS_Store, desktop.ini, and zero-byte files inflate or deflate counts. Excluding them is fine — just remember you did, so the final count still adds up.

Verify, then delete — in that order

1. Compare file count and total size per top-level folder against the numbers you wrote down at the start.
2. Open five files that would genuinely hurt to lose. Not a sample of five random files: the five that matter.
3. Re-share what was on your sharing list and send the new links.
4. Only now, make the old side read-only. Delete it 30 days later, not the same day.
5. If you are cancelling a paid plan, do it after all of the above, and at least three days before the renewal date.

That order is the whole trick. The failure mode people actually hit is not a broken transfer — it is deleting the source on the same day the transfer "looked finished."

FAQ

Can I really move 500 GB without free disk space?

Yes. rclone and direct-transfer apps stream each file through memory and the network. Your disk usage stays flat for the whole run. What you do need is time and a stable connection — expect roughly 50–150 GB per hour per account, limited by provider API throttling rather than your bandwidth.

Does running it in parallel make it faster?

Only up to a point, and only across different accounts. Both providers throttle per account, so eight parallel transfers on one account will not beat four — it will just start returning rate-limit errors.

Should I use copy or move?

Copy, always, for the first pass. Move deletes at the source as it goes, which means a failure halfway through leaves you with a half-empty source and a half-full destination and no easy way to tell which is which. Copy, verify, then delete.

My company uses SharePoint, not personal OneDrive. Same thing?

The mechanics are the same, the mapping is not: SharePoint sites and Teams channels become shared drives on the Google side, and personal OneDrive becomes My Drive. Decide that mapping — and who verifies each department — before you transfer a single byte.