Notice periods for a SaaS shutdown range from about two years to about four days.
Atlassian told Opsgenie customers in March 2025 about an April 2027 end of life. Productiv announced the retirement of its platform on 6 August 2026 and shut it down four days later. Same category of event, two orders of magnitude apart in warning.
You do not get to choose which kind you get. What follows assumes the bad one, and scales down cleanly if you were lucky.
Week one: get the data out
Before evaluating replacements, before the vendor call, before telling anyone. Export first, because it is the only step with a hard deadline you do not control.
Two dates matter and they are not the same date. Access ends when the product stops working. Deletion happens later, sometimes much later, sometimes days later, and the second one is the one that ends your options. Find both in writing.
Then check what you actually got, because a completed export is not a complete export. The gaps are consistent across products:
- Attachments and documents. A row-per-record CSV rarely brings the files with it, and files are the part you cannot reconstruct.
- History. Current state exports give you today. What something cost, or who owned it, three years ago frequently does not survive.
- Archived and deleted records. Exports tend to default to active. Your retention obligations do not.
- Anything computed. Balances, scores and rollups are calculations. Without the inputs and the rules, the number is a screenshot.
Open the files. Do not assume a download that finished is a download that worked.
Week one, in parallel: work out what actually depends on it
Usually more than the team that owns it thinks, and the dependencies are rarely documented.
Look for scheduled reports going to people outside the team, integrations pushing data into other systems, single sign-on relationships, anything with a webhook, and any process where this tool is the system of record rather than a convenience. That last category is what turns a tool migration into a compliance problem.
Week two: replacements, with your eyes open
Now you can evaluate, and you will be reading a lot of content written by people who want to sell you the answer.
Search any shutdown and the results are dominated by competitors publishing migration guides. Some are genuinely excellent on export mechanics, because they have done the migration dozens of times and know where the data hides. All of them arrive at a shortlist they are on.
Read them for the mechanics. Build your own shortlist. The two activities are separate and the pages are designed to blur them.
Give real weight to how long migration takes rather than to feature comparison. Teams moving off Opsgenie with straightforward setups still report six to eight weeks, and more with heavy integrations. Feature parity is a spreadsheet exercise. Elapsed time is what determines whether you make the deadline.
The recovery nobody thinks of
If the data is already gone, or the export came back thin, stop looking at the dead vendor and look downstream.
Most of what you lost exists somewhere else, because systems that integrated with the dead one kept copies. Your data warehouse, your accounting system, the SFTP destination somebody set up years ago, the reporting tool that pulled a nightly extract, the other SaaS product that syncs contacts. Reconstruction from downstream systems is usually more complete than people expect, and nobody tries it because the instinct is to grieve the primary source.
Then fix the thing that let it hurt
Once the fire is out, two contract terms are worth adding everywhere. A minimum notice period on discontinuation, and a defined post-termination data retention window with an export format specified. “You can export your data” and “you can export your data in a form another system can read” are different promises.
Worth checking whether your existing agreements have either. Most do not, which is how a four-day notice becomes legal.
The worked example is what happened to Lattice HRIS customers, where the product died on schedule and the data deletion terms turned out to be worse than the standard policy everyone assumed applied. CopperFeed records shutdowns and retirements as they are announced, which is the only version of this that gives you time.
General guidance, not legal advice. Retention obligations and contract terms vary, and your own agreement governs.