CA to Broadcom: Contract Implications

The 2018 Broadcom acquisition of CA Technologies did not simply change a contracting counterparty. It changed how CA software contracts are interpreted, renewed, audited, and enforced. Customers who hold contracts signed under CA Technologies — or under the prior eras (Computer Associates, then CA Inc.) — live with the contract language they signed plus the Broadcom interpretation of that language. The gap between those two can be material.

This article sets out the practical contract implications of the CA-to-Broadcom transition for buyer-side stakeholders: which clauses changed in interpretation, which clauses changed in successor enterprise agreements, what legacy contractual protections still hold, and how customers should think about contract strategy in 2026 and beyond.

The contractual continuity question

The legal position is straightforward: the contractual obligations of CA Technologies passed to Broadcom under the acquisition, and customers' existing CA contracts remained in force on their existing terms. There was no automatic renegotiation; existing rights and obligations on both sides continued.

The practical position is more nuanced. The interpretive posture of the contracting counterparty changed materially, and the contract terms in many CA agreements provided latitude that the CA Technologies field organisation interpreted one way and that the Broadcom field organisation interprets differently. Three patterns emerge.

Pattern 1: ambiguous language interpreted more aggressively

Where CA contract language is ambiguous — particularly around user counting, integration accounts, edition-feature scope, and module entitlement — Broadcom routinely takes a more revenue-favourable interpretation than CA Technologies did. Customers who relied on the CA Technologies interpretation as practical reality often discover at audit or renewal that the practical reality has changed.

Pattern 2: latent rights newly exercised

CA contracts include rights that CA Technologies rarely exercised — particularly audit rights, full pricing increases on renewal where contract caps did not apply, and de-bundling of bundled entitlements. Broadcom exercises these rights more routinely. The contract permitted it before; it just was not happening.

Pattern 3: successor contracts with narrower terms

When CA contracts come up for renewal under Broadcom, the successor contract typically has narrower customer protections than the predecessor: shorter price-lock provisions, broader audit clauses, narrower customer termination rights, less generous bundle definitions. The transition from a legacy CA contract to a Broadcom-era contract is itself a material commercial event.

Specific clauses where Broadcom's posture differs from CA Technologies

Audit clauses

CA Technologies audit clauses were generally exercised modestly and with negotiation latitude on findings. Broadcom's audit posture is more systematic, with broader data requests, more aggressive interpretation of findings, and less negotiation latitude in the early audit phases. The contract permitted both postures; the customer experience differs sharply.

User-counting definitions

CA contracts define users in language that often supported the customer's preferred interpretation (active users, named users with a usage qualifier). Broadcom routinely interprets the same language to mean the broadest user count (all users with active accounts, regardless of usage). Customers should re-read user-counting language with the Broadcom interpretive posture in mind.

Module bundling

Many CA enterprise agreements included broad bundled module entitlement: Clarity with all modules, CA Service Management with all components, the full Automic stack. Broadcom interprets bundling more narrowly at renewal: customers may find that legacy bundled modules are now invoiced separately, and that the historical implicit entitlement was not as broad as the customer believed.

Geographic and entity scope

CA contracts often included broad entity and geographic scope that customers used to deploy across affiliated entities and global operations. Broadcom enforces entity and geographic scope more strictly: contracts signed in the name of one entity do not extend to affiliates without explicit clause, and contracts with named geographies do not extend beyond them.

Price-increase caps

CA contracts varied on price-increase protection — some included annual caps, some did not. Where caps existed, CA Technologies generally honoured them in practice even where contractual ambiguity might have permitted otherwise. Broadcom honours caps where they clearly apply and takes available increases where they do not.

Subscription conversion

Perpetual licences with annual maintenance were the dominant CA model. Broadcom's strategic preference for subscription has produced renewal-time conversion pressure that customers' original perpetual contracts did not anticipate. The contractual right to retain perpetual entitlements typically exists, but the commercial framework around exercising that right has changed.

The legacy-contract review

Customers holding legacy CA contracts in 2026 should review them deliberately before any material engagement with Broadcom — renewal, audit, or other commercial discussion. The review should identify:

• Audit-rights clauses, including scope, frequency, notice periods, and dispute mechanisms.
• User and metric definitions, with particular attention to language that admits multiple interpretations.
• Bundling and module-entitlement language, with explicit mapping to current usage.
• Entity and geographic scope language.
• Price-increase caps and protective clauses.
• Renewal mechanics, including notice periods, default-renewal terms, and pricing baselines.
• Termination and exit rights, including for-cause and for-convenience provisions.
• Assignment and successor language, governing what happens on acquisition (and what already happened in 2018).

The customer should produce a contract summary that translates legal language into operational terms: what entities, what products, what user counts, what geographies, what modules, on what commercial terms, with what protective clauses. The summary becomes the reference document for all subsequent Broadcom engagement.

The successor-contract transition

When legacy CA contracts reach renewal under Broadcom, the proposed successor contract is rarely a like-for-like extension. Broadcom typically proposes a Broadcom-era contract with the standard Broadcom contractual framework. Customers should expect the following changes in the proposed successor:

Subscription as default

Perpetual licences with maintenance are typically replaced with subscription terms. The financial impact runs 40-80% above prior maintenance run-rate. The customer should negotiate the subscription-conversion economics explicitly and not accept them as automatic.

Narrower customer protections

Price-lock provisions tend to be shorter, audit clauses tend to be broader, termination rights tend to be narrower. The Broadcom standard form generally narrows the customer-protective elements of the prior CA Technologies framework.

Tighter scope

