① Guide · Broadcom (CA)
Most full exits run 12 to 36 months and cost less in lock in than the vendor implies. This is the buyer side map: which product classes move easily, what migration and parallel run actually cost, where third party support fits, and why the plan is worth more than the migration.
The exit you can cost is the renewal you can win.
Broadcom (CA) mainframe renewals commonly arrive with steep uplifts, often well above historical run rates where capacity has grown without a negotiated cap. The vendor's strongest card is the assumption that you cannot leave. A product by product exit assessment tests that assumption, and the pattern we commonly observe is that a meaningful share of a CA portfolio is more portable than buyers assume. Utilities, reporting, and tape or storage management tools tend to have mature IBM and BMC equivalents. Only the deeply embedded scheduling and security layers earn the lock in premium they all claim.
The point is not that everyone should migrate. It is that the credible, costed plan to migrate is the leverage, executed or not. A renewal negotiated with a real alternative priced and timed behaves nothing like one negotiated without. Read this alongside our Broadcom (CA) renewal advisory page, which turns this map into a negotiation.
Directional ranges · vary by estate size, embedding, and change rate
| CA product class | Portability | Typical exit window | Main cost drivers |
|---|---|---|---|
| Utilities, reporting, output management (CA Deliver, CA View) | High | 6 to 12 months | Output reformatting, archive migration, validation |
| Tape and storage management | Medium to high | 9 to 18 months | Catalog conversion, data movement, parallel run |
| Scheduling and workload automation (CA 7, CA Workload Automation) | Medium to low | 18 to 36 months | Job dependency mapping, calendar conversion, long parallel run |
| Security (ACF2, Top Secret) | Low | 24 to 36 months | Rule translation to RACF, access recertification, risk sign off |
| Database and data management (IDMS, Datacom) | Low | 24 to 48 months | Application rewrite or data migration, regression testing |
Windows are migration plus safe parallel run, not raw install time. The embedded layers dominate the timeline; the portable layers dominate the early wins.
The people and project cost to move the function: rule translation, job conversion, data movement, and the testing that proves equivalence. This is the largest line for embedded products and a modest one for utilities.
The work scales with embedding, not license size.
Running old and new side by side until the replacement is trusted. For security and scheduling this period is long and deliberate, and it carries double license cost while it lasts. Underbudgeting it is the most common exit mistake.
Trust is bought in parallel run time.
Where you want to stop paying vendor maintenance uplifts before migration completes, third party support on stable CA products bridges the gap and removes the deadline pressure that makes migrations risky. Best suited to functionally frozen estates.
A bridge lets you migrate at a safe pace.
The cost of the IBM, BMC, or other product you move to, negotiated as its own deal. Done well, the displacement target becomes a second negotiation you also control rather than a price you accept to escape the first.
The destination is negotiable too.
④ What the plan is worth
The migration is the fallback. The costed plan to leave is the leverage. Most clients keep the leverage and never migrate.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Most full exits run 12 to 36 months. A standalone utility moves in two to three quarters; an embedded scheduler or security product takes two to three years to migrate and parallel run safely. The timeline is set by what depends on the product, not by the software.
Often less hard. Buyers overestimate lock in for utilities and reporting with mature alternatives, and underestimate it only for embedded scheduling and security. A product by product assessment usually finds more is portable than assumed.
Frequently. It lets you stop paying vendor uplifts while you migrate at a sustainable pace rather than under deadline pressure. Best for functionally frozen products where you control the change rate. See our support reinstatement guide.
No. The credible, costed plan is the leverage whether or not you execute it. Many engagements use the assessment to secure a much better renewal and never migrate. The plan does the work; the migration is the fallback.
Related: Broadcom (CA) licensing hub · renewal advisory · support reinstatement · license negotiation service
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →