How to Move Files from Google Drive to Another Cloud Storage Service
Takeout works, but it is only half the job. The other half is ownership, shared links and verifying that what arrived is what left.

Moving out of Google Drive is not difficult. It is easy to do incompletely, which is worse. The files usually survive; what gets lost is the context around them — who owned what, which links were live, which documents were shared with whom — and that is invisible until someone asks for a file you thought you had.
Plan before you move anything
Measure what you have
Check storage used and count the files. Google's storage page shows the split between Drive, Gmail and Photos — only the Drive portion is moving, and this figure tells you which plan you need on the other side.
Inventory what is shared
List files and folders shared with other people, and note who has access. This is the part people skip and later regret. Google's Drive has a shared-with-others view; capture it as a screenshot or export.
Identify what is not actually yours
Files shared with you count against the owner's quota, not yours, and you cannot move them. Either ask the owner, or accept that they will disappear from your view when your account changes.
Choose a target large enough
Account for growth, not just current usage. How much storage you need has the arithmetic.
Pick a window
Do the export when you are not relying on Google Drive for active work. Both services stay available throughout, but a long download competes for bandwidth.
Exporting your data
Two approaches, and the right one depends on how much you are moving and whether you need a complete archive.
| Method | Best for | Preserves structure | Caveats |
|---|---|---|---|
| Google Takeout | Full export, archival, large libraries | Yes, in a folder hierarchy | Split into multiple archives; slow; needs local disk space |
| Google Drive for desktop | Partial moves, fast connections | Yes, exactly | Downloads to your disk first; needs enough free space |
| Manual download | A handful of files | Only if you rebuild it | Tedious and error-prone at scale |
| Third-party migration tools | Organisations with budget | Usually | Requires OAuth access to your account; vet the vendor carefully |
Takeout is the safest option for a complete move because it produces a single dated export you can keep as an archive even after the new service is live. Request it, choose only Drive rather than every Google product, and select the archive size that suits your disk space — Takeout will split a large export into 2 GB, 10 GB or 50 GB parts.
Preserving folder structure
Takeout preserves the hierarchy inside the Drive archive, but it nests it inside an archive folder with a name you will want to strip. When you re-upload, upload the folder rather than its contents, or you will flatten a tree you spent years building.
Orindle's upload accepts folders and keeps their structure. This is the moment to fix the structure rather than reproduce it — if the old hierarchy was five levels deep and full of `New folder (3)`, reorganise it now. A migration is the only time you will ever look at all of it.
Ownership and permission limitations
This is where most migrations quietly lose things, and none of it is obvious until after the original is deleted.
- Shared links die. A Google link is a pointer to a Google file. Once the file is gone, every pasted copy of that link is broken, including ones in contracts, tickets and old emails.
- Collaboration history does not travel. Comments, suggestion mode and revision history are Google-side features. The exported document has none of them.
- Ownership changes hands. Files you owned become files you uploaded. In an organisation that matters — the account that uploaded them becomes the owner.
- Permissions are not portable. Google's sharing model does not map onto another service's. Every grant has to be rebuilt, which is the reason to inventory sharing before you start.
- Files shared with you do not come along. They belong to someone else. Copying them is fine if you have the right to; deleting them from your view is not the same as deleting them.
Large transfers
Beyond a few gigabytes, the constraint stops being storage and becomes bandwidth and patience. A few practical notes: do the download over a wired connection, expect the upload to be the slower half unless you have symmetric fibre, and split the work into batches of tens of gigabytes so a failure costs you an hour rather than a day. Takeout's multiple archives are helpful here — you can verify one part while the next downloads.
If your library is measured in terabytes, budget real time. At a typical 20 Mbps upload, one terabyte takes a little over four days of continuous transfer. That is arithmetic, not a defect in either service.
Verifying the transfer
Do not delete anything at the source until you have verified the destination. Two checks are worth doing:
Compare totals
File count and total bytes on both sides. A 2% difference is usually hidden files or Google-native exports that changed size; a large difference means something did not move.
Spot-check the important 1%
Open a handful of the files you would most regret losing — the ones that are scanned, large, or oddly formatted. This catches corruption that a file count cannot.
Test a share link end to end
Send yourself a link from the new service and open it in a private window. It confirms the link works for someone who is not signed in, which is the case that fails silently.
Keep the export for a month
A dated Takeout archive is a cheap insurance policy against discovering a missing folder three weeks later.
Final migration checklist
- Measure Drive usage and confirm the target plan is large enough, with room to grow.
- Capture a list of files and folders shared with other people.
- Request a Google Takeout export of Drive only.
- Download the archives; keep them dated and intact.
- Upload the folder (not its contents) to the new service, so the structure survives.
- Reorganise anything that was already a mess — this is the one chance you get.
- Verify file count and total size; spot-check the most important files.
- Rebuild shares, and send new links to everyone who needs one.
- Test a link as a signed-out visitor.
- Keep the Takeout archive for at least a month before deleting anything at Google.
- Only then remove the originals — and check the bin afterwards, in both services.
If you are still deciding where to move to rather than how, our comparison of Google Drive alternatives covers ten services on free space, pricing, sharing and privacy, with a checked date on every figure.
Sources
The export tool described above, including archive splitting.
How Drive, Gmail and Photos share one quota.
How folder uploads preserve structure.
Frequently asked questions
- What is the fastest way to move files out of Google Drive?
- For a large library, enable Google Takeout with the Drive archive split into multiple files and download them over a wired connection, or install Google Drive for desktop and let it download everything locally before uploading elsewhere. Takeout is more reliable for a full export; the desktop client is faster when you have a fast connection and only part of the library to move.
- Do Google Docs, Sheets and Slides convert?
- Takeout exports them as Office formats (docx, xlsx, pptx) or PDF. The content survives; the live collaboration, comments and revision history do not. Download them in a standard format and re-upload, expecting some layout differences.
- What happens to shared links after I move?
- They stop working when the original is deleted — Google's links point at Google's files. Anyone you have shared with needs a new link from the new service, and any link pasted into a document, email or ticket becomes dead. Export a list of shared files before you start.
- Does Orindle have a one-click Google Drive import?
- No. Moving files means exporting from Google Drive and uploading to Orindle — the upload flow handles large files and folders, but there is no automated migration tool. This article describes the manual path, which is the one that works today.
Written and reviewed by the Orindle team. This article is editorial content published by Orindle, which sells cloud storage. Where a competitor is discussed, the figures come from the provider's own published pages and are dated in the text. Prices and allowances change; re-check before relying on them.