Progress MOVEit Transfer End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Progress MOVEit Transfer versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Progress MOVEit Transfer 2026.0 (18.0) is supported until November 17, 2027, its end-of-support date. Active support for Progress MOVEit Transfer 2026.0 (18.0) ends on May 19, 2027; security fixes continue until that end-of-life date. The next Progress MOVEit Transfer version to reach end of life is 2025.0 (17.0), on November 18, 2026. 2 tracked Progress MOVEit Transfer versions are declared end of life without a published date. The full Progress MOVEit Transfer lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2024.0 (16.0) | 2024.0.8 | May 22, 2024 | Not published | Past EOL | EOL |
| 2024.1 (16.1) | 2024.1.8 | Nov 20, 2024 | Not published | Past EOL | EOL |
| 2025.0 (17.0) | 2025.0.8 | May 21, 2025 | Nov 18, 2026 | 40 days remaining | Warning |
| 2025.1 (17.1) | 2025.1.7 | Nov 19, 2025 | May 19, 2027 | 222 days remaining | Active |
| 2026.0 (18.0) | 2026.0.5 | May 20, 2026 | Nov 17, 2027 | 404 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/progress-moveit-transfer)
Progress MOVEit Transfer lifecycle status — the real story
Progress MOVEit Transfer is a managed file transfer server. Progress ships two major releases a year, in May and November (2025.0 on May 21, 2025, 2025.1 on November 19, 2025, 2026.0 on May 20, 2026), and publishes three dates per release on its MOVEit Product Support Lifecycle page: Active, Sunset and Retired. In the Sunset phase, "No service packs or hot fixes are provided"; in the Retired phase Progress offers only 'best effort' support and "No product updates are provided". The page also says "Releases not listed in the table below are considered Retired", and on October 9, 2026 it lists only 2026.0, 2025.1 and 2025.0, so 2024.1 and every older release is retired.
The reason this matters is CVE-2023-34362, the MOVEit Transfer SQL injection that CISA added to its Known Exploited Vulnerabilities catalog on June 2, 2023 and flags as used in ransomware campaigns. It is the only MOVEit Transfer entry in the catalog (catalog 2026.10.08). Progress has shipped fixes past the Sunset date before: 2025.0 entered Sunset after May 20, 2026, and the 2025.0.8 hotfix still shipped on June 22, 2026. Treat that as an exception, not a promise, because the policy says Sunset releases get no service packs or hot fixes.
Field mapping: support is the vendor's SUNSET date, the day the Active phase (service packs and hot fixes) is over. eol is the vendor's RETIRED date, after which there are no updates and only best-effort support. We copy both exactly as Progress prints them. Release dates and the latest build in each line come from the MOVEit Transfer release notes on docs.progress.com. Progress numbers each release twice (2026.0 is also 18.0), and the cycle label shows both.
Progress MOVEit Transfer release and support pattern
Across the 5 release lines with a published release date, Progress MOVEit Transfer has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 1.5 years from its release to its end-of-life date (measured on the 3 lines with both dates published).
Of the 5 release lines tracked, 2 are past end of life and 3 are still within support; 2 are marked end of life without a published date. The newest line, 2026.0, was released May 20, 2026. The next scheduled end of life is 2025.0 on November 18, 2026 — 39 days from this build. The longest-supported line currently published is 2026.0, to November 17, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Progress MOVEit Transfer end of life mean for your organization?
When a version of Progress MOVEit Transfer reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Progress MOVEit Transfer should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Progress MOVEit Transfer reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Progress MOVEit Transfer versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Progress MOVEit Transfer has 2 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Progress MOVEit Transfer is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."