onedrive

OneDrive is good at keeping files available across your devices. It is not a separate backup. A deleted folder, a compromised account, or a bad sync can reach every device connected to the same account.

Backblaze B2 gives you a copy outside Microsoft's ecosystem. Blober can now read OneDrive through Microsoft Graph and write those files directly to B2, so you do not need to download the whole library first.

OneDrive Files On-Demand keeps online-only files as placeholders on your disk. They look like ordinary files in Finder or File Explorer, but the content stays in Microsoft's cloud until something opens the file.

That saves disk space. It also means a backup tool that reads only the local OneDrive folder may see a placeholder instead of the file itself. The usual workaround is to select "Always keep on this device" and wait for OneDrive to download everything. For a large account, that can take hours and may not fit on the computer at all.

Blober avoids the local folder. It requests each file from OneDrive through Microsoft Graph, then streams it to Backblaze B2 through your computer. Files On-Demand does not enter the path.

The useful part is separation. Your working files stay in OneDrive, while the backup lives under a different provider and account. B2 also uses S3-compatible object storage, which suits archives that you expect to keep longer than you actively edit them.

This transfer copies files and folders. It does not reproduce Microsoft sharing permissions, version history, comments, or recycle-bin contents.

1. Connect Microsoft OneDrive in Blober.
2. Connect Backblaze B2 with your key ID, application key, and bucket.
3. Create a workflow with OneDrive as the source and B2 as the destination.
4. Choose the OneDrive folder and the destination path in your bucket.
5. Start the workflow and keep Blober open until it finishes.

Blober recreates the folder structure in B2. The data passes through the computer running Blober, but it is not staged as a second full copy on disk.

Blober reads the signed-in user's default OneDrive. That includes ordinary files and folders in "My files." It does not include "Shared with me," SharePoint or Teams libraries, OneNote notebooks, Personal Vault, or shortcuts to another drive.

If a shared file must be part of the backup, first download it and upload it to your own OneDrive as an ordinary file. An "Add shortcut to My files" shortcut is still a reference to another drive, so Blober skips it.

Do I need to mark every OneDrive file "Always keep on this device"?

No. Blober reads the cloud copy through Microsoft Graph rather than backing up the local OneDrive sync folder.

Does the transfer need free disk space equal to my OneDrive library?

No. Files stream through the computer running Blober and are not stored there as a complete intermediate copy.

Is Backblaze B2 a full OneDrive clone?

No. It receives the files and folder structure. OneDrive permissions, links, comments, version history, and deleted items do not transfer.

Can Blober include files shared with me?

Not from OneDrive. Microsoft's old "Shared with me" Graph endpoint is deprecated, requires broader access to read remote items, and will stop returning data after November 2026. Blober keeps the narrower Files.ReadWrite permission and reads only the signed-in user's drive.

• The 3-2-1 backup rule for people who live in the cloud
• What S3-compatible really means
• OneDrive setup

Move your OneDrive files to Backblaze B2 without first filling your disk.

Download Blober at blober.io

Changing cloud storage is usually part of a bigger move. A company adopts Google Workspace, a school issues Microsoft 365 accounts, or a family decides it no longer wants to pay for two storage plans. The files are only one part of that decision, but they are the part that has to come with you.

Blober transfers files in either direction between OneDrive and Google Drive. It streams them through your computer, so you do not need enough free disk space to download the entire account first.

Google Drive fits best when most work already happens in Gmail, Google Docs, Meet, and Calendar. A move from OneDrive can make sense when:

• your company or school has standardized on Google Workspace;
• people collaborate mainly in Docs, Sheets, and Slides;
• Chromebooks or browser-based work have replaced Windows desktops;
• you want storage billed under an existing Google One or Workspace plan.

Office files do not have to be converted during the transfer. Word, Excel, and PowerPoint files arrive in Google Drive as .docx, .xlsx, and .pptx files. Google can open and edit them, and you can choose later whether to convert them to native Google formats.

OneDrive is the more natural home when work revolves around Windows, Microsoft 365, Teams, and the desktop versions of Office. People commonly move in this direction because:

• their organization has moved to Microsoft 365;
• Office formatting needs to survive round trips without surprises;
• Teams and SharePoint are now the main places where people collaborate;
• OneDrive storage is already included in a Microsoft 365 plan.

The main catch is Google's native file formats. A Google Doc is not a normal .docx file sitting in Drive. When Blober moves native Google files out of Drive, it exports Docs to .docx, Sheets to .xlsx, and Slides to .pptx. Those copies open in Microsoft Office, but Google comments, revision history, sharing rules, and some format-specific features do not come with them.

Source	Destination	File behavior
OneDrive	Google Drive	Office files and other regular files keep their existing formats
Google Drive	OneDrive	Native Docs, Sheets, and Slides export to Microsoft Office formats
Either service	The other service	Folder structure is recreated; sharing rules, links, comments, and version history are not

