CA Technologies Is Gone. What Replaced It Is Worse.

When Broadcom acquired CA Technologies in 2018 for $18.9 billion, the mainframe software market changed overnight. CA had been a relationship-driven vendor. Customers had personal account managers. Pricing reflected long histories and negotiated loyalty discounts. Renewals were conversations, not ultimatums.

Broadcom operates differently. The company's playbook, refined through its earlier acquisition of Symantec and later applied to VMware, treats acquired software portfolios as cash-generation engines. The approach is straightforward: standardize pricing upward, eliminate legacy discounts, bundle aggressively, reduce support overhead, and rely on switching costs to keep customers paying.

For CIOs running mainframe environments, this shift has been painful. Products like CA 7, ACF2, Top Secret, IDMS, Endevor, and SYSVIEW are deeply embedded in critical production systems. These are not applications you replace in a quarter. They touch batch scheduling, security, databases, source control, and system monitoring. Broadcom knows this. Their pricing reflects that knowledge.

This playbook explains what changed, what it means for your renewal, and what you can actually do about it.

The Three Pillars of Broadcom's Pricing Strategy

Aggressive enforcement and dramatic price increases. Multiple large customers have reported renewal demands of 200-400% above prior contract levels. UnitedHealthcare publicly alleged that Broadcom demanded hundreds of millions of dollars more for the same CA software their organization had been running for years. Broadcom enforces contract deadlines strictly. There are documented cases of Broadcom threatening to cut off access to mission-critical software if new terms were not accepted by the deadline. This is not CA's old approach of extending grace periods and working toward a mutually acceptable deal. This is commercial pressure applied with precision.

Pricing standardization and the elimination of legacy discounts. CA granted deep, custom discounts to long-standing customers over decades of relationship-based selling. Broadcom is systematically unwinding those discounts. Every renewal is an opportunity to align a customer to Broadcom's standard price book, which sits significantly higher than most legacy rates. Standard contract terms now include predetermined annual uplift clauses, typically 5-7% per year, compounding over the contract period. If your current CA deal reflects years of negotiated concessions, expect Broadcom to treat the next renewal as a reset.

Product bundling and reduced support. Broadcom pushes customers to bundle CA software renewals with other Broadcom products, including products the customer does not use. The goal is to increase total deal size and make it harder to compare pricing on a product-by-product basis. Customers report being told they must upgrade to broader, more expensive suites rather than renewing individual tools a la carte. Meanwhile, Broadcom drastically cut CA's sales and support staffing. Account management has become less proactive, support response times have lengthened, and the human relationships that made CA easier to work with have largely disappeared.

The underlying logic: Broadcom prioritizes roughly 600 top-tier accounts. If you are not in that group, you are likely receiving take-it-or-leave-it offers with minimal negotiation flexibility. Broadcom is explicitly comfortable losing smaller customers. Their strategy depends on the majority of customers concluding that the cost of switching exceeds the cost of the price increase. For mainframe software, that calculation often favors Broadcom. But not always.

Why Your Legacy Contract Might Be Your Best Weapon

Before you negotiate anything, audit your existing contracts. This is the single most valuable step most CIOs skip.

When Broadcom acquired CA, it assumed CA's existing contracts through an assignment process. Those contracts contain specific terms: renewal caps, discount levels, perpetual license rights, support obligations, and pricing metrics. Broadcom is legally bound to honor those terms for the duration of the contract period. But Broadcom will not volunteer this information. Their negotiators will present Broadcom's standard terms as the baseline, regardless of what your CA contract actually says.

Gather every document: master agreements, amendments, product schedules, order forms, proofs of entitlement, and any communications about the CA-to-Broadcom transition. For each product, document the term end date, license type (perpetual vs. subscription), pricing metric (MIPS, MSUs, CPU), discount percentage, renewal caps, and any special provisions like transfer rights or bundled entitlements.

