Every year, apps get discontinued — sometimes with generous warning, sometimes with barely any. The users who sail through a shutdown are not lucky; they prepared before the announcement. Shutdown preparedness is not paranoia. It is the same logic as having a fire extinguisher: you hope you never need it, and you are profoundly glad it is there when you do.
This 2026 checklist walks you through a complete preparedness audit for every app you use: inventorying what matters, securing your exports, documenting your setup, and building exit plans for your most critical tools. Work through it once, then revisit it once a year. It takes an afternoon the first time and under an hour on repeat visits.
Step 1: inventory every app that holds your data
You cannot protect what you have not listed. Start by writing down every app and online service where you have an account — not just the ones you open daily. Include the note-taking app, the photo backup, the budgeting tool, the project manager, the password manager, the email service, the cloud drive, the fitness tracker, the recipe box. Most people are surprised by the count; thirty to fifty accounts is normal.
For each app, note three things: what data lives there, how painful losing it would be on a scale of one to five, and whether you know how to export it. The pain score is the key insight — it tells you where to spend your limited preparedness time. Your password manager and photo library deserve a full exit plan; the app where you once saved three recipes does not.
Do not forget the apps you access through someone else’s account — a family photo library, a shared work drive, a partner’s streaming login. You have even less control over those, which makes documenting them more important, not less. Our guide on Replacing a Password Manager Safely: Step-by-Step is a natural companion here, since it walks through the same inventory idea in more depth.
Step 2: map the export path for your critical apps
For every app you rated four or five on the pain scale, find the export option today — while nothing is wrong. Open the settings, look for Privacy, Data, Account, or Backup sections, and confirm that an export or download feature exists. Run it once as a test. Note the format of the download and where you saved it.
You will discover three categories. Category one: apps with a proper export tool that produces usable files — these are the good citizens. Category two: apps with a partial export — your files come out but your organization, tags, or history do not — which means you need supplementary documentation. Category three: apps with no export at all, where your only options are manual workarounds. Knowing which category each critical app falls into, before any shutdown, is the entire point of this exercise.
Write down what you find. A simple note — “Notes app: exports as plain text via Settings > Export, tested June” — is enough. Future you, reading a shutdown notice at 11pm, will be grateful for past you’s ten minutes of documentation. Understanding Why Apps Get Shut Down: The Business Reasons, Explained helps explain why some apps invest in export tooling and others never bother.
Step 3: set a backup cadence you will actually keep
A one-time export is a snapshot; preparedness needs a rhythm. For your highest-pain apps, schedule a recurring export — monthly for things that change fast like notes and finances, quarterly for slower-moving archives like photos. Put it in your calendar as a repeating event with the exact steps in the event description, so future you does not have to rediscover the process.
Store each export in two places: your computer and somewhere else — an external drive, a second cloud account, a trusted family member’s storage. One copy is not a backup; it is a hope. And keep at least the two most recent exports, not just the latest, so a corrupted download does not leave you with nothing.
Be honest about what you will maintain. A monthly export you actually do beats a weekly one you abandon by February. Start with quarterly for everything critical, and tighten the cadence only for the two or three apps whose data changes fastest. Systems survive on sustainability, not ambition.
Step 4: secure your credentials and recovery paths
A shutdown is the worst time to discover you cannot log in. Verify today that you can access every critical account: the password works, the two-factor method is one you still possess, and the recovery email is an inbox you still read. Update anything stale now, while support teams exist to help if something goes wrong.
This is also the moment to make sure your password manager itself is preparedness-proof. Export your vault to an encrypted file and store it somewhere safe — a password manager you cannot export from is a single point of failure wearing a security costume.
Do not forget shared access
If other people depend on your accounts — family photo libraries, shared project folders — document who has access and how they would get the data if you were unavailable. Preparedness is not only about companies shutting down; it is about your own continuity too.
Step 5: write mini exit plans for your top five apps
For your five highest-pain apps, write a short exit plan: where your data would go, which replacement you would try first, and the rough steps to migrate. This is not a research project — thirty minutes per app, tops. The goal is to convert a future panic into a checklist you already wrote while calm.
A good mini exit plan fits on an index card: “If NotesApp shuts down: export via Settings > Export (plain text, tested); try Alternative X first (imports plain text); budget one weekend for migration; cancel annual plan before renewal in March.” That is it. You will refine it when the day comes, but starting from a card beats starting from zero.
Step 6: audit the money side
Preparedness has a financial dimension. List every app subscription you pay for, what it costs, when it renews, and whether it is annual or monthly. Annual plans deserve special attention: if the app shuts down mid-year, refund policies vary, and you want to know your renewal dates before you need them. Our Subscription Audit Calculator on the homepage can help you see the full annual picture in about a minute.
Consider whether your highest-pain apps are on the right billing cycle. Monthly costs more per year but limits your exposure if a service disappears; annual saves money but ties up cash in a company that might not survive the year. There is no universally right answer — there is only the tradeoff, made deliberately instead of by default.
Step 7: make it a yearly habit
Preparedness decays. Apps change their export options, you adopt new tools, old ones fade from memory. Once a year — pick a memorable date — rerun the quick version: update the inventory, re-test the critical exports, refresh the exit plans, and check that recovery emails still work. An hour a year keeps the whole system honest.
The deeper payoff is psychological. Once you have done this audit, shutdown notices stop feeling like emergencies and start feeling like errands. You will still be annoyed — nobody enjoys migrating — but you will not be afraid. And in a software landscape where apps get discontinued every year, the absence of fear is worth an afternoon.
Step 8: test one restore per year
Backups you have never restored are aspirations, not safety nets. Once a year, pick one export and actually restore something from it — open the files on a different device, import a sample into a fresh account, confirm the data is intact and usable. This single habit catches the silent failures: corrupted archives, expired download links you forgot to refresh, formats your new computer can no longer open.
A restore test takes twenty minutes and answers the only question that matters: if the app disappeared tomorrow, could you actually get your life back from these files? If the answer is yes, your preparedness is real. If the answer is no, you have found the gap while there is still time to fix it — which is precisely the point of the exercise.
Frequently asked questions
How long does the full checklist take the first time?
Plan for an afternoon — roughly three to four hours for someone with thirty to fifty accounts. The inventory is the slow part; everything after it moves quickly. Subsequent yearly reviews take under an hour.
Which apps should I prepare first?
Start with the intersection of high pain and poor export options: the apps where losing data would hurt most and getting it out is hardest. Password managers, photo libraries, and financial tools usually top the list.
Should I bother with apps I barely use?
List them, rate them honestly — usually a one or two on the pain scale — and move on. The checklist is about focusing effort where it matters, and explicitly deprioritizing the rest is part of the method.
What about apps my employer provides?
Your employer’s IT team owns that preparedness, but your personal work product inside those apps is still worth exporting where policy allows. Keep personal and work data separated as a standing habit so a job change never becomes a data emergency.
Is 2026 different from previous years for shutdown risk?
The pattern is steady rather than spiking: apps get discontinued every year as funding shifts, strategies change, and products consolidate. What has changed is how much of daily life runs through apps, which raises the stakes of each shutdown. Preparedness matters more now because dependence is higher, not because shutdowns are more frequent.
Print this checklist, or save it somewhere you will find it. Then do the single most valuable step today: pick your highest-pain app and test its export. Ten minutes, one app, done. Preparedness compounds — and it starts with that first export.