9 followers
9 followers
Big migrations fail in boring, specific ways. Here's what actually goes wrong, and the small number of things that have to be right.
Anyone can move ten files between clouds. Moving half a terabyte tens of thousands of files, nested folders, the odd 4 GB video in the middle is a different animal, and it fails in ways that only show up at scale.
I've watched these migrations break, so here's the honest list of what goes wrong and what has to be true for it not to.
1. The "download everything first" approach collapses under its own weight.
The full-storage warning isn't about space. It's about being locked into one account with nowhere to put the overflow.
You know the message. "Your storage is 98% full." A little red bar, a button that says Get more storage, and a monthly price that quietly went up since you signed up.
Here's what that bar is really telling you: every new photo, every shared document, every phone backup is now competing for the same shrinking room in one account, from one provider, on their terms. The warning feels like a storage problem. It's actually a concentration problem. You put fifteen years of your life in a single place because it was easy, and now moving out feels impossible.
So most people do the only thing that seems available: pay more. The bar goes green for a few months. Then it's red again, at the next price tier.
There's a quieter option nobody advertises, because nobody selling you storage benefits from you knowing it: you probably already have space elsewhere. A Dropbox you barely use. A OneDrive that came free with your laptop. An S3 or Backblaze bucket that costs a few dollars a terabyte. The room exists it's just scattered across accounts that don't talk to each other.
The hard part was never space. It was movement. Getting 200 GB out of one full account and into another has traditionally meant downloading all of it to your laptop first filling up your local disk, tying up your internet for a day, and hoping nothing drops halfway.
That download-to-your-machine step is the part that shouldn't exist. Both clouds are already on the internet. The file should go straight from one to the other.
That's the whole idea behind what I built. You connect the account that's full and the account with room, pick what to move, and it streams cloud to cloud the bytes never touch your computer, and never sit on our servers either. A folder of RAW photos leaves the full account and lands in the spare one while your laptop is closed.
The full-storage bar stops being a countdown to a bigger bill. It becomes a routing decision: this stuff can live over there instead.
If your red bar is back again this month, that's the reframe worth trying before you tap Get more storage one more time.
I'm the maker happy to answer any "but what about my setup?" question in the comments, including the ones where the honest answer is "not yet."