A pattern we see frequently: Customers with perpetual CA licenses and capped renewal rates have significantly more leverage than those on term licenses approaching expiration. If your CA contract includes a renewal cap of 3-4%, Broadcom cannot unilaterally impose a 7% uplift or a 200% price reset. Courts have been sympathetic to customers on this point, with injunctions issued to prevent Broadcom from terminating licenses in violation of inherited contract terms. The willingness to cite your contract clause by clause can fundamentally change the negotiation dynamic.

Locate the assignment notice from 2018-2019. If it is missing, request written confirmation from Broadcom that your contract was assumed under the original terms. Compare Broadcom's standard Foundation Agreement or EULA side by side with your CA agreement. Note every difference. Broadcom's standard terms are almost always less favorable than legacy CA terms, particularly on renewal caps, support scope, and audit provisions.

The ELA Play: Consolidation as Leverage

If you are running multiple CA products, and most mainframe shops are, your strongest negotiating position is a consolidated enterprise license agreement covering the entire portfolio. The alternative, letting each product renew separately on staggered dates, is exactly what Broadcom wants. Staggered renewals let Broadcom pick off products one at a time. Each individual renewal is a smaller deal with less leverage. You cannot credibly threaten to switch your scheduler when your security product renewed three months ago and your database tools are not up for renewal until next year.

Co-terming all CA products to a single renewal date concentrates your leverage. Broadcom faces the prospect of losing an entire portfolio at once, not just one tool. A consolidated 3-to-5-year deal also provides pricing stability, which matters enormously when the alternative is Broadcom's 7% annual uplift compounding over time.

What to negotiate inside the ELA: Push for renewal caps at 3% or below, well under Broadcom's standard 5-7%. Include provisions for adding new licenses at the same discounted rates. Negotiate a transferable spend clause so that if you decommission one product, its value applies to another Broadcom product. And insist on flex-down rights. If your MIPS consumption declines, either through workload optimization or migration, your licensing costs should follow.

The timing matters. Start renewal discussions at least 12 months before contract expiration. Align negotiations to coincide with Broadcom's fiscal quarter or year-end, when their deal teams have the strongest motivation to close. Never let licenses expire while still negotiating. Have a contingency extension clause agreed in advance.

The Competitive Landscape: IBM, BMC, and the Art of the Credible Alternative

Broadcom's entire commercial model depends on one assumption: that switching costs are prohibitively high. For some CA products, that assumption holds. For others, it does not. Understanding where realistic alternatives exist, and where they do not, is essential for any negotiation.

Workload automation (CA 7): This is where alternatives are most viable. BMC Control-M is an industry-leading enterprise scheduler that spans mainframe and distributed environments. BMC provides conversion utilities for migrating CA 7 job definitions. Some organizations run dual-vendor strategies, moving new workloads to Control-M while phasing out CA 7. IBM Z Workload Scheduler is another option, though less commonly chosen. A concrete migration plan from CA 7 to Control-M, with timelines, resource estimates, and a BMC proposal in hand, is one of the most powerful negotiation tools available.

Security (ACF2, Top Secret): Alternatives are more constrained here. IBM RACF is the native z/OS security subsystem and is often included with the operating system license. Migration from ACF2 or Top Secret to RACF is technically feasible. IBM and specialist firms offer migration toolkits. But this is a major project that touches every system permission, user profile, and access rule in the environment. It is not a 90-day effort. It is a 12-to-24-month program with significant testing requirements. That said, the one-time migration cost versus ongoing Broadcom license increases can make the economics compelling over a 5-year horizon, particularly if Broadcom is pushing for a large step-up. Even if you do not intend to migrate, having a RACF migration plan with cost estimates gives Broadcom a reason to negotiate.

Database tools (IDMS, Datacom, DB2 utilities): For CA's proprietary databases, alternatives are the hardest to execute. IDMS and Datacom underlie decades of core applications. Migrating to Db2 means unloading data, transforming schemas, and rewriting application code. This is application modernization, not a tool swap. For CA's DB2 utilities and performance tools, BMC offers strong alternatives through its AMI Database suite, and these are worth evaluating. But for IDMS and Datacom shops, the realistic play is negotiating longer-term maintenance-only pricing rather than planning a near-term exit.

