A Vendor Is Sunsetting the Software You Rely On: Decision Tree
Why this matters
One day an email arrives: the software running your shop is being retired, or the company was acquired and the product is going away. Your customer list, job history, invoices, and photos live inside it, and now there is a clock on all of it. Handled well, this is an orderly move to a new tool. Handled slowly, it is a scramble that ends with data you cannot get out and a deadline you cannot move. The difference is what you do in the first week.
First move: get your data out before anything else
Before you evaluate options, negotiate, or panic, secure the irreplaceable thing. Your leverage and your access only shrink from the day of the notice, so do this first.
- Export everything you can, now. Customers, jobs, invoices, estimates, and especially the photos and signed documents, in whatever format the tool offers. Do it even if the shutdown is months out.
- Confirm the export is complete and readable, not just that a file downloaded. Open it. A partial or corrupt export discovered in month one is fixable; discovered at the deadline it is a loss.
- Ask the vendor in writing what data you can get, in what format, with what help, and how long they keep it after shutdown. The written answer sets the timeline you plan against.
Only once you hold a real, verified copy of your data do you move on to deciding where it goes. Everything after this is easier with your data already in hand and much harder without it.
Start here: read the notice for three facts
The sunset notice, or a call to the vendor, has to give you three things. They drive every branch below.
- The runway: the hard date the software stops working or stops being supported. That is your countdown.
- The path: is there a successor product or an offered migration, or nothing.
- The data terms: how you get your data out, and how long they hold it after the end.
If there is a successor product or migration
A vendor sunsetting one product often points you to a replacement, sometimes with automatic migration.
- Do not assume the successor is right just because it is offered. Evaluate it as a fresh purchase against your real workflow, the same as any new tool.
- If it fits and the migration is clean, this is your lowest-effort path. Verify the migration actually carried everything, especially photos and history, before you trust it.
- If it is worse or priced higher for what you need, treat the offer as one option among several, not the default. A forced move is a fair time to shop.
If the successor is a downgrade, or there is none
Now it is a forced switch, and the work is a normal migration on a deadline.
- Shortlist two or three alternatives and trial them on real work, fast, because the clock is running.
- Choose on data fit and daily feel, not the feature grid, and confirm each candidate can ingest the data you exported.
- Run the migration deliberately: map your data, pilot a small batch, verify it, then move the rest.
If the vendor is folding with no path
The hardest case: the company is shutting down and support is evaporating.
- Treat the export as an emergency, done today, because a dead vendor cannot help you later and the data may simply vanish at the end.
- Get everything into a neutral format you control (common spreadsheet files, downloaded image files) even before you have picked the destination, so a slipped shutdown date cannot strand you.
- Then migrate to your chosen tool on your own timeline, from the copy you hold, not from the dying system.
The options compared
| Response | Effort | Data-fidelity risk | Best when |
|---|---|---|---|
| Accept the successor | Lowest | Depends on their migration; verify it | It fits your workflow and the migration is clean |
| Migrate to a competitor | Higher | You control it; you also carry it | The successor is weak, pricey, or absent |
| Ride it out to the deadline | Deferred, then rushed | Highest; you gamble on late access | Almost never, only with a long runway and a firm plan |
Riding it out is rarely the answer. A deadline you do not control plus data you have not exported is the exact setup that ends in loss.
The recap
- Export and verify your data first, the day the notice lands.
- Read the notice for the runway, the path, and the data terms.
- Successor offered: evaluate it as a new purchase; accept only if it truly fits.
- Successor weak or absent: shortlist alternatives and run a deliberate migration.
- Vendor folding: emergency export to formats you control, then migrate on your timeline.
The judgment to bank: the sunset notice is a countdown, and your data's exit is the first task, not the last.
References
- U.S. Small Business Administration (SBA), business continuity planning for small business
- Trade-standard practice for software migration and data portability
- See related: Data Portability When Switching Field Service Management Software; Choosing Field Service Software: What Matters; The Data Backup Habit That Saves a Shop From Disaster