I built a tool that moves your Google Drive files between accounts. Here’s how I made it safe enough to trust.

说明与用途

Spillover 允许您安全地在 Google Drive 账户之间移动文件，使用哈希验证、回收站撤销和本地事务日志。

问题

The author’s main Google account hit the 15 GB free limit while alternate accounts were empty, requiring a way to rebalance storage across accounts without risking data loss.

结果

Spillover enables safe, reversible, and auditable transfer of Google Drive files between a user’s own accounts, preventing accidental data loss and respecting Google’s API limits.

工作流

• 1. Run spillover run to preview the plan; no files move until --execute is passed and confirmed.
• 2. For each file, download → compute SHA‑256 hash → upload to destination → verify hash matches downloaded bytes.
• 3. If verification succeeds, trash the source file; otherwise log failure and leave source untouched.
• 4. Trashed files remain in the source account’s trash for 30 days, allowing recovery.
• 5. If the process crashes, run spillover resume to continue from the first unfinished transaction stage.
• 6. All moves are recorded in a local SQLite ledger for audit and lookup.

证据

spillover run only ever previews the plan. Nothing moves until you pass --execute — and even then it asks for confirmation.

来源

This is the core guarantee: a source file is trashed only after the destination copy’s SHA‑256 hash matches the downloaded bytes.

来源

Even after verification, originals go to the source account’s trash — not permanent deletion.

来源

Every file is tracked as a transaction: pending → in_progress → done/failed, with the last completed stage recorded.

来源

Every move (done, failed, or skipped) lands in a local SQLite ledger: filename, size, hash, source → destination.

来源

1GB safety buffer per account — a destination is never filled to the brim.

来源

Since March 2025, Google blocks third‑party apps from reading your full photo library and provides no delete endpoint — so no tool on earth can fully automate Photos moves in 2026.

来源