Monitoring (SYSVIEW): IBM OMEGAMON and BMC MainView/AMI Ops both provide comprehensive mainframe monitoring. Switching entails re-training operations staff and converting custom dashboards and automation scripts, but the technical migration is more manageable than security or database migrations.

The dual-vendor strategy: You do not need to replace everything at once. Starting with one competitor product, even in limited capacity, signals that you are not wholly dependent on Broadcom. If Broadcom sees that you already run BMC Control-M for some workloads, extending it to replace CA 7 entirely is not far-fetched. Running parallel tools is a temporary cost, but it can be a tactical investment that pays for itself in negotiation leverage.

Making the Alternative Threat Credible

The difference between a negotiation where Broadcom gives you 5% and one where they give you 30% often comes down to whether they believe you will actually switch. Talking about alternatives is not enough. Broadcom's negotiators have heard it before. You need evidence.

Run a formal benchmarking exercise or RFP. Solicit written proposals from BMC for replacing CA 7 with Control-M, or from IBM for a RACF migration. Get hard numbers: total cost over 5 years, migration timeline, and resource requirements. If BMC says they can replace your CA scheduling suite at 30% lower total cost, that data point changes the conversation.

Build a documented exit plan for each major product. Not a slide deck. A plan with named resources, realistic timelines, stakeholder sign-offs, and budget estimates. "Migrate from CA Top Secret to RACF over 24 months, using IBM's toolkit, with 4 internal FTEs and $400K consulting spend, target completion Q4 2026." The specificity is what makes it credible.

Use timing deliberately. Have alternative proposals finalized 6 months before your Broadcom renewal. If Broadcom senses last-minute scrambling, they will call the bluff. If you have been testing a BMC product for 4 months and have a firm migration offer valid through your renewal date, the seriousness is hard to ignore.

Know Broadcom's pressure points. Broadcom does not want high-profile departures. Every customer that leaves encourages others. If negotiations stall, communicate that executive leadership is reviewing alternatives and that a board presentation on migration options is scheduled. This often prompts Broadcom to revisit the deal structure. They would rather give a discount than lose a reference account.

Facing a Broadcom CA Renewal?

Our Broadcom licensing specialists have reviewed hundreds of CA mainframe contracts. We provide fixed-fee, vendor-independent support for ELA negotiations, legacy contract audits, competitive benchmarking, and transition planning.

Book a Confidential Call →

Transition Planning: When You Decide to Move

If the decision is made to migrate away from one or more Broadcom products, the execution must be disciplined. Mainframe systems are the backbone of critical processes. A failed scheduler migration or a security cutover that locks out production users is not a theoretical risk. It has happened.

Always choose phased migration over big-bang. For workload automation, migrate one application or batch subsystem at a time. Run the new scheduler in parallel and validate that every job executes correctly before moving the next batch. For security, run ACF2 or Top Secret alongside RACF in parallel mode during cutover testing. For database tools, migrate one Db2 subsystem at a time and verify performance before proceeding.

Each product category has specific migration mechanics. Security migrations require exporting user profiles, access rules, and dataset rules, then importing into RACF equivalents with extensive verification. Scheduler migrations require converting CA 7 job schedules, calendars, and dependencies, and BMC provides conversion utilities for this. Database migrations from IDMS or Datacom to Db2 require unloading data, transforming schemas, and rewriting application calls, which is part of a larger application modernization effort.

The human dimension matters as much as the technical one. Operations staff and developers may have used CA tools for decades. Include comprehensive training. Identify champion users who become experts early through pilot projects and then mentor others. Update every runbook, operating procedure, and monitoring dashboard to reflect the new environment before declaring cutover complete.

During the transition, define how old and new tools coexist without conflict. Watch resource overhead from running parallel tools. Have a fallback plan: if the new tool encounters a severe issue in production, you need the ability to temporarily revert. Keep data synchronized between old and new systems until the cutover is declared final and verified.

SAM: The Foundation Everything Else Depends On

None of the strategies above work without accurate Software Asset Management data. You cannot negotiate a right-sized ELA if you do not know exactly what you are running. You cannot build a credible exit plan if you are not sure which products are actually in use versus installed but dormant.

