Software Shutting Down? There Is No 30-Day Window

The short answer

What happens to your data depends on how the company dies, not on what your contract says, because for most small-contractor platforms the contract says nothing about it at all.

Search this question and you will find a dozen articles assuring you that "most contracts grant data-return rights" and that "a 30-day export window is common." So we read the actual terms of the two platforms most small service businesses in North America run on. On 5 September 2026, neither Jobber's Terms of Service nor Housecall Pro's Terms contained the word insolvency, the word bankruptcy, or the phrase wind-down. Neither promised a data-return obligation. In Housecall Pro's terms, the word "export" does not appear once, and the only 30-day window in the entire document governs the transfer of a domain name after you cancel a Pro Website.

What Jobber's terms do say is this: "You are responsible for ensuring that you maintain backups of your data at all times." And, in the same section: "Jobber has no responsibility or liability for the deletion, access restrictions, or failure to store any data."

That is not a knock on either company. Both are well-run, both ship real export tools, and this language is standard across the industry. That is exactly the point: the protection you assume is contractual is actually a product feature, and product features belong to a company that may not exist next year.

The four ways your software dies, and what each one costs you

Software companies do not fail in one way, and the way yours fails sets your timeline more than any other factor. Here are the four modes, with real dated cases.

Mode one: the orderly sunset

This is the good outcome, and it still costs you a season. Buildertrend acquired CoConstruct in 2021, development tapered off, and the platform moved into maintenance mode. Third-party migration guides published this year, including JobTread's and Billdr's, cite Buildertrend migration notices setting hard dates: no new projects in CoConstruct after 31 March 2027, and formal migration beginning by 30 June 2027.

Here is the detail that matters more than the dates. We fetched CoConstruct's own migration page on 5 September 2026 and it publishes no deadline at all. It sorts customers into "focused," "moderate" and "all-inclusive" feature users and asks them to book a consultation. The hard dates circulating in the trade press are not on the vendor's public page.

If the friendliest, most orderly, best-publicized sunset in residential construction software does not put its deadline on its own migration page, you cannot build your plan around a date you expect to be told.

Mode two: the acquisition absorb

Nothing shuts down. That is what makes this one dangerous. Your login works, invoices keep processing, and the product quietly stops improving. A builder in r/Contractor described exactly this position in a thread about leaving CoConstruct: "my whole business lives in coconstruct. estimates, selections, invoicing, all of it. now that buildertrend owns it and put it in maintenance mode, i know i have to move." Another commenter in that thread noted a practical cost nobody budgets for, that the acquirer's pricing is not the acquired platform's pricing, and warned to lock a flat rate before agreeing to migrate.

The absorb is the mode where you have the most time and use the least of it, because nothing is visibly broken.

Mode three: the quiet decay

The most common outcome in this market, and the one no checklist prepares you for. There is no filing and no announcement, because the vendor is a five-person shop or one talented developer with an LLC. Invoices stop arriving, support emails start bouncing, and you discover the failure retroactively on the day you need a change. Snowman Labs' guide for owners of orphaned systems calls this the version with no date, where the failure "is already quietly two years old" by the time you notice.

Mode four: the lights go out

On Friday 27 December 2024, Bench Accounting went offline. Not a sunset notice, not a migration plan. Offline. TechCrunch's report that day was headlined that the shutdown left thousands of businesses without access to accounting and tax documents. Bench was acquired by Employer.com on 30 December, and export access came back with the acquisition rather than with the closure.

A Bench customer of four years wrote up the experience days later, and one line should be pinned above every contractor's desk. At signup, she raised the walled-garden risk directly, and: "they promised me that, even though their app was a walled garden, I would always have access to my data and could export it at any time. With that potential dealbreaker addressed, I signed up."

The promise was made. The promise was believed. On the day, it was worth nothing, because it lived in a sales conversation instead of a contract, and because the company that made it no longer had anyone to keep it.

