# How to Transfer Files from OneDrive to Google Drive Safely

Canonical: https://aainulraza.cloud/guides/transfer-files-from-onedrive-to-google-drive-safely/
Author: Aain Ul Raza
Published: 2026-10-21
Updated: 2026-10-27

Quick answer: Copy a small batch to a separate local folder, upload it to a private Google Drive folder, verify the contents and access, and keep OneDrive originals until every exception is resolved.

## Before you start

Goal: Move ordinary cloud files using a staged copy and a verification record before switching the working location.

First step: Inventory a small batch and classify shortcuts, shared material and special-format items separately.

Done when:
- Counts and exceptions reconcile, representative files open, and the intended people have suitable access.
- The authoritative editing location is clear while the source remains available for unresolved items.

Limit: Equal counts are only one check; provider-native formats, sharing links and dates can require separate treatment.

A cloud transfer looks finished when the upload bar disappears. The useful question comes afterward: can you find the right version, open it with the right application, and give the intended person access without exposing everything else?

This guide explains how to transfer files from OneDrive to Google Drive through a computer. It covers ordinary files you are authorised to copy, such as PDFs, photographs, Word documents and ZIP archives. It does not present a folder upload as a migration of an entire Microsoft 365 workspace. Notebooks, organisational controls, old links and collaboration history need separate decisions.

The method is deliberately staged. Keep a source, make a local transfer copy, upload a small batch, and record the evidence before changing where you work. You can use it without connecting an unfamiliar migration service to both accounts.

## Choose the right kind of transfer

Start by deciding what must move. A personal collection of ordinary files is a different job from a company library used by several people. If an employer owns the data or account, get the authorised migration route before copying it to a personal account.

| Your situation | Suitable starting point | What needs separate review |
| --- | --- | --- |
| Personal PDFs, photos and ordinary documents | A staged download and upload | File contents, paths and storage |
| Several people use shared folders | A pilot with the owners involved | Permissions, links and authoritative copies |
| OneNote notebooks or protected documents | A format specific export plan | Export support and access restrictions |
| An organisation is leaving Microsoft 365 | An administrator led migration | Identity, compliance, applications and retention |

This guide concentrates on the first row. The checks in later sections still help you discover when your collection belongs in another row. A transfer should stop for an unresolved special item instead of silently treating it as an ordinary file.

## Make an inventory before downloading

Choose one top level folder and give the batch a label, for example HomeArchive_01. Record the source account, folder path, ordinary file count, approximate bytes, and any items that need special handling. Count files inside the folder, not just the folder entries you can see at the top level.

Use an exceptions column for shared shortcuts, notebooks, items you cannot open, and files that are still being edited. A shortcut is a route to something elsewhere, so do not count its presence as evidence that the underlying content has been exported.

