The biggest obstacle to simplifying your digital system isn’t technical — it’s emotional. The fear of losing something. The idea that buried in those notes you haven’t reviewed in two years there’s something valuable, that in the tool you’re about to eliminate there’s information you’ll someday need. That fear paralyses. And while you’re paralysed, you keep maintaining tools you don’t use, paying subscriptions you don’t benefit from and dragging complexity you don’t need. This chapter gives you a method to migrate without losing what matters — and to let go of what doesn’t.

The Fear Of Losing

Attachment to information is a form of digital hoarding that operates with the same logic as physical hoarding. “I won’t throw it away because I might need it.” “I won’t delete this app because it has data from three years ago.” “I won’t consolidate because I don’t want to lose anything.”

But ask yourself honestly: of all the information you’ve saved in the past five years, what percentage have you actually gone back to consult? Research suggests that most people access less than 10% of the information they archive. The other 90% exists only as weight — digital weight, mental weight, operational weight.

That doesn’t mean you should delete everything without looking. It means that most of what you think you can’t lose, you’ve actually already lost — because you never go back to look for it. What you genuinely need is far less than you think.

The fear of losing also feeds on a cognitive bias: overvaluing what you already have simply because you have it. In psychology it’s called the endowment effect. A note you haven’t opened in two years has no practical value — but because it’s yours, your brain assigns it a disproportionate emotional value. Recognising this bias doesn’t eliminate it, but it lets you decide more clearly.

Before Migrating, Filter

The most common mistake in a migration is trying to move everything. Every note, every file, every record — all from the old tool to the new. The result is that you replicate the mess from the old system in the new one, and instead of starting clean, you start with inherited rubbish.

Before migrating, filter. And the filter is simple: have I needed this in the last six months?

  • Yes → It migrates.
  • No, but it’s an important reference document (contract, legal document, certificate) → It migrates to cold storage.
  • No → It doesn’t migrate. It stays where it is during a grace period and is then deleted.

Cold storage is a useful concept: a folder or space where you keep what you probably don’t need but aren’t ready to delete. It has one rule: if in six months you haven’t opened anything in there, you delete the entire thing without reviewing it. Most people never open it again.

The filter doesn’t just reduce the volume of migration — it improves the quality of your new system. You start with only what’s relevant, current and actually used. That’s infinitely better than starting with ten years of files you’ll never touch.

The Migration Process

Once you know what to migrate, the process has four phases:

Phase 1: Export. Get your data out of the old tool in the most standard format possible. Markdown, CSV, PDF, plain text files. Avoid proprietary formats that only the original tool can open. If the tool doesn’t offer clean export, manually copy the essentials — it’s tedious but necessary.

Phase 2: Organise before importing. Don’t dump everything as-is into the new tool. Use the transition as an opportunity to reorganise. Create the structure you want in the destination — folders, tags, categories — then place each piece in its spot. Migration is the perfect chance to start with a clean organisation.

Phase 3: Import. Bring the filtered, organised data into the new tool. Do it in a dedicated session, not bit by bit. Gradual migration — “I’ll move things little by little” — rarely completes. Block a couple of hours, put on some music and do it in one go.

Phase 4: Verify. After importing, check that everything has arrived correctly. Verify that formats have been preserved, that links work, that the structure makes sense. Fix what needs fixing now, not when you discover it by surprise three months later.

Estimated time: for a personal notes migration, between two and four hours. For a more complex system with multiple tools, a weekend. It’s a significant time investment, but one you only make once.

After Migrating

The migration doesn’t end when the data is in the new tool. It ends when the old tool stops existing in your digital life.

Grace period. Keep the old tool installed but inactive for 30 days. If during that month you need something you didn’t migrate, retrieve it and move it. If you don’t need anything — which is most likely — you know the migration was complete.

Uninstall. After the grace period, uninstall the old tool. Don’t leave it “just in case” — that’s exactly the habit you’re trying to break. If the tool is a web service, cancel the subscription and, if you like, export a final backup before closing the account.

Update your stack document. Record the migration: what tool you eliminated, what tool now absorbs it, the date. This record serves as your system’s history and as a reference when you wonder “where did I have that?”

Resist the urge to go back. The first days after a migration are uncomfortable. Things you found quickly before now take a bit longer. Flows that were automatic now require thought. That’s normal — it’s the adaptation curve. Don’t interpret it as a sign that the decision was bad. Give it time. In two weeks, the new system will feel natural.

Migrating is letting go. Letting go of tools, letting go of information you don’t need, letting go of the illusion that you need everything you have. It’s uncomfortable, it takes time and it generates temporary anxiety. But on the other side is a cleaner, faster, more reliable system — a system that works with you instead of against you.