If it becomes a bankruptcy, your data becomes somebody else's asset

This is the part that separates an inconvenience from a genuine loss, and almost nothing written for contractors covers it.

When a US vendor files, Section 362(a) of the Bankruptcy Code imposes an automatic stay that prohibits all adverse actions against the debtor. As Thompson Coburn's analysis of cloud provider bankruptcy sets out, the question then becomes whether your data is "property of the estate" under Section 541. If it is, you cannot simply take it back. You need relief from the automatic stay, which means a bankruptcy lawyer and a motion, not a support ticket.

Do not assume your data is too obviously yours for this to be contested. In the Caesars Entertainment Chapter 11, creditors argued that the customer loyalty program data was the estate's most important asset, with a valuation of roughly one billion dollars. Customer databases are not treated as filing cabinets in bankruptcy. They are treated as the good stuff.

Three more mechanics worth knowing before you need them:

• The bailment argument is your best one. Thompson Coburn's recommended position is that the vendor holds your data as a bailee for hire, purely for storage, with no ownership stake, so it never becomes property of the estate. That argument is far stronger when your contract already says it. It is a clause you negotiate at signing, when you have leverage, not at filing, when you have none.
• A Section 363 asset sale can hand your contract to a stranger. The contract may be assumed and assigned to the purchaser under Section 365. Your data can end up under new ownership with different terms and a different privacy policy.
• Section 332 exists because this got bad enough to legislate. Added to the Code in 2005, it lets the court appoint a consumer privacy ombudsman to weigh privacy losses when personally identifiable information is part of a proposed sale. That is your customers' names, addresses and payment history, sitting on a schedule of assets.

One protection that gets recommended constantly does not really apply to you. Section 365(n) lets a licensee keep using licensed software even if the trustee rejects the contract, which is genuinely powerful for perpetual on-premise licences. It does nothing for a cloud subscription, because when the servers go dark there is no software left to license. Housecall Pro's terms make the same point from the vendor side: the service is "provided under license to User, not being sold to User," and you "do not gain any ownership interest of any kind."

The obligation that does not shut down with the vendor

Here is the asymmetry that makes this a real risk rather than an annoyance: your vendor's duties end when it dissolves, and yours do not.

The Canada Revenue Agency generally requires you to keep business records for six years after the end of the tax year they relate to. If you build homes in Ontario, Tarion's statutory warranty on major structural defects "begins on the date that the purchaser takes possession of the home and ends on the seventh anniversary." Seven years. Name a field service platform you are confident will still exist, under the same ownership, with the same export tooling, in 2033.

When a homeowner comes back in year five claiming a change order was never approved, "our software company shut down" is not a defence. It is an admission that you cannot produce the document.

Which reframes the whole question. You are not protecting a database. You are protecting your position in disputes that have not happened yet. For a contractor, four documents per job cover almost all of it:

1. The signed contract
2. The approved selections sheet
3. Every change order, with the approval
4. The final invoice and payment record

An experienced operator in that same r/Contractor thread reached the identical conclusion from the other direction: "You rarely need the live thread again, you need the contract, the approved selections sheet, the change orders, and the final invoice. Those four documents per job cover warranty and disputes, which is the only real reason to keep any of it."

Why "we own our data" is not the same as "we can get our data"

Owners tend to relax when they find an ownership clause. It is the wrong thing to look for.

Ownership is a legal claim. Possession is a working copy on a drive you control. In every scenario above, possession is what saves you and ownership is what you argue about afterwards with a lawyer you are paying by the hour. Look at what a real export gap does to that claim. In the r/Contractor migration thread, the recurring complaint was not the price or the interface. It was that there was no bulk export for documents: "no bulk export, files trapped in the platform, downloading stuff one at a time until you give up. i shouldn't have to fight my own software to get my own job history back."

