The Day Your App Gets Bought Is the Day You Should Start Packing

The email lands at 9:14 on a Tuesday. The subject line reads something like: Exciting news — your favorite app is joining forces with a bigger company. There is a stock photo of a handshake. There is a phrase about the road ahead. There is absolutely no mention of what happens to the fourteen gigs of your life currently sitting on their servers.

Here is my unpopular position, stated plainly: an acquisition announcement is not good news for you. It is a deadline with the date filed off. Treat it accordingly.

The email is a warning shot, not a press release

Nobody buys a company to leave it alone. They buy the team, the users, the technology, or the revenue — and every one of those paths leads through change. Sometimes it works out. More often you get a redesign nobody asked for, a pricing page that quietly grew a tier, a privacy policy updated with language about affiliates and partners, and eighteen months later a support article explaining that the service will sunset on a date you'll read about in the past tense.

I've watched this cycle play out across note apps, password managers, budgeting tools, and one very beloved podcast app. The pattern is so consistent that the announcement itself is now the signal. When it arrives, you have a window. The window is not permanent.

Five red flags worth watching in the first month

• The privacy policy changes before the product does. Watch for wording about sharing data with parent companies, affiliates, or business partners. That clause is usually the whole point of the acquisition.
• The roadmap goes quiet. A public changelog that stops updating in week two is telling you something the blog post won't.
• Support slows to a crawl. Time your next help request. Two days becomes nine, and then the help center itself starts pointing to a generic form.
• The pricing page gets a redesign. New tiers, new annual-only options, and a discount for upgrading now. That discount is a bet against your own future.
• Key people leave. Founders posting farewell notes on social media, engineers updating their profiles, designers announcing they're taking some time off. The people who built the thing you rely on are the first to know what's coming.

None of these is a death sentence alone. Three together is a fire drill.

The 72-hour drill

If an app you depend on gets acquired, do this in the first three days, before anyone has changed anything:

1. Export everything. Not the pretty PDF summary. Hunt for the raw format — CSV, JSON, Markdown, ZIP of originals. If the export is buried in a settings submenu, screenshot the path so you can find it again.
2. Download your attachments separately. Many exports reference files without including them. Open the archive and check that your images, audio, and PDFs actually came along.
3. Screenshot anything that isn't exportable. Shared lists, custom views, chat threads, saved addresses, that one dashboard you check every morning. Screenshots are ugly and they are still data.
4. Switch to monthly billing if you were paying annually and the renewal is more than a month out. You are buying optionality, not loyalty.
5. Write down the version number of the app you're on and the date. When things break later, this is how you'll know exactly when it started.

What usually happens next, in order

Month one brings the reassurance post and maybe a small feature. Months two through four bring a redesign, often one that adds a navigation pattern borrowed from the parent company. Around month six the subscription pricing shifts and the free tier tightens. Somewhere in year two you get either an integration announcement — your app is now a feature inside something bigger — or a sunset notice with a suggested replacement and a window to export that closes sooner than you'd like.

A few acquisitions are genuinely fine. The company stays intact, the product gets funding, and nothing changes for years. But you cannot know which kind you're in on day one, and the cost of preparing is low.

The part most people forget

The data inside the app is obvious. The data around it isn't. Check what's connected: calendar access, cloud storage sync, third-party integrations, shared accounts with family members, and API tokens you generated once and forgot. Those connections outlive your decision to leave. Unlink them deliberately, and rotate any keys you handed out.

If you have kids on a family plan, or a partner using the same grocery list, that's an extra export and an extra heads-up. It is much easier to move to a new app together on a Sunday than to discover mid-week that the household list vanished.

Prep, don't panic

I'm not telling you to flee every app the moment it gets acquired. I'm telling you to keep a running list of the four apps you'd genuinely miss if they disappeared tomorrow, and to test a replacement for each one before you need it. Fifteen minutes twice a year. Then, when the handshake email arrives, you're not starting from zero.

The best time to leave an app is when you still have the option to stay. The worst time is when the support article is already published and the export button is already gone.