Entity and geographic scope tend to be defined more precisely, with affiliate access requiring explicit clause and geographic expansion requiring explicit licence.

Module unbundling

Bundled modules in legacy contracts are typically broken out in the successor contract, sometimes with material price implications.

Audit-clause expansion

Broadcom-era audit clauses tend to be broader than CA Technologies-era clauses: broader data-request rights, longer audit periods, broader scope language.

What to negotiate in successor contracts

The successor-contract negotiation is the customer's principal opportunity to restore protective contractual elements. The principal negotiation targets:

• Price-lock provisions: covering the contract term, with explicit cap on out-of-term renewal increases.
• Audit-clause narrowing: explicit scope, notice, and dispute mechanisms.
• User-counting definitions: precise definitions that close interpretive ambiguity.
• Module entitlements: explicit module list with clear scope.
• Entity and geographic scope: explicit definition consistent with operational footprint.
• Termination rights: for-cause termination on material breach, with explicit cure mechanics.
• Transition rights: data extraction, decommissioning support, transition-services pricing.

Each of these is negotiable. The successor contract is the moment to negotiate; once signed, the protective elements (or their absence) govern customer experience until the next renewal.

The dual-contract period

Many customers operate during a transition period in which some CA contracts are still legacy CA Technologies-era contracts and others are Broadcom-era successor contracts. This dual-contract period creates several practical considerations:

• Inconsistent interpretive treatment: legacy contracts and successor contracts may be interpreted differently by Broadcom, even where the underlying language is similar.
• Cross-contract bundling proposals: Broadcom may propose to bundle multiple legacy contracts into a single successor agreement; the bundle economics deserve close analysis.
• Audit coordination: audits that span legacy and successor contracts require careful scope management to avoid blending the interpretive frameworks.
• Renewal sequencing: the order in which legacy contracts convert to successor contracts affects total commercial outcome.

The dual-contract period is typically 2-5 years for large CA customers with multiple legacy agreements. Active contract-portfolio management during this period materially affects cumulative outcomes.

The audit-contract interaction

Audits are increasingly used as the catalyst for contract conversion. The pattern is recognisable:

1. Audit notification arrives 12-18 months before a major contract renewal.
2. Audit findings include material exposure.
3. Settlement proposal includes both the audit exposure and a go-forward purchase commitment.
4. The go-forward commitment converts the legacy contract to a successor contract, often on broader Broadcom-era terms.

Customers should recognise this pattern and respond strategically. The audit settlement and the contract conversion should be negotiated as separate elements, not as a single bundled outcome. The customer who allows them to be bundled often accepts contract terms that would not be accepted in a standalone renewal negotiation.

Common CA-to-Broadcom contract mistakes

1. Assuming continuity of interpretive practice. The contract continues; the interpretive posture does not. Re-read the contract with the Broadcom posture in mind.
2. Accepting successor-contract terms as the default. The Broadcom-era contract framework is not the only available framework; many protective elements can be negotiated back in.
3. Bundling audit settlement with contract conversion. These are separate negotiations and should be conducted as such.
4. Failing to track legacy-contract expirations and conversion timing. The contract-portfolio view is necessary for coherent strategy; managing contracts individually as they renew misses sequencing opportunities.
5. Underestimating subscription-conversion economics. The financial impact is substantial and should be quantified explicitly in renewal analysis.

Strategic posture for 2026

Customers who manage CA contract strategy actively in 2026 typically adopt the following posture:

• A current contract portfolio summary covering all CA contracts, with key terms translated into operational terms.
• A renewal-and-conversion calendar with explicit sequencing.
• A negotiation playbook for each major contract conversion, with defined targets on price-lock, audit-clause, scope, and protective provisions.
• A coordinated approach to audit-and-renewal interaction.
• An independent advisory relationship for major engagements.

The posture is not passive; CA contracts under Broadcom reward active management.

Final word

The CA-to-Broadcom contract transition is now seven years old but its effects remain live in customer commercial experience. Legacy contracts persist; successor contracts proliferate; interpretive postures differ. Customers who treat their CA contracts as static documents accept the consequences of changed interpretation and changed posture. Customers who re-read contracts under the current interpretive posture, manage the conversion sequencing deliberately, and negotiate successor terms with protective intent consistently produce better commercial outcomes. The cost of contract discipline is modest; the cost of contract neglect compounds.

CA-to-Broadcom contract implications — frequently asked questions

Are our existing CA contracts still valid under Broadcom?

Yes. The acquisition transferred the contracts on their existing terms. The contracts remain valid; the interpretive posture of the counterparty has changed.

Can Broadcom force conversion of our perpetual licences to subscription?

Not directly during the contract term. At renewal, Broadcom typically proposes subscription conversion; customers have negotiation latitude but the practical pressure to convert is real and increasing.

How do we maintain protective clauses from our legacy CA contract in a successor agreement?

By negotiating them explicitly. Broadcom's standard successor form is a starting point, not the only available form. Price-lock provisions, audit-clause narrowing, entity-scope definitions, and termination rights are all negotiable.

Should we sign a new master agreement with Broadcom?

Decide based on the comparative terms. A new master agreement may simplify ongoing engagement but typically narrows protective elements relative to legacy CA master agreements. The trade-off should be evaluated explicitly.

How does Broadcom typically use audits to drive contract conversion?

By bundling audit settlement with successor-contract commitment. The settlement is offered in conjunction with a go-forward purchase that converts the legacy contract to a Broadcom-era successor. Customers should negotiate the audit settlement and the contract conversion as separate elements rather than as a single bundle.