You may fully own 9,000 job photos and signed PDFs. If retrieving them means 9,000 individual clicks, and the account is winding down while rate limits tighten, you own something you cannot carry. The mechanics of getting each layer out are their own project, which we cover in how to export your data from your current CRM.

The warning signs run about a year ahead

The Bench customer saw it coming and got out a month before the lights went off. She was not clairvoyant. She was watching operational tells that anyone could see:

• The humans got replaced by canned responses. Her named bookkeeper left and the replies turned into templated status text.
• The product got worse while the marketing got louder. Super Bowl-scale advertising alongside a degrading customer experience is a specific and reliable signal.
• Billing started making mistakes. She was overcharged for four straight months and refunded roughly two thousand dollars.
• Delivery slipped and never recovered. In April she was still waiting on January's books.

Translate that to your own vendor: are releases still shipping, or has the changelog gone quiet? Does support answer with a person or a macro? Have the account managers you knew all left? Did pricing change in a way that smells like a company reaching for revenue rather than growing into it? A vendor's decline is usually visible a year out, and none of the signals require inside information. If several are flashing, run our checklist on signs you have outgrown your CRM.

The 90 minutes a quarter that makes all of this a non-event

Everything above collapses into one habit. If you hold a current copy of your own records, a vendor shutdown stops being an existential event and becomes an administrative one. Four times a year, block 90 minutes:

1. Pull the rows. Export clients, jobs, estimates, invoices, payments and your price book to CSV. This is the fast part and it works on every platform worth naming.
2. Pull the files. Job photos, signed contracts, permits, attachments. If there is no bulk export, have someone technical script a logged-in browser session against the file list, or pay an assistant to work a checklist. Never click through it yourself.
3. Print the screens. Selections, change order approval threads, client message history. These are not files and no download will catch them. PDF them, named by job and date.
4. Build a manifest. One row per file: job name, date, original filename, where it landed. A folder with 9,000 unsearchable files is not an archive.
5. Count before you trust it. The platform tells you how many documents each job has. Reconcile that against your manifest. A pull that silently misses 300 files is worse than no pull, because you find out in year three of a dispute.
6. Open the files. Once a year, actually open a random sample. Untested backups fail exactly when tested for the first time.

Store the result somewhere you control and pay for directly, under your own company account, not the vendor's and not an employee's personal login.

What to ask before you sign the next one

The one moment you have leverage is before you sign. Four questions, all answerable by a non-technical owner:

• "Show me a full export of a demo account." Not a description of one. The file. Confirm records come out as CSV and files come out in bulk. If the answer is vague or routed to a support ticket, you are buying the same trap with a nicer interface.
• "What does the contract say happens if you cease operations?" If the terms do not contain the words insolvency or wind-down, the answer is nothing, and you now know that going in.
• "Will you commit to a data-return obligation and a notice period in writing?" A machine-readable export, available for a defined number of days after termination for any reason. Ask for it as an addendum.
• "Who owns the data, in the contract, in those words?" Push for language that the vendor holds your data purely as a bailee for storage, with no ownership interest, and that delivery to them transfers nothing. That single sentence is the argument that keeps your records out of an estate.

None of these are exotic. They are standard terms in enterprise master services agreements. The only reason small contractors do not have them is that nobody asks.

The bottom line

The honest answer to "what happens to my data if my software shuts down" is that it is entirely out of your hands, and it is out of your hands by contract, not by accident. Your platform's terms almost certainly do not promise you an export window, do not mention insolvency, and explicitly tell you that backups are your responsibility. The 30-day grace period you have heard about is an industry custom that evaporates precisely when the vendor is under the financial pressure that would make you need it.

That is not a reason to panic about your current vendor. It is a reason to stop treating their servers as your filing cabinet. Four documents per job, pulled quarterly, held on storage you control, turn every scenario above from a threat into a Tuesday. Bench customers who had a recent export lost a subscription. The ones who did not lost their books at tax time.

Your records will outlive your software. Make sure they outlive it somewhere you can reach.