Perform a fresh inventory of every CA/Broadcom product deployed across your mainframe environment. Identify each instance, version, and usage metric. Map every installed product to its purchased license and capacity entitlement. Flag over-deployments (compliance gaps that Broadcom could use as audit leverage) and under-deployments (where you are paying for capacity you do not consume).

Look specifically for overlap and redundancy. Mainframe environments accumulate tools over decades. You may have CA Endevor alongside Git-based pipelines, or CA SYSVIEW alongside IBM OMEGAMON. Quantify the overlap. If Broadcom's bundling has introduced functionality you already get elsewhere, that is wasted spend you can eliminate at renewal.

Track usage trends over time, especially for capacity-based licenses. Broadcom's pricing often depends on peak MSU consumption. Use SCRT reports and resource management tools to see whether usage is rising, stable, or declining. Document planned reductions. If growth is expected, lock in additional capacity at current rates before the renewal. If you are planning workload migrations off the mainframe, that declining usage trajectory is a powerful argument against a multi-year commitment at current levels.

Audit preparedness matters: Broadcom reserves the right to audit with as little as 30 days notice. Simulate an internal audit now. Ensure proof of licenses is in order and deployment matches entitlements. Proactively fixing compliance gaps removes Broadcom's most powerful lever: the threat of back charges or forced upsells at list price for unlicensed usage. A clean SAM position means you negotiate from strength, not from exposure.

Planning for 2025 to 2027: What to Do Now

Consolidate and optimize. Negotiate a single umbrella agreement. Eliminate duplicate tools. Reduce license counts where SAM data shows underutilization. Every dollar of waste removed from the current footprint is a dollar of leverage in the next negotiation.

Budget for reality. Assume 5-7% annual increases under multi-year maintenance. If your contracts are expiring, budget for a potential step-change increase and plan the negotiation accordingly. If you are upgrading to IBM z16 hardware, remember that increased capacity will increase capacity-based license costs. Build both a "stay with Broadcom" and a "migrate to competitor" budget scenario showing total costs over 3-5 years. Hold roughly 10% of Broadcom spend as contingency for unplanned license needs or audit findings.

Engage your board. Mainframe software licensing has gained board-level visibility because of the magnitude of Broadcom's price increases. Executive backing empowers IT leadership to take tougher negotiating positions. Keep your CEO and CFO informed about the commercial dynamics, the alternatives being evaluated, and the potential cost scenarios. A CIO who can say "the board has approved a migration budget if terms are not acceptable" has fundamentally different leverage than one negotiating without that mandate.

Think long-term about the mainframe itself. If the mainframe remains strategic to your organization for the next decade, invest in stable vendor relationships and accept that some premium is the cost of guaranteed support and continued product development. If you are planning to downsize mainframe workloads, be more aggressive with Broadcom. Do not get locked into 5-year contracts for applications slated to migrate by 2027. Negotiate shorter extensions or flexible arrangements that match your actual trajectory.

And remember that Broadcom now owns VMware and Symantec in addition to CA. Set an internal policy that each domain is evaluated on its own merits. Do not accept cross-portfolio bundling that does not fit your needs. The fact that you use VMware does not mean your CA renewal should be tied to your vSphere licensing. Unbundling Broadcom's cross-portfolio pressure is a separate but related negotiation challenge.

The Bottom Line

Broadcom's acquisition of CA created a genuinely difficult vendor relationship for mainframe shops. The pricing increases are real. The support degradation is real. The bundling pressure is real. But Broadcom's strategy only works as long as customers conclude that paying more is easier than changing.

The CIOs who get the best outcomes are the ones who invest in the unglamorous work: contract audits, SAM optimization, competitive benchmarking, documented exit plans, and early engagement with BMC and IBM. None of that is exciting. All of it is effective.

The worst position is to arrive at a Broadcom renewal with no SAM data, no knowledge of your legacy contract terms, no alternative proposals, and 90 days until expiration. That is the position Broadcom designs for. Do not give it to them.