Every software company you sign up with will eventually stop existing in its current form. Most get acquired, some pivot, some simply run out of money, and a handful survive long enough to matter. This is not cynicism about any particular vendor; it is the ordinary lifespan of a small software business, and a working farm routinely outlives several of them. The only question worth asking is what happens to your records on the day it happens to whichever one holds yours.
This page is about settling that question before you sign up, not after — because after is exactly the moment you have the least power to do anything about it.
Read this knowing who wrote it. This page is about what happens to your records if a vendor disappears, and it is published by a vendor. Apply the test below to us with the same rigor you would apply to anyone else — the argument is meant to survive that.
“You own your data” is a promise, not a mechanism
Almost every software company's terms of service state, somewhere, that you own your data. It is a nearly universal clause and a nearly meaningless one on its own, because ownership on paper does not tell you whether you can actually extract your records in a format you can use. A right you cannot exercise is not a protection. The clause that matters is not the one about ownership; it is the one about export — whether it exists, how complete it is, and whether you can trigger it yourself, on demand, without the company's help.
Read a vendor's export policy the way you would read the fine print on a lease, because that is the closer analogy: a promise that you own the furniture does not help if the landlord controls the only door out of the building, and it especially does not help if that door only opens when the landlord decides to open it.
Lock-in is rarely a decision; it is an accumulation
Vendor lock-in does not usually happen because a company deliberately traps you. It happens gradually, as a season's worth of records piles up inside a system, and the cost of leaving grows quietly with every entry, until one day the thought of extracting and rebuilding your history elsewhere feels larger than the annoyance that made you consider leaving in the first place. By the time lock-in is obvious, it has already been accumulating for a year.
This is exactly why the right time to test export is at the beginning, during a trial, when the stakes of a bad answer are low — covered in detail in what to demand from a farm software export. Waiting until you actually want to leave is waiting until the test costs the most to fail.
A company failing and a company disappearing are different risks
It is worth separating two scenarios that get treated as one. A company can fail commercially — run out of money, get quietly discontinued — while its servers and your data remain accessible for a wind-down period, giving you time to export if you act. A company can also disappear more abruptly — an acquisition that shutters the product overnight, a founder who simply stops responding — leaving no wind-down window at all. You cannot predict which kind of ending any given vendor will have. You can only control whether you already hold your own copy before either one arrives, which is why an export taken after the bad news is announced is already too late for the second scenario — one more reason this question belongs early in how to choose farm software honestly, not as an afterthought once you are already dependent on a product.
Young companies are not the only risk, but they are the honest one to name
It would be convenient to say lock-in is only a risk with new, unproven vendors, and untrue. Established companies get acquired and sunset products too. But a young company failing outright is a genuinely more common outcome, and it is worth naming plainly rather than glossing over: a small team building software is taking a real risk with your records, whether or not either of you says so out loud. The honest response is not to avoid every small vendor — often the smaller company is the one building the feature you actually need — but to hold every vendor, young or old, to the same export standard, and to actually exercise it.
What to actually check before you sign anything
Three things, in order. First, does the export button exist today, in the plan you are actually paying for, or is it a “contact support” process gated behind a request. Second, is the file it produces a structured format — a CSV, most commonly — or a summary designed to be read once rather than reused. Third, does the company's own communications suggest they expect you to export regularly, or do they treat the request as unusual when you ask about it during a trial. That third signal is softer than the first two, but it is often the most honest one: a company that builds its product assuming you will eventually leave treats export as ordinary; one that has not thought about it treats the question as slightly suspicious.
None of this requires a lawyer or a contract review. It requires clicking the export button during your trial, before you have paid anything, and opening the file it produces on a machine with no connection to the vendor at all. That single act tells you more about lock-in risk than any clause in the terms of service, and it costs you nothing but a few minutes you were going to spend on the trial anyway.
The one habit that makes the question moot
None of the scenarios above matter if you already hold a current, readable export of your own records, kept somewhere the vendor cannot reach. That single habit — an export taken on a schedule, stored outside the software's own account — converts every version of “what if the company disappears” from a crisis into a Tuesday. Farm40 gives every account twelve one-click CSV exports for exactly this reason, and we would rather you take one monthly and keep it somewhere we cannot reach than trust our own survival. The limit, stated plainly: an export only protects you if you actually take it. A capability sitting unused in a menu offers no more protection than a company that never built it, and that part is a habit only you can keep.
The rest of the questions worth asking a vendor before you commit are collected in what to ask a farm software vendor, and this one — what happens if you disappear — belongs at the top of that list, not the bottom.