Your software vendor vanished. Here's the rescue plan.

The software you’ve been running for five years suddenly has no support. The company that made it stopped answering emails. The login page still works, but the help docs are gone. The domain shows a parked page. You’re not sure if the company sold, shut down, or just stopped caring, but the result is the same: the software still runs, but nobody’s maintaining it.

This happens more often than it should. Small software companies fold. Bigger ones get acquired and kill the product. Sometimes the vendor just stops responding and the software keeps running on autopilot until something breaks. If your business depends on that system, you need a plan before it stops working.

Signs your vendor is gone

The first sign is usually silence. Support tickets go unanswered. Phone numbers disconnect. The company blog stops updating. Social media goes dark. If you’re paying a subscription and the charge keeps hitting your card, that’s not proof anyone’s actually maintaining the product. Billing systems can run on autopilot long after everyone’s gone.

The second sign is that the software stops getting updates. If you’re six months past the last release and the vendor used to ship updates monthly, something’s wrong. If security patches stop coming, that’s a bigger problem. Unmaintained software collects vulnerabilities. Eventually, something will break or get exploited.

The third sign is that other customers are asking the same questions you are. Check forums, LinkedIn, or wherever users talk. If everyone’s wondering where the vendor went, you’re not alone. That doesn’t fix your problem, but it tells you the situation is real and you need to act.

First: get your data out

Before the system dies completely, export everything. Most software has some kind of export function. If it’s a database-backed system, get a database dump. If it exports to CSV or JSON, download everything. If the only option is manually copying data, start copying.

You need your data in a format you control. As long as the data is locked in someone else’s system, you’re at their mercy. Once it’s out, you have options. Even if the export is messy or incomplete, it’s better than nothing. If the system crashes tomorrow and you can’t log back in, whatever you didn’t export is gone.

Check what you actually got. Open the export files and verify they’re complete. Make sure critical fields didn’t get dropped or corrupted. If you export customers and half the email addresses are blank, that’s a problem you need to catch now, while the system is still running and you can re-export or manually fill gaps.

Store the export somewhere safe. Don’t leave it on your desktop or in a downloads folder where it might get deleted. Back it up. If this is the only copy of your business data, treat it that way.

Retire it without breaking the workflow

Once you have the data, you can start planning the replacement. But don’t shut down the old system until the new one is fully running. Even a dead-end system that still works is better than nothing while you’re transitioning.

Run both systems in parallel if you can. Enter new data into the replacement, but keep the old system running in read-only mode so you can look up historical information. That gives you a safety net. If something’s missing or wrong in the new system, you can check the old one.

The replacement doesn’t have to be another piece of software. Sometimes the right move is to simplify. If the old system was overkill and you only used a fraction of its features, maybe a spreadsheet or a simpler tool does what you actually need. Don’t replace complexity with more complexity unless the complexity is actually necessary.

If the old system handled multiple things, you might split it. One tool for customer records, another for invoicing, a third for inventory. That’s more tools, but if each one is simpler and better maintained, it’s less risk overall. The key is that each piece is something you control or something backed by a vendor you trust to stick around.

Test the replacement with real work before you fully commit. Don’t just set it up and assume it works. Run a few jobs through it. Check that the data flows the way you need. Make sure the people who actually use it daily can do their jobs without the old system. If they’re still reaching for the old tool because the new one doesn’t quite work, you’re not done yet.

When you’re confident the replacement handles everything the old system did, then you can retire it. Not before. Shutting down too early means you’ll be scrambling to bring it back or working around gaps you didn’t know existed. Give it a month of parallel operation. If nothing breaks and nobody’s using the old system anymore, turn it off.

---

Small businesses typically run on dying software longer than they should because replacing it feels overwhelming and nobody has time to plan it. We’ll audit your current setup for free for one week and map exactly what the system does, where the data lives, and what replacing it actually requires. You’ll get a written rescue plan with specific next steps. Contact us at founder@fjorra.app.