Skip to main content

Zero-Downtime SharePoint to Google Shared Drives Migration with RcloneView

· 4 min read
Tayson
Senior Engineer

Keep designers, finance, and project teams working in SharePoint while you hydrate Google Shared Drives in the background--then flip the switch in one cutover window.

SharePoint Online libraries are often packed with permission-heavy folders, document sets, and regional data controls. At the same time, Google Workspace Shared Drives promise simpler collaboration and storage quotas, but the native movers rarely honor metadata, delta windows, or throttling. RcloneView wraps rclone's SharePoint and Google Drive backends in a GUI, so you can plan multi-cloud migrations with staged Compare runs, Sync + Copy jobs, mount-based QA, and scheduler-based delta passes.

RcloneView app preview

Manage & Sync All Clouds in One Place

RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.

  • One-click jobs: Copy · Sync · Compare
  • Schedulers & history for reliable automation
  • Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
WindowsmacOSLinux
Get Started Free →

Free core features. Plus automations available.

Why Plan a Zero-Downtime SharePoint -> Google Cutover

  • Distributed teams can't pause -- marketing assets, PMOs, and contracts need continuous access while the new Shared Drive is filling.
  • Granular permissions -- SharePoint libraries mix Teams-connected folders and standalone document centers; you need a repeatable way to rebuild them inside Shared Drives with clear audit logs.

A zero-downtime strategy means running multi-phase syncs while both platforms stay online, then cutting over after the final delta.

Migration Blueprint: Multi-Cloud Control Panel

  1. Connect both sides using Remote Manager along with the provider guides for SharePoint for Business and Google Shared Drives. RcloneView isolates OAuth tokens per tenant and stores them with the protections.
  2. Organize Explorer panes so each pane references a matching library vs. Shared Drive.
  3. Templates for jobs come from Create Sync Jobs and Synchronize Remote Storages. Copy jobs seed the target; Sync jobs handle onedirectional clean-up; Compare runs validate.
  4. Mounts for QA follow Mount cloud storage as a local drive, letting power users preview content inside Finder or Explorer before cutover.
  5. Schedulers + monitoring rely on Job scheduling and execution and Real-time transfer monitoring to keep delta runs predictable.
Open multiple cloud remotes in RcloneView

Step 1 -- Harden Connectors & Metadata

  • Label every remote (sp-marketing, sp-pmo, gdrive-regional-apac) and restrict the root path to the specific library. This keeps remote browsing fast inside Browse and manage remote storage.

Step 2 -- Baseline with Compare Runs

  1. Open the dual-pane Explorer, point the left side at SharePoint, right side at the empty Shared Drive.
  2. Use Compare folder contents to detect size, checksum, and timestamp deltas.
Compare SharePoint library to Google Shared Drive before migrating

Baseline Compare snapshots give you a forensic record of the original state and help identify stale subsites you might archive instead of moving.

Step 3 -- Stage Copy + Sync Jobs

  • Create a Copy job per business unit to hydrate the Shared Drive without deleting anything on SharePoint. Reference: Create Sync Jobs.
Running an encrypted sync job in RcloneView

Step 4 -- Automate Delta Windows with Scheduler

Open Scheduler, enable it globally, then assign cadences per job:

Schedule staged SharePoint to Google migration jobs inside RcloneView

Step 5 -- Cutover Day Checklist

  1. Freeze writes on SharePoint (communicate via Teams/Slack) but keep the site online for read-only needs.
  2. Run the final Sync + Compare job set. Use the Compare diff to confirm only a handful of files changed since the last delta.
  3. Mount the new Shared Drive with Mount cloud storage as a local drive and have business owners spot-check complex folder trees.
mount from remote explorer

Post-Migration QA & Mount Operations

Mount Manager lets engineers, finance, or creative leads open the new Shared Drives (or the legacy SharePoint remote) as read-only drives for auditing and training.

Project Timeline Playbook

PhaseRcloneView actionOutcome
Week 1Connect remotes, baseline Compare, create Copy jobsInventory of each library + seeded Shared Drives
Week 2Nightly Scheduler delta + Weekly Compare reportContinuous updates with drift visibility
Week 3Pilot mounts, permissions validation, user trainingStakeholders preview Google Shared Drives safely
Cutover weekSharePoint freeze, final Sync/Compare, Shared Drive go-liveMinutes of downtime with signed validation logs
2 weeks afterScheduled Sync on legacy remote + optional archival Copy to S3/WasabiProof that no files were missed before decommissioning

RcloneView turns multi-cloud migrations into a predictable playbook: set up remotes, preview differences, stage Copy + Sync jobs, automate deltas, and mount for QA. Your teams stay productive on SharePoint until the exact moment you redirect them to Google Shared Drives.

Supported Cloud Providers

Local Files
WebDAV
FTP
SFTP
HTTP
SMB / CIFS
Google Drive
Google Photos
Google Cloud Storage
OneDrive
Dropbox
Box
MS Azure Blob
MS File Storage
S3 Compatible
Amazon S3
pCloud
Wasabi
Mega
Backblaze B2
Cloudflare R2
Alibaba OSS
Ceph
Swift (OpenStack)
IBM Cloud Object Storage
Oracle Cloud Object Storage
IDrive e2
MinIO
Storj
DigitalOcean Spaces