Your favorite app is shutting down: get your data out before it's gone
Pocket and Omnivore both closed and took years of saves with them. When your app announces a shutdown, here is how to export fast and rehome the data somewhere lasting.
Your favorite app is shutting down: get your data out before it's gone
When an app you rely on announces it is closing, the window to act is short and the stakes are your own saved years. The playbook is the same every time: find the export, pull everything out in a portable format now, and rehome it somewhere durable before the lights go off. Do the export first and decide where it lives second, because the deadline does not wait.
This is not hypothetical. Pocket, the read-later app Mozilla owned, shut down on July 8, 2025, and its data export window closed about four months later in November. Omnivore, a beloved open-source read-later tool, was shut down in late 2024 after its team was acquired, with users reporting roughly a month of notice before the service and its data were gone. Two well-loved apps, two short windows, a lot of people who learned the hard way that a save inside someone else's app is only as permanent as the company behind it.
The lesson is not to panic every time a tool wobbles. It is to know the steps cold, so that when the email arrives you export calmly and lose nothing.
The export-and-rehome playbook
Work it in order, because the early steps are the ones with a deadline. First, find the export. Most apps have a settings or account page with an export or download-your-data option, often producing HTML, JSON, or CSV. If you cannot find it, search the app's help docs for the word export. Do this the day you hear the news, not the week before the cutoff.
Second, pull everything, not just the highlights. Export the full archive in the most portable format offered. HTML and JSON open anywhere and import into most other tools. A proprietary format that only the dying app reads is worth far less, so prefer the open one if given a choice.
Third, verify the file actually contains your data before you trust it. Open the export, confirm it holds the items you care about, and keep a copy somewhere boring and safe, a folder in your main cloud drive, not inside another app that could also close.
Fourth, rehome it. Move the export into a destination you can actually use, ideally one where you can search what you imported rather than just store it. A pile of exported HTML you never reopen is the same problem in a new folder.
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <link href="https://fonts.googleapis.com/css2?family=Playfair+Display:wght@400;500&family=Inter:wght@400;500;600&display=swap" rel="stylesheet"> <style> :root{--accent:#0c1e3a;--coral:#F26849;--soft:#f7f5f0;--rule:#e2e2e2} *{box-sizing:border-box} body{font-family:Charter,Cambria,Georgia,"Times New Roman",serif;max-width:760px;margin:0 auto;padding:8px 24px 24px;color:#1a1a1a;line-height:1.65;background:#fff;font-size:17px} .failure-grid{display:grid;grid-template-columns:1fr;gap:14px;margin:22px 0 24px} @media(min-width:640px){.failure-grid{grid-template-columns:1fr 1fr}} .failure-card{background:var(--soft);border-left:4px solid var(--coral);padding:18px 18px 14px;border-radius:4px;position:relative} .failure-card .num{position:absolute;top:-10px;left:14px;background:var(--coral);color:#fff;width:28px;height:28px;border-radius:50%;display:flex;align-items:center;justify-content:center;font-weight:700;font-size:0.92em;font-family:ui-sans-serif,system-ui,sans-serif} .failure-card h4{margin:6px 0 6px;color:var(--accent);font-size:1em;font-family:Charter,Georgia,serif} .failure-card p{font-size:0.94em;margin:0;color:#2a2a2a} </style> </head> <body> <article> <div class="failure-grid"> <div class="failure-card"><span class="num">1</span><h4>Find the export today</h4><p>Open settings or account, look for export or download-your-data, and start the day you hear the news, not before the cutoff.</p></div> <div class="failure-card"><span class="num">2</span><h4>Pull the full archive</h4><p>Export everything in the most portable format offered. Prefer HTML or JSON over a format only the dying app reads.</p></div> <div class="failure-card"><span class="num">3</span><h4>Verify, then back it up</h4><p>Open the file, confirm it holds what you care about, and keep a copy in a safe place that will not also close.</p></div> <div class="failure-card"><span class="num">4</span><h4>Rehome it somewhere usable</h4><p>Move it into a destination you can search, not just store, so it does not become a pile you never reopen.</p></div> </div> </article> </body> </html>Pick a durable destination, not another fragile one
The quiet failure after a rescue is rehoming your data into the next app that might also close, and starting the countdown over. The fourth step is the one most people rush. A safer home has two traits: it does not lock your data behind a format only it can read, and it lets you actually find what you imported instead of storing it in silence.
This is where dEssence fits, an AI memory app built around what you saved. You bring saves in through the web app, a Chrome extension, or Telegram, and then you find them by describing them rather than hunting a folder of exported files. Ask in your own words. "The articles I saved about sleep." "That recipe from the app that shut down." No folders, no tags, no organizing. Memory you do not have to maintain.
The point of rehoming into something you can question is that the rescue finally pays off. A read-later app that dies leaves you a heap of HTML. A memory you can ask turns that same heap back into something you reach for: save it, forget it, ask for it later. The data does not just survive the shutdown, it becomes usable again.
That said, no app should be trusted as a single vault, including this one. Keep the raw export in your own cloud drive too, so your durable copy is yours regardless of which tool you use to read it.
Honest about where dEssence falls short
dEssence is in beta, which means it is free with no card but still rough in places, and a tool in beta is exactly the kind of thing a careful person should not make their only copy. There is no native iPhone or Android app yet, so on mobile you save through Telegram or the mobile web rather than a polished home-screen app. Its capture surfaces are web, Chrome, and Telegram, so a bulk export file is brought in deliberately, not swept in with one universal importer for every dead app's format. And the free tier caps how much you can keep, which a large rescued archive can press against.
So the honest advice is layered. Always keep the raw export of any app you rescue in your own cloud storage as the durable backup. Use a memory like dEssence as the place you actually search and ask, not as the sole guardian of the only copy. The apps that burned people, the ones that gave a month of notice and then deleted everything, are a reason to never trust one tool completely again, this one included.
Frequently Asked Questions
Q: How do I export my data before an app shuts down?
Go to the app's settings or account page and look for an export or download-your-data option, usually producing HTML, JSON, or CSV. Start the moment you hear about the closure, choose the most portable format, and verify the file holds your data before the window closes.
Q: What if I already missed the export deadline?
If the app is fully closed, the data may be gone, as happened to people who missed the Pocket and Omnivore windows. If you have an old export file saved from before, you can usually still import it into another tool. This is why exporting early and keeping the file matters.
Q: Where should I move my data so this does not happen again?
Somewhere that does not lock your data in a closed format and lets you search what you imported. Keep the raw export in your own cloud drive as the durable copy, and use a searchable memory on top of it so the saves stay usable, not just stored.
Q: Is dEssence free right now?
Yes. It is free during beta with no card. Paid plans exist on paper as Free, Pro, and Team, but the beta itself costs nothing to try.
Apps close. The ones that mattered to you will probably outlast their welcome and then leave with little warning. Know the export steps, keep your own copy, and rehome into something you can actually ask, so the next shutdown costs you a login, not your memory.