What happens to your data when an app shuts down?
Cloud data lives as long as the company's servers. What app shutdowns and pivots actually look like, the warning signs, and the export-before-you-need-it habit.
When an app shuts down, your data’s fate was sealed years earlier — by architecture, not by the farewell email. Data on the vendor’s servers lives exactly as long as those servers; a file on your device outlives the developer. The personal-CRM category has already run this experiment, twice, with different endings.
Two precedents from the personal-CRM shelf
This isn’t hypothetical for this category. Two well-loved apps already demonstrated the two main failure modes.
Garden: the quiet abandonment. Garden (“Garden: Stay in Touch”) launched in April 2018, built by Zander Adell, and got the core idea beautifully right — tend relationships like plants, set a catch-up rhythm per person, jot a note after you talk. TechCrunch and HuffPost covered it; it was free. Then, by everything publicly verifiable, development simply stopped around 2020: no updates, no release notes, last traceable version 1.1.8 — while the App Store listing stayed live, quietly collecting new installs. The architecture made the silence dangerous: Garden required an account at sign-up, so notes lived at least partly on a server nobody has publicly confirmed is still looked after, and the app shipped no export function of any kind. Users’ contacts themselves were safe — Garden layered on top of the iOS address book — but every note typed into the app is in limbo. The full picture, including what current users should do, is in our Garden alternatives rundown.
UpHabit: the pivot. UpHabit was arguably the best mobile networking-reminder app in the category — and then it pivoted from a consumer personal CRM into a relationship-selling tool for Salesforce teams, with personal users advised to migrate their data out. The contrast with Garden is the lesson: UpHabit’s CSV export (Settings → Account → Export) works and carries contacts, notes, last-touched dates, and tier labels, so leaving is an errand rather than a loss. The destination options are in our UpHabit alternatives guide. The same pattern played out a tier up: FullContact sold its consumer app Contacts+ to Benchmark Email in January 2021 and pivoted to enterprise identity resolution — the consumer product survived under a new owner, the company that built it moved on.
Same category, three endings: silence, pivot, sale. None of them announced themselves years in advance. All of them were survivable for users whose data had an exit.
Reading the warning signs
Apps telegraph their decline in a fairly consistent order. None of these signs alone is a verdict — together, they’re a countdown.
Release notes go quiet. A year without updates on a platform that changes annually means the app is aging toward incompatibility even if nothing else goes wrong. Garden’s version number froze at 1.1.8 while iOS kept moving.
The business model is missing. Garden was entirely free — which is part of the explanation, not a counterpoint: no revenue, no development. Someone pays for servers; when no customer does, the funder’s patience is the product’s lifespan.
Support stops answering. Often the earliest testable sign. An unanswered support email about a paid feature is worth more than any blog post.
The “exciting news” post. Acquisitions and enterprise pivots arrive wrapped in enthusiasm. The sentence to look for is whom the product serves next quarter — UpHabit’s pivot was precisely such a move, and consumer users were the ones advised to leave.
The formal sunset email, when it comes at all, is the final sign — and it puts you on the vendor’s timeline, exporting alongside everyone else before a hard deadline. The point of reading the earlier signs is to act on your own schedule instead.
Export before you need it
The entire defense is one habit, practiced while everything is fine.
-
Find the export today
For every app holding data you’d mind losing, locate the export function now and run it once. Standard formats only — vCard for contacts, CSV or JSON for records, Markdown or text for notes. An app with no export just told you something important about itself.
-
Put it on a quarterly schedule
A recurring reminder, four times a year, five minutes each. The same session feeds your contact backup ritual — date-stamped files, copies in more than one place.
-
Open the file once
A export you’ve never opened is a guess. Check that the vCard imports somewhere neutral, the CSV has all its rows, the notes are readable text — the vCard format guide covers what healthy files look like.
-
Re-run the warning-sign scan yearly
Once a year, ask of each app: updates in the last twelve months? Support responsive? Business model still visible? Three quick questions, and you’ll never be the user who learns about a pivot from a shutdown notice.
What a source-release pledge actually promises
Some vendors — Endearist among them — make a written promise: if the company ever shuts down or is acquired, the application’s source code is released, data stays exportable, and build instructions go public. It’s worth being precise about what that buys you.
What it guarantees: the app can outlive its maker. The community can rebuild it, patch it for new OS versions, and your data files remain readable by software that can always be resurrected. The worst case stops being “everything dies with the company.”
What it doesn’t guarantee: a roadmap, new features, or anyone running cloud infrastructure on the company’s behalf. A pledge is a floor, not a future.
That’s why the pledge matters most in combination with local-first architecture: when the primary copy of your data is a file on your device, the pledge only needs to keep an app buildable — not keep servers alive. Cloud-only apps making the same promise are pledging the harder half. For the architecture comparison in depth, see self-hosted vs local-first.
The pattern to carry away from Garden and UpHabit isn’t cynicism about small apps — it’s that survivability is a property you can check in ten minutes, before the first note goes in. Where does the data live, is there an export, who pays, what’s the exit promise. Choose tools where the answers are boring, and shutdown announcements become errands instead of losses.
FAQ
What actually happens to my data when an app is discontinued?
It depends entirely on where the data lives. **Cloud-only data** exists as long as the vendor's servers do — after the sunset date, the account page becomes an error page. **Local files** stay on your device regardless of what happens to the company; the risk shifts to the app itself eventually failing to launch on a newer OS. The architecture question is settled the day you choose the app, not the day it dies.
How much warning do companies give before shutting down?
When they shut down *formally*, typically **30 to 90 days** with an export window. The harder case is the informal death: no announcement, just years of silence while the app stays downloadable. **Garden** showed no public developer activity after roughly 2020, yet its App Store listing remained live — nobody who installed it in 2023 got a warning of any kind.
Was Garden ever officially shut down?
No — and that's what makes it instructive. By everything publicly verifiable, **Garden** simply went quiet around **2020**: no updates, no release notes, last traceable version 1.1.8, while the listing stayed up. The app required an account at sign-up, so notes lived at least partly server-side, and it offered **no export function of any kind**. An app can be effectively dead for years without anyone declaring it.
What does a pivot mean for existing users?
A pivot means the company survives but **stops building for you**. UpHabit moved from a consumer personal CRM to a relationship-selling tool for Salesforce teams, and personal users were advised to migrate their data out. FullContact sold its consumer app Contacts+ to Benchmark Email in January 2021 and turned to enterprise identity resolution. The product keeps running — pointed at someone else.
What are the warning signs an app is dying?
In rough order of appearance: **release notes go quiet** for a year or more; support stops answering; the product is **free with no visible revenue** (someone is paying for those servers, and eventually stops); the company announces an acquisition or an enterprise pivot framed as exciting news. The official sunset email is the *last* sign, not the first — by then you're acting on their timeline.
Does uninstalling an app delete my data?
On mobile, usually yes for local data: iOS and Android **remove an app's private storage when you uninstall it**. If an unmaintained app holds notes you care about, the order of operations matters — export or copy everything out *first*, uninstall second. For cloud-backed apps the data survives an uninstall but depends on the server still existing when you return.
What is a source-release pledge?
A written commitment that if the company shuts down or is acquired, the **application source code is released**, so the community can keep the app buildable and your data readable. It converts the worst case from "the app dies with the company" to "the app loses its maker but stays alive." Endearist makes this pledge in its manifesto — paired with local files, it covers both halves of the survival question.
What should I check before trusting an app with years of notes?
Four things. **Where does data live** — on your device or only their servers? **Is there an export**, in a standard format (vCard, CSV, JSON, Markdown), and have you actually run it once? **What's the business model** — who pays, and is that sustainable? **What's the exit promise** — data-out guarantees or a source-release pledge? Ten minutes of checking before adopting beats a rescue operation after.
Which export formats should I insist on?
**Standard ones**: vCard for contacts, CSV or JSON for structured records, Markdown or plain text for notes. A proprietary backup blob that only the same app can read is not an export — it's a tether. The test: can you open the file in software that has nothing to do with the vendor? If yes, your data survives the vendor.
What if the app has no export function at all?
Then the rescue is manual, and sooner is cheaper than later. Garden users faced exactly this: no export, so the route was opening the app **while it still launches** and copying notes out by hand — for most people an hour covers the relationships that genuinely matter. If an app you rely on has no export today, that hour is best spent this week, not after the app stops opening.
Are my contacts themselves at risk when a contacts app dies?
Usually less than you'd fear. Apps that **layer on top of the system address book** — as Garden did with iOS Contacts — leave the underlying contacts safe in your iCloud or Google account. What dies with the app is everything you typed *into* it: notes, reminders, schedules, tags. That layer is exactly what the quarterly export habit exists to protect.