The 30 cloud and software services that closed between 2023 and 2026 gave a median of 90.5 calendar days of documented public notice, per a 5WPR review of company announcements. The median was 127.5 days across the 14 shutdowns with directly dated provider records. Ten of 30 shutdowns published refund terms or a refund request process, and 24 gave export instructions. Fourteen gave under 90 days.
Last updated: November 21, 2026.
Summary: what did the 30 shutdowns have in common?
The 30 shutdowns in this study varied widely in notice, export dates and migration help. The table below counts what each company published, using the date of its earliest recoverable public notice.
| Finding | Count |
|---|---|
| Median original documented public notice, all 30 shutdowns | 90.5 days |
| Median notice using the latest announced dates | 91 days |
| Median notice, 14 directly dated provider records | 127.5 days |
| Under 30 days of original notice | 2 of 30 |
| 30 to 89 days | 12 of 30 |
| 90 to 179 days | 6 of 30 |
| At least 180 days | 10 of 30 |
| Shutdowns with refund terms or a refund request process | 10 of 30 |
| Export instructions | 24 of 30 |
| Export instructions and a dated cutoff | 15 of 30 |
| Migration guidance or a tool | 18 of 30 |
| Migration destination named only | 4 of 30 |
| No migration information recovered | 8 of 30 |
| A later update moved a customer deadline | 5 of 30 |
The 90.5-day median covers all 30 shutdowns. Across the 14 shutdowns with directly dated provider records, the median was 127.5 days, a difference of 37 days. The full sample also uses notice dates recovered from archived copies, linked or quoted contemporaneous reporting and, where the official publication day was indeterminate, the earliest recoverable company-attributed public date. Some of those intervals may be shorter than the true first public notice, so the two medians should be read together.
How much notice did customers get before software shut down?
The median interval between the earliest recoverable public notice and the originally announced end of normal use was 90.5 calendar days. The spread was large: Humane gave 10 days for its Ai Pin cloud service, while Dark Sky gave 640 days and later extended the date to 1,095 days.
The shortest notices came from consumer products. Humane announced its cloud wind-down on February 18, 2025 and scheduled cloud connectivity and data deletion for noon Pacific on February 28, according to its archived Ai Pin FAQ. Cohost gave 22 days, Sora web and app gave 33 days, and Revue gave 35 days.
The longest notices came from enterprise and developer products. Workplace from Meta gave 474 days, Halp gave 397, and Kaizala, Jamboard, Amazon Chime, Amazon WorkDocs, the OpenAI Assistants API and Twilio Frontline each gave 365 days or more.
These intervals measure the time between the earliest recoverable public notice and the announced end of normal use. Individual customers may have learned about the closure earlier or later.
Did companies publish refund terms?
Ten of 30 shutdowns published refund terms or a refund request process. The records reviewed showed no case-wide denial of refunds. In the other 20, the audit found no qualifying public refund information, including services where pricing or free status made a refund question less relevant. Some parent companies appear twice in the sample, so the unit is a shutdown, not a company.
Four examples show the range. Google announced automatic processing of eligible Stadia purchases, generally excluding Stadia Pro, in its Stadia FAQ. Glitch said it would refund unused Pro time in its wind-down announcement. Skiff gave customers a refund email procedure without an amount or deadline, and Sora pointed to the standard ChatGPT subscription refund process with no separate adjustment.
Could customers export their data before the cutoff?
Yes, in 24 of 30 cases, because those companies published export instructions. Fifteen of the 24 also gave a dated cutoff, and none of the 15 set that cutoff earlier than the announced end of normal use. Nine set it on the same date and six set it later.
| Export cutoff versus service end | Cases |
|---|---|
| Before the announced end | 0 of 15 |
| On the same date | 9 of 15 |
| After the announced end | 6 of 15 |
| Before the exact documented actual end (smaller subset) | 1 of 6 |
A same-day cutoff can still fall before midnight. Neptune set its export deadline for March 5, 2026 in its transition hub, and its retrospective service shutdown record reports that hosted termination occurred on March 6. Humane scheduled the cloud cutoff and customer-data deletion for the same noon Pacific hour.
Some export routes outlasted the product. Mozilla closed Pocket on July 8, 2025 and first listed October 8 as the last day to download saved items in its Pocket announcement. Its updated Mozilla support page later listed November 12. Microsoft advised Skype users to request their history before deletion began on April 1, 2026, but accepted export requests until June 15, 2026, 472 days after its first notice, and warned that later exports might be incomplete, per Microsoft support.
Coverage also varied. Amazon Chime documented CSV export for contacts and room membership, but the Chime transition guide did not establish a general chat-history export.
What migration help did companies offer?
Eighteen of 30 shutdowns offered a migration guide, training or tool, four named a destination without a concrete workflow, and eight had no migration information in the recovered record. A migration guide answers a different question than an export guide: export explains how to take data out, migration explains where it lands.
The most specific materials described both ends of the move. Workvivo published a Meta-built transfer workflow for Workplace and dated its free migration offer through October 31, 2024, per its Workplace migration documentation. Atlassian described moving Halp tickets into Jira Service Management. Neptune published version-specific exports and guides for loading experiment records into competing platforms.
Which shutdown deadlines moved?
Five of the 30 services moved a customer deadline after the first announcement. Read-only or export-only periods that were part of a company's original plan were coded as milestones, not extensions.
| Service | Deadline type | Original | Latest announced |
|---|---|---|---|
| Skype | Export | January 2026 | June 15, 2026 |
| Export | October 8, 2025 | November 12, 2025 | |
| Neptune hosted SaaS | Service termination | March 4, 2026 | March 5, 2026 |
| Dark Sky API | Service termination | December 31, 2021 | March 31, 2023 |
| Cohost | Final server retirement | End of 2024 | January 12, 2025 |
Two of the five moved the date of normal operation. Two moved an export window, and Cohost moved its final server retirement while leaving its earlier interactive cutoff in place.
What do the findings mean for PR and communications teams?
The findings point to four gaps that a communications team can close before a shutdown notice goes out: a refund statement, an export cutoff that falls after service end, a named migration path, and a single page that holds every date. These are 5WPR's reading of the public record, not causal claims, and the groups are small.
5WPR also cross-tabulated notice length against what each shutdown published. The 10 shutdowns with refund terms or a refund request process had a median notice of 61.5 days, against 142 days for the 20 without. Median notice was 37.5 days in the eight cases where no migration information was found and 163 days in the 18 cases with a guide or tool. The four cases that named a destination only had a median of 106.5 days.
| PR finding | Evidence in this study | Action for a communications team |
|---|---|---|
| Refund terms were the exception | 10 of 30 shutdowns published refund terms or a refund request process | State the refund rule, amount basis and claim route in the first announcement |
| Export deadlines mirrored service end | 9 of 15 dated cutoffs fell on the same date as service end | Set the export cutoff after service end and state the hour and time zone |
| Migration help varied with notice length | Median 37.5 days where no migration information was found, 163 where a guide or tool existed | Publish the migration guide on the day of the notice, not weeks later |
| Dates moved after launch | 5 of 30 changed a deadline | Keep one dated change log so customers can see what moved and why |
| Export is not migration | 24 of 30 gave export steps, 18 gave migration help | Publish both, and say what the export file contains and leaves out |
| Notice date is not receipt date | Public posts cannot show when a customer was told | Send direct messages the same day as the public post and archive a dated copy |
Teams that handle shutdowns, product exits and customer-facing incidents can apply the same checklist to their crisis communications planning and their corporate communications templates. A related 5WPR study, what companies tell customers after a cyber incident, examines the same customer-notice question for security events.
What did each of the 30 services publish?
The table lists each service, its original public notice in calendar days, and whether the recovered record showed refund terms, export instructions and migration help. "Published" and "Instructions" mean a qualifying public statement was found. "Not found" means none was recovered, not that none existed.
| Service | Original notice (days) | Refund terms | Export | Migration |
|---|---|---|---|---|
| Stadia | 111 | Published | Instructions | Guide or tool |
| Jamboard app | 369 | Not found | Instructions | Guide or tool |
| Skype | 66 | Published | Instructions | Guide or tool |
| Kaizala | 370 | Not found | Not found | Guide or tool |
| Workplace from Meta | 474 | Not found | Instructions | Guide or tool |
| Meta Spark | 140 | Not found | Instructions | Destination only |
| Amazon Chime | 366 | Not found | Instructions | Guide or tool |
| Amazon WorkDocs | 365 | Not found | Instructions | Guide or tool |
| 47 | Published | Instructions | Not found | |
| Fakespot | 40 | Not found | Not found | Not found |
| Glitch application hosting | 47 | Published | Instructions | Guide or tool |
| Deta Space | 45 | Not found | Instructions | Not found |
| Revue | 35 | Not found | Instructions | Not found |
| Mint (Canada endpoint) | 144 | Not found | Instructions | Guide or tool |
| Foursquare City Guide | 55 | Not found | Instructions | Guide or tool |
| Dropbox Passwords | 90 | Not found | Instructions | Guide or tool |
| Sora web and app | 33 | Published | Instructions | Not found |
| Assistants API | 365 | Not found | Instructions | Guide or tool |
| Humane Ai Pin cloud service | 10 | Published | Instructions | Not found |
| Skiff suite | 182 | Published | Instructions | Guide or tool |
| Stitcher listening app | 63 | Published | Instructions | Destination only |
| Halp standalone | 397 | Not found | Not found | Guide or tool |
| Twilio Frontline | 365 | Not found | Not found | Destination only |
| Mocha | 78 | Not found | Instructions | Guide or tool |
| Neptune hosted SaaS | 91 | Published | Instructions | Guide or tool |
| Relay.app | 60 | Published | Instructions | Guide or tool |
| Adobe Aero cloud experience | 118 | Not found | Instructions | Not found |
| Dark Sky API | 640 | Not found | Not found | Guide or tool |
| Cohost | 22 | Not found | Instructions | Not found |
| Drizly | 73 | Not found | Not found | Destination only |
Frequently asked questions
How much notice do customers get when software shuts down?
In 5WPR's study of 30 closures, the median was 90.5 calendar days of documented public notice. Fourteen of 30 gave under 90 days and 10 gave at least 180 days.
Do companies refund customers when a software service shuts down?
Ten of 30 shutdowns published refund terms or a refund request process. For the other 20, 5WPR found no qualifying public refund information.
Can customers still export data after a service shuts down?
Sometimes. Of the 15 cases with a dated export cutoff, 6 ran past the announced end of normal use, including Pocket and Skype. Nine ended on the same date as service end.
What is the difference between exporting and migrating?
Export is taking data out of a service in a file or request. Migration is moving that data into a replacement product, usually with a guide or transfer tool. Twenty-four of 30 shutdowns published export instructions and 18 published migration help.
Which shutdowns changed their deadlines?
Five of 30: Skype, Pocket, Neptune, Dark Sky and Cohost. Dark Sky moved its end date from December 31, 2021 to March 31, 2023.
Does this study cover every software shutdown?
No. It is a search-discovered sample of 30 cases capped at two per parent company, so it does not estimate an industry-wide rate.
Conclusion
Documented public notice varied from 10 to 640 days, and the gaps in the public record were smaller and fixable: a refund rule, an export cutoff after service end and a migration guide published on day one. Communications teams planning a product exit can use the table above as a checklist, and 5WPR's crisis communications team works with companies on shutdown notices, customer FAQs and direct outreach.
How did 5WPR run this study?
5WPR reviewed 30 search-discovered software and cloud service shutdowns completed between January 1, 2023 and October 31, 2026, with public evidence observed on November 21, 2026. The sample is a purposive, search-discovered set capped at two products per parent company at the time of notice, so it does not estimate an industry-wide rate.
How was notice counted?
Notice is the number of calendar days from the earliest retrievable dated public company notice to the announced loss of normal use, including a move to read-only. Where only a broad period was announced, the later exact date was used and flagged. Dates recovered from archived copies, quoted contemporaneous records or the earliest company-attributed public date are flagged as well. Original and revised dates are kept apart from actual dates and export cutoffs.
How were refund, export and migration coded?
Refund counts only explicit eligibility, an amount rule or a shutdown-linked claim route. Export counts a step, control, usable guide link or documented request method, including category-limited exports. Migration counts a guide, transfer tool, training or operational handoff. A vendor-to-vendor tool alone is not a stand-alone export, and information not found is kept separate from an explicit denial.
What are the limits of the data?
The data describe public documents only. Private communications, individual refund receipt, successful exports and customer satisfaction were outside the evidence reviewed. Search discovery favors visible products and surviving sources, coding was a single pass without a blinded second reviewer, and the sensitivity check on 14 directly dated provider records produced a 127.5-day median.
What is the disclosure?
5WPR is a communications agency and has a commercial interest in transition communications. The research was prepared with ChatGPT, which is operated by OpenAI, whose Sora and Assistants API closures are included. Neptune is included under its ownership at the time of notice, when its acquisition by OpenAI was pending. Agency client and vendor relationships with all named companies were not independently verified against private records.
When will the study be refreshed?
5WPR will freeze the next cohort on October 31, 2027, covering November 1, 2026 through October 31, 2027. The refresh keeps the two-per-parent cap and the target of 30, saves dated notices at discovery, adds a second reviewer for all deadline changes and a random subset of coding, and publishes a dated correction log for revised historical records.




