MOVEit Transfer's Sunset Is a Reminder That Vendor End-of-Life Is a Security Decision
On November 18, 2026, MOVEit Transfer 2025.1 leaves Progress Software's Active support phase and enters Sunset. No more service packs. No more hotfixes. If a defect is found and verified, Progress will make a "best effort" to describe a workaround and nothing more. For most enterprise software, that's a line item for the procurement team to schedule around. For MOVEit, a file-transfer product with one of the decade's largest vendor-originated breaches on its record, it's a date engineering leadership should already have on a dependency map.
What "Sunset" means for this specific version
Progress's own product lifecycle page is blunt about what the Sunset phase means in practice: the version stops receiving service packs or hotfixes entirely. If a customer finds and verifies a defect, Progress will try to describe a manual workaround, but the underlying code in that release does not get patched. The company's stated recommendation is the same one every vendor gives at this point in a lifecycle: upgrade to the current version. MOVEit Transfer 2025.1 won't be fully retired until May 2027, so it keeps running, but from November 18 onward it runs without a path to a real fix if something breaks.
That would be a routine maintenance notice for most software. It isn't routine for MOVEit, because this isn't the product's first brush with a catastrophic, vendor-side security failure. The 2023 MOVEit breach exploited a zero-day in the transfer tool itself and compromised hundreds of organizations that had treated secure file transfer as commodity infrastructure, not a system worth watching closely. Progress has kept shipping security bulletins since, including one as recently as September 2026 (tracked as CVE-2026-8800 in the National Vulnerability Database) covering the current MOVEit Transfer line. A product with that pattern losing its hotfix path on a specific version isn't paperwork. It's the version of your dependency map where "we'll patch it when something comes up" stops being an option.
Teams that are evaluating custom software development instead of renewing another year on a sunsetting vendor product aren't doing it because they distrust file transfer as a category. They're doing it because owning the patch cycle on a system that moves sensitive data between partners is worth more than the convenience of not building it.
Why "best effort workaround" is a worse deal than it sounds
A workaround is not a fix. It's a documented set of steps, often a configuration change or a manual process, that reduces exposure until an actual patch exists. For a version in Sunset phase, no patch is coming, so the workaround is the permanent state of the system. Every workaround Progress documents going forward for 2025.1 has to be applied and re-verified by someone on your team, indefinitely, for a product your team doesn't control the source of. That's a materially different operational burden than "apply the hotfix and move on," and it's the burden every customer still on this version inherits the moment the clock runs out.
The dependency nobody re-evaluates until it breaks
File transfer tools get this treatment more often than almost any other category of enterprise software: stood up once by a team that has since moved on, left running because it works, and never revisited until a CVE or a lifecycle notice forces the question. The 2023 breach is the clearest evidence that this habit is expensive. Hundreds of downstream organizations didn't choose MOVEit directly, they inherited it through a vendor or partner who had, and found out they were exposed only after attackers had already used the zero-day. A lifecycle sunset date is the rare case where the vendor tells you exactly when the risk profile changes, in advance, instead of you finding out from a breach disclosure.
- Inventory every system still running MOVEit Transfer 2025.1, or any other product entering a vendor's unsupported phase in the next two quarters, and attach an owner to each one by name.
- Read the actual lifecycle terms, not the marketing page. "Best effort workaround" and "no SLA" are not the same promise as "supported," even when the software keeps functioning normally.
- Treat a sunset notice on a file-transfer or data-movement tool as a security review trigger, not just an upgrade reminder, given how often this category has been the entry point for breaches that started somewhere else entirely.
- Decide deliberately between upgrading to the vendor's current release and replacing the dependency with something your team controls end to end, rather than defaulting to "upgrade" because it's the path of least resistance.
The calendar doesn't care that the software still works. On November 18, the question stops being "is it running" and becomes "who fixes it when it doesn't."
What this changes about vendor lifecycle tracking
Most engineering organizations track uptime obsessively and vendor lifecycle calendars almost not at all, because a sunset date doesn't page anyone. MOVEit's history is a useful, uncomfortable reminder of why that gap matters for exactly this category of software: systems that move sensitive data between organizations are high-value targets, and "it has worked fine for years" was true right up until 2023, when it stopped being true for hundreds of companies at once. A version entering Sunset phase isn't an emergency by itself. It's the moment to decide, with a clear head and no incident in progress, whether the right answer is an upgrade, a migration, or finally building the piece you've always rented.