There is one difference around shared files. Blober exposes Google Drive's "Shared with me" list as a read-only source. OneDrive does not offer an equivalent usable root through the narrow permission Blober requests, so its shared items and cross-drive shortcuts are not shown.

1. Connect OneDrive with a Microsoft app client ID.
2. Connect Google Drive.
3. Create a workflow with OneDrive as the source and Google Drive as the destination.
4. Select the source folder and destination folder.
5. Run the workflow and keep Blober open until it finishes.

After the transfer, open a sample of Word, Excel, and PowerPoint files in Google Drive before closing the old account. Decide whether to leave them in Office format or convert the files you still edit.

Use the same process in reverse: choose Google Drive as the source and OneDrive as the destination. Include "Shared with me" only for files you are allowed to copy and want to keep. Native Google files are exported during the transfer.

Check a few converted documents, spreadsheets, and presentations in Microsoft Office afterward. Complex layouts, formulas, fonts, and embedded Google-only features deserve a manual look.

Compare file counts and inspect the folders that matter most. Keep the old account available until you have checked converted documents and confirmed that other people can reach the new location.

Then recreate sharing permissions in the destination. File ownership, organization policies, public links, and team memberships belong to the old service and cannot be carried over as ordinary files.

Can I move between OneDrive and Google Drive without downloading everything?

Yes. Blober streams each file through the computer running the app instead of staging the whole library on disk.

Will Google Docs work in OneDrive?

Blober exports Google Docs, Sheets, and Slides to Word, Excel, and PowerPoint formats. Check complex files after conversion because the two editors do not support every feature in exactly the same way.

Will Office files become Google Docs automatically?

No. They arrive in Google Drive as Office files. Google Drive can edit them in that format, or you can convert selected files later.

Does the migration copy shared files?

Google Drive's "Shared with me" items can be selected as a read-only source. OneDrive's "Shared with me" items and shortcuts to other drives are not available in Blober.

Move the files once, check the result, and finish the ecosystem switch without renting a permanent sync service.

Download Blober at blober.io

GoPro Cloud, iCloud, OneDrive, and an external drive can all hold video. That does not make them interchangeable.

GoPro Cloud is built around camera upload and Quik. iCloud is built around Apple devices and photo libraries. OneDrive is built around ordinary files, Windows, and Microsoft 365. An external drive is local storage that you own and manage.

The useful comparison is not "which one is best?" It is "which one should capture, share, and archive the footage?"

GoPro Cloud has the cleanest path from a compatible GoPro camera into an online library. When the camera charges on a saved Wi-Fi network, it can upload new footage for use in Quik.

The tradeoff is account dependence. The cloud benefit follows the subscription. Unlimited storage also applies to compatible GoPro-captured footage, not every file from every camera.^[1]

Use it when automatic camera ingestion and Quik editing matter. Keep another copy when the footage matters beyond the current subscription.

iCloud Photos keeps full-resolution originals in the cloud and can leave smaller device copies when Optimize Storage is enabled. Apple documents support for HEIF, JPEG, RAW, PNG, GIF, TIFF, HEVC, and MP4.^[2]

That covers common GoPro MP4 and HEVC video, but Apple's published list does not include GoPro's GPR RAW format or 360 project formats. Check a real sample before moving an unusual camera library.

iCloud is a good fit when the footage belongs in an Apple Photos workflow. It is less useful when editors, clients, or archive machines work outside that ecosystem.

OneDrive treats footage as files inside folders. That makes it easier to place video beside project documents and share it through Microsoft 365.

Microsoft currently documents a 250 GB maximum per file. It also recommends keeping normal sync workloads below 300,000 items for best performance, with a newer Windows-only preview raising the supported count for qualifying systems.^[3]

OneDrive is practical for active projects and familiar Windows folders. A large archive may need more planning around capacity, item counts, and sync behavior.

An external drive has no cloud subscription and works without internet access. It is often the fastest place to edit large video files.

One drive is not a complete backup. Drives fail, cables are pulled, and portable disks are easy to lose. Keep at least one more copy in another physical location or cloud account.

For many GoPro users, the clean setup uses more than one destination:

• GoPro Cloud receives footage from the camera.
• A computer or fast external SSD handles editing.
• OneDrive or iCloud holds active shared work when it fits the team.
• A second drive, NAS, or object-storage account holds the long-term archive.

Blober can move the GoPro Cloud library into local storage or another provider. That lets the camera workflow stay convenient without making the subscription the archive's only home.

• GoPro Cloud vs Dropbox vs Google Drive
• Best Cloud Storage for GoPro Footage
• GoPro Cloud Storage: The Complete Guide
• Back Up GoPro Cloud to Backblaze, S3, or Local

Let each service do the job it is good at, then keep the archive somewhere you control. Blober moves your GoPro Cloud library to local storage, a NAS, or another cloud provider.

Download Blober at blober.io