For a shared item, identify who owns it and whether copying is permitted. Microsoft documents restrictions on downloading directly from the Shared view and on downloading OneNote notebooks with ordinary folder downloads. Review those cases using the [current OneDrive download guidance](https://support.microsoft.com/en-us/onedrive/download-files-and-folders-from-onedrive-or-sharepoint).

The inventory is your expected result. Without it, an empty folder or a small error text file can be mistaken for a successful export. Keep the log outside the transfer batch so that uploading the log itself does not change the count you are trying to reconcile.

## Budget for the local copies as well as cloud storage

Check free space on the computer and the destination account. A local staging copy can exist alongside a downloaded ZIP, an extracted folder and files you download again for verification. The size of the source collection is not necessarily the peak space you will need.

Here is a planning example, not a measured transfer. Assume 2.4 GB of extracted files, a 1.8 GB download archive, and a 0.4 GB sample verification download. Keeping all three at once would need approximately 4.6 GB before your normal free space reserve. Compression and temporary storage vary; replace these values with the sizes you actually observe.

If you do not have enough room, divide the work into smaller batches with independent logs. Do not make room by deleting the only original you are trying to move. The [storage planning guide](/guides/how-much-cloud-storage-do-you-need/) helps separate the current collection, future growth and headroom.

## Create a real local staging folder

Choose a folder outside both cloud sync locations, for example a clearly named folder on a local drive with adequate space. It should not be an ordinary Desktop or Documents folder unless you have checked that those folders are not redirected into a cloud account.

There are two practical source routes. In OneDrive on the web, select the authorised files and download them. If the result is a ZIP, extract it into your staging folder and inspect the extracted contents. A ZIP sitting in Downloads is still an archive, not an inspected working collection.

Alternatively, if you use the OneDrive desktop app, make the chosen files locally available before copying them to the staging folder. Microsoft explains the difference between online placeholders and files kept on the device in its [Files On Demand documentation](https://support.microsoft.com/en-us/onedrive/save-disk-space-with-onedrive-files-on-demand-for-windows). Wait for the selected batch to finish downloading.

Use Copy and Paste for the staging step. Do not drag the only source collection out of OneDrive and assume that the action leaves the cloud untouched. Moving and copying have different effects. Keep the original in place while the transfer is being checked.

Open several files directly from the separate staging folder. For a document, inspect more than its first page. For a video, check playback at more than one position. For a ZIP archive, inspect its contents. An unreadable file belongs in the exceptions list even if its name and size look plausible.

## Upload into a new private destination folder

Sign in to the intended Google account and create a distinct destination folder for the pilot. Confirm the account address before uploading. A browser may already be signed in to more than one account, and a successful upload to the wrong account is still the wrong result.

Choose a location whose effective access you understand. A new folder under an already shared parent is not a substitute for a private staging location. Google explains inherited access in its [folder sharing documentation](https://support.google.com/drive/answer/7166529?hl=en).

Google's [file and folder upload instructions](https://support.google.com/drive/answer/2424368?hl=en) cover browser uploads and the conversion setting for Office documents. For the first verification pass, keep ordinary files in their existing formats. If you later decide to convert them, treat conversion as a second change to test.

A fresh pilot folder also reduces filename collisions. Do not casually merge an unknown upload into a folder that already contains files with the same names. Review any replace, revision or keep both choice before proceeding. The correct action depends on whether you are adding a new item or updating the same intended document.

## Use a three layer verification record

A transfer is easier to judge when you separate completeness, content and access. Passing one layer does not imply that the others passed.

| Layer | What to record | What the result does not prove |
| --- | --- | --- |
| Completeness | Expected files, received files and exceptions | Equal counts do not prove equal contents |
| Content | Files opened and any unchanged binary files compared | A sample does not verify every untested file |
| Access | Correct account and intended recipient test | Owner access does not prove recipient access |

First reconcile the batch inventory. If you expected 103 ordinary files, identify what you actually received. An unexpected extra error file should not be used to make a missing original disappear from the arithmetic. Keep empty folders and special items on separate lines when your tools count them differently.

Next open representative destination files from Google Drive. Include the largest item, an unusual format, a deeply nested item, and something important enough that a damaged copy would matter. Record the exact filenames and the result, rather than writing all checked after looking at one PDF.

For an unchanged binary file, you can download the destination copy into another separate folder and compare its SHA256 hash with the staged source. A matching hash is strong practical evidence that the compared file bytes match. It does not check permissions, external spreadsheet links, or the meaning of the document. Conversion can legitimately change bytes, so compare like with like.

For irreplaceable material, increase the verification scope. A sample is a sensible pilot, but it is not a claim that every photograph or archive was checked. If you cannot verify everything now, write down that limit and retain the source.

## Worked example: 103 ordinary files and two exceptions

Consider an illustrative family archive with the following inventory. These numbers demonstrate reconciliation; they are not a benchmark or a customer result.

| Group | Expected ordinary files | Separate handling |
| --- | --- | --- |
| Documents | 36 | None recorded |
| Photos | 60 | None recorded |
| Videos | 4 | None recorded |
| ZIP archives | 3 | Open the archives during review |
| Other items | 0 | One notebook and one shared shortcut |
| Total ordinary files | 103 | Two unresolved special items |

Suppose the first extracted download contains 102 ordinary files plus a text file describing a notebook export problem. You do not have 103 successfully transferred originals. You have a missing ordinary file to locate and a known notebook exception. The text file documents an issue; it does not replace the missing content.

After finding the missing PDF, repeat only the affected batch. The final ordinary file reconciliation can then read expected 103, staged 103, received 103, sampled 8, exceptions 2 special items. The sample count stays visible instead of being described as complete verification.

Write an acceptance decision: ordinary files received and the eight listed samples opened; notebook and shared item remain in OneDrive pending separate handling. That is a useful partial result. Calling the entire account migrated would hide the unfinished work.

## Rebuild access and decide where editing happens

A downloaded file is a copy of file contents. Treat old OneDrive sharing links, comments and earlier versions as separate migration requirements. Do not assume that putting the latest file into Google Drive recreates those relationships or brings over the original history.

If you need an earlier version, identify it before leaving the source account and use the relevant export or recovery method. Google's [version history guidance](https://support.google.com/drive/answer/2409045?hl=en) distinguishes ordinary stored files from Google Docs editor history. Review the history that exists at each destination instead of assuming the two products share one record.

For collaboration, choose one destination document, set the intended role, and ask the recipient to test using their own permitted account. An owner opening the file does not prove a recipient can open it. Check the exact URL that will be sent, not only the folder where you intended to put it.

Then set a switching point: from a named date, new edits happen in Google Drive. Leave a clear note in your own project records and update links you control. Editing both locations after the pilot creates two diverging versions, which is a separate problem from incomplete copying.

## Decide when the originals can be retired

Keep OneDrive until the acceptance record covers the files, exceptions, required history and access tests. There is no universal number of days that proves a migration is safe. A week without a complaint is weak evidence if nobody tried to open the important archive.

Before deleting or cancelling anything, confirm that an independent recovery copy exists where needed and that you can reach it. A destination in a second cloud account can help with availability, but a migration and a [recoverable backup plan](/guides/sync-is-not-your-whole-backup-plan/) answer different questions.

If a batch fails, keep working from the authoritative source, record what failed, and retry into a distinct destination batch. Do not solve an unexplained count difference by deleting files until the numbers match. The purpose of the log is to explain the difference, not conceal it.

## Questions that usually cause confusion

### Is there a way to move directly between the services?

There are services and organisation specific migration routes. This article explains a local staged method and does not evaluate those providers or ask you to grant them account access. A company migration should use its approved process.

### Can I delete OneDrive as soon as uploading finishes?

Wait until the content, access and exception checks are complete and any required recovery copy is usable. The end of an upload is evidence about that upload, not a complete account retirement test.

### Why do equal file counts still need checking?

Counts can hide a missing original and an unexpected extra file. Even a perfect name list says little about an unreadable archive or a recipient's access. Reconcile names and exceptions, then check the relevant contents and permissions.

### Will file dates and appearance stay exactly the same?

Distinguish the date displayed by a cloud service from the contents and embedded metadata of a file. Do not use a matching displayed date as proof of a successful copy. If an application's formatting or metadata matters, include that application and file in your pilot checks.

## Keep the evidence beside the batch

[Download the cloud transfer verification log](/resources/cloud-transfer-verification-log.txt). It has separate spaces for expected counts, observed copies, sampled files, access checks, unresolved items and the decision to switch. Keep secrets and sensitive document contents out of the log.

Method and scope: this is an original planning workflow with an illustrative reconciliation example. Provider behaviour was checked against the linked Microsoft and Google support pages on 21 October 2026. No live account migration, transfer speed comparison or account wide verification is claimed. AI assisted drafting and technical review were used; the [editorial policy](/editorial-policy/) explains that process and how to request corrections.

Examples and checking methods: https://aainulraza.cloud/methods/