Control-M End of Life (EOL) Dates and End of Support (EOS) Dates
Control-M end of life (EOL) and end of support (EOS) dates: 4 Control-M versions have reached EOL, including Control-M 9.0.20 (EOL date: Jul 23, 2025) — no longer receiving security updates or patches. Control-M 9.0.22.100 is the current supported release, with support through May 19, 2030 — 2 versions in active support. Also see Artifactory lifecycle dates for related end-of-life information.
Currently Supported Control-M Releases - Active EOS/EOSL Support (2)
| Release | Released | Limited Support | Full Support | Latest |
|---|---|---|---|---|
| 9.0.22 | (1 year and 6 months ago) | (in 3 years and 5 months) | (in 1 year and 5 months) | 9.0.22.100 (5 months ago) |
| 9.0.21 | (4 years and 2 months ago) | (in 9 months) | (1 month and 3 weeks ago) | 9.0.21.300 (2 years and 3 months ago) |
Control-M End of Life (EOL) Releases - No Longer Supported (4)
| Release | Released | Limited Support | Full Support | Latest |
|---|---|---|---|---|
| 9.0.20 | (6 years and 3 months ago) | (1 year and 3 months ago) | (2 years and 6 months ago) | 9.0.20.200 (5 years ago) |
| 9.0.19 | (7 years and 8 months ago) | (2 years and 8 months ago) | (3 years and 10 months ago) | 9.0.19.200 (6 years and 10 months ago) |
| 9.0.18 | (8 years and 10 months ago) | (3 years and 7 months ago) | (5 years and 7 months ago) | 9.0.18.200 (8 years and 1 month ago) |
| 9.0.0 | (11 years and 4 months ago) | (6 years ago) | (8 years and 3 months ago) | 9.0.00.200 (10 years and 5 months ago) |
Control-M end of life planning starts with one question: which release do you run? BMC sets an end of support date for each version of this enterprise workload automation product, which helps you orchestrate business processes, applications and data workflows across its components. Below are the latest dates for every released version.
Control-M End of Life Dates for Each Release
BMC gives three years of full support from each release, then two years of limited support for high-impact problems only. That support policy, shown in the supported product list, produces the end of support date for every release.
| Release | Released | Full support ends | Limited support ends |
|---|---|---|---|
| 9.0.22 | 19 May 2025 (patch 9.0.22.100, 17 Jun 2026) | 19 May 2028 | 19 May 2030 |
| 9.0.21 | 8 Sep 2022 | 30 Sep 2026 | 8 Sep 2027 |
| 9.0.20 | 24 Jul 2020 | 30 Apr 2024 | 23 Jul 2025 |
Run a supported release only, and check yours with ctm -v. The latest version support data is also published as CPE identifiers, an RSS feed, a calendar feed and a GitHub page for corrections, with BMC documentation as the source.
Control-M 9.0.21 Support Timeline
An extension of support moved full support for 9.0.21 to 30 September, and the extended window changes nothing else. Because the extension leaves the final date alone, limited support covers 9.0.21 until September 2027, so you should upgrade before then.
Control-M End of Support Announcements by Platform
The deprecation and end of support page lists every announcement, and a technical bulletin usually follows. Recent notices include:
- Control-M/Agent on Debian 11 and Amazon Linux 2 (11 August 2026)
- Microsoft SQL Server 2016 and PostgreSQL 12, 13 and 14 database releases
- Windows 10 and Windows Server 2016, plus Red Hat, CentOS and Ubuntu 20.04 LTS
- Oracle Solaris and 32-bit UNIX binaries
- Control-M/EM (Enterprise Manager) cli utility and emdef utility suite replacement
Older end of version support notices cover add-ons such as managed file transfer, plug-ins and batch integrations, for both mainframe and distributed systems. An XML format deprecation is also under way, with deprecated jobs still running for now.
Control-M/Agent and Control-M/Server Platforms
Agents and servers lose operating system and database coverage first, so match each platform to the latest matrix before any upgrade.
Automation API and Utility Changes
Scripts built on legacy utilities need rewriting once those tools drop out of the product.
Control-M Client Deprecation and the Move to Control-M Web
From 9.0.22.100 the Control-M Client is deprecated: no new features arrive and only critical bugs are fixed. BMC recommends Control-M Web and plans to end support during 2027, announced in a notice dated 17 February 2025. Review the Control-M Web capabilities and adoption guides, ask the community, or contact BMC Support. Self service users should test their workflows early.
Replacement and Migration Plan Away from Control-M
Rising license costs, limited scalability and weak cloud support push some teams toward a replacement once their release nears its end of support. A good migration plan starts with a conversion tool that maps your job definitions, then moves workloads in stages.
Choosing an Alternative
Compare architecture, orchestration, SLA monitoring and integrations, and estimate TCO and cost savings, because business users want self-serve access.
Preparation
Audit your existing definitions and propose a target design.
Implementation
Complete a configured deployment and migrate the first batch of production jobs.
Delivery Iterations
Each later phase takes two to four months and overlaps the last.