Salesforce contracts in mergers and acquisitions. Align the renewals before you disclose.

A merger turns two routine Salesforce renewals into one large negotiation. Whether the combined volume helps you or becomes an upsell depends on what you tell the account team, and when, far more than on the rate.

A merger or acquisition turns two routine Salesforce renewals into one negotiation with a lot more money on the table. Whether that works for you or for the account team depends on the order of events: which contract renews when, and at what point Salesforce learns the combined numbers.

What changes in Salesforce contracts on day one of a merger?

Very little, and far less than most integration plans assume. Two Salesforce agreements keep their own terms, metrics and uplift schedules until each one reaches its own renewal. The Salesforce Main Services Agreement (MSA, formerly the master subscription agreement) governs what can move and when.

• Term. Each contract runs to its own anniversary regardless of the corporate event.
• Metrics. Seat counts and editions stay as contracted, per legal entity and per order form.
• Uplift. Each agreement carries its own renewal increase unless someone renegotiates it.
• Renewal notice. The standard MSA renews subscriptions for one year terms unless either side gives written notice at least 30 days before the term ends. Some negotiated order forms set a different window, and a merger team busy with other work misses it easily.
• Added seats. Seats added to an existing subscription end on the same date as that subscription, so buying extra users on one contract ties them to that contract's anniversary.
• Repricing on reduction. Under the standard MSA, Salesforce can reprice any renewal where subscription volume or term length falls, without regard to the prior per unit price. Removing duplicate seats after a merger is exactly that kind of reduction.

The practical result is that on the day the deal closes you hold two separate commercial positions with Salesforce. That is an advantage, as long as you do not give it away in the first few weeks.

Does a stock deal or an asset deal change the contract position?

Yes. A stock purchase usually carries the contract with the legal entity, so the acquired company's order forms simply keep running. An asset purchase often needs vendor consent to assign, which turns the assignment clause into something Salesforce can hold over you. Read it in the first week of diligence, not the last.

The current standard MSA allows the whole agreement to be assigned without consent in a merger, acquisition or sale of all or substantially all assets. One business unit is rarely "substantially all", and moving only some order forms needs consent that Salesforce may not unreasonably withhold. Older or negotiated paper can differ, so check the version you signed.

What if the acquirer competes with Salesforce?

The standard MSA allows either side to terminate on written notice if the other is acquired by a direct competitor, with a refund of prepaid fees for the rest of the term. It rarely applies, but a software company buying a Salesforce customer should have counsel check it.

Why does disclosure timing cost more than the rate?

Combined volume is the most valuable piece of information in the deal, and buyers usually hand it over for free. Once the account team can see the consolidated footprint, it prices an expansion rather than a renewal.

In the situations we supported, buyers who shared combined volume first still got per unit rates that looked fine on paper. What changed was the thing being priced. Two renewals Salesforce had to defend became one growth opportunity it could plan around.

The account team reads combined volume as an upsell. You can read it as bargaining power. Which reading wins depends on whether the renewals are aligned before the number is shared.

What will the account team say, and how should you answer?

Expect the account team to call soon after the announcement. These are the lines we hear most often in merger situations, with the replies that keep the sequence in your hands.

• "Congratulations on the deal. Can you share the combined user count so we can plan?" Reply that both contracts continue as signed and that you will share consolidated numbers when you open the renewal, on your date.
• "We can bring everything onto one order form now and give you a better blended rate." Ask for the proposal in writing with the rate, the term end date and the renewal cap. A blended rate that puts the combined spend on the earlier anniversary usually costs more than it saves.
• "The acquired company's users need to be on your contract to stay compliant." Ask which clause says so. Once the deal closes, the acquired company is an affiliate, and its users stay licensed under its own order forms until they renew, as long as they keep working in the org those forms cover.
• "This pricing is only available if you sign by quarter end." Quarter end pressure is routine. Our note on end of quarter deadline pressure covers how to treat it. In a merger, your renewal date sets the timetable.

What have we seen in Salesforce merger and divestiture negotiations?

Across roughly 20 to 30 Salesforce situations tied to mergers, acquisitions and divestitures that we supported in 2024 and 2025, the avoidable cost almost always came from timing and disclosure. The headline rate was rarely where the money went. Three patterns stood out.

• Early disclosure. Buyers who disclosed combined volume before aligning renewals paid 5 to 12 percent more on the consolidated deal. It is the clearest pattern in our file, and it is entirely within the buyer's control.
• Mid term true forward. Misaligned anniversaries forced a mid term true forward in about 1 in 3 cases. That locked the higher combined run rate early and removed the renewal as the point where terms could have changed.
• Late transition terms. Divestitures without a transition services clause agreed up front cost weeks of access risk and rushed terms. The separating business needed continuity, and it paid more for continuity bought late.

Neither the disclosure cost nor the true forward is a rate outcome. Both come from sequencing, which is why they deserve more attention than the discount conversation that follows. Once the contracts are settled, our renewal negotiation guide covers the ordinary cycle.

What does early disclosure cost in dollars?

Take a hypothetical pair of companies. Company A spends $1,800,000 a year on Salesforce and renews in March. Company B spends $700,000 a year and renews in October. The table applies the low and high ends of the range we observed to a consolidated three year deal.

Compare that with the price of waiting. Extending Company A's contract from March to October at its current rate costs about $1,050,000 for the seven month bridge ($1,800,000 divided by 12, times 7). The company would have spent that money anyway. In return, the full $2,500,000 is negotiated once, on the later date, before Salesforce has seen the combined count.

How should two Salesforce footprints be consolidated?

On evidence, and at the later anniversary. Run a usage and process overlap review across both orgs first, then choose to consolidate or coexist, with a dated transition plan behind the choice.

The wider picture sits in the Salesforce knowledge hub. If the combined footprint spans Sales Cloud, Service Cloud, Marketing Cloud and Data Cloud, work through our brief on multi cloud negotiation before you pick an order for the renewals.

Why consolidate at the later anniversary?

The later anniversary is the first date on which the whole combined footprint is open to negotiation. Aligning to the earlier one hands Salesforce the combined volume while the second contract still has months to run. Bridge the earlier contract to the later date, then negotiate once. Our co term anniversary calendar shows how to plan the bridge.

Is fast consolidation onto one contract the cheapest route?

Usually not. The common advice is to fold everything onto one Salesforce contract quickly for a volume discount. We disagree, because in our situations speed produced the true forwards and the early disclosure, which cost more than the volume break.

Consolidate on your date instead, after the overlap review removes duplicate users, and get a written rate hold on the lower count.

How do you check what each org actually uses?

Start with data both companies already hold. Finish the review before anyone talks numbers with Salesforce.

1. Licenses in each org. Setup, then Company Information, lists every user license and permission set license with total, used and remaining counts.
2. Inactive users. A users report with the last login date shows who has not logged in for a set period. Frozen users still consume a license; deactivated users release theirs.
3. Duplicate people. Match users across the two orgs by email or employee ID. After a merger, sales and service staff often hold a seat in both.
4. Process overlap. Compare custom objects, installed packages and connected apps. Heavy overlap favors consolidation; very different processes favor coexistence.
5. Contract data. Pull every order form, amendment and renewal quote for both companies, and record the term end date and notice window for each.

What does a divestiture need that a merger does not?

A transition services clause, agreed before the deal is announced. The separating business needs continued access to Salesforce on terms that no one is under time pressure to accept, and the seller needs a clear end date for supporting it.

Regulatory review adds a constraint. Under the premerger notification program, parties to a reportable US deal generally wait 30 days after complete filings before closing, and hold separate obligations can limit integration while the review runs. Plans that assume the two orgs merge on day one are wrong on the contract side and on the regulatory side.

Why keep the two orgs separate until close?

In many deals it is a compliance requirement, and in most it is a commercial advantage. Two contracts that have not been merged can still be renegotiated separately. Sharing each company's Salesforce pricing across the deal line before close can also raise antitrust questions.

The contract adds its own limit. The standard MSA treats order form terms and pricing as confidential, disclosable without Salesforce's written consent only to affiliates, legal counsel and accountants. Before close the buyer is not yet an affiliate, so agree with counsel early how the target's term dates, quantities and notice windows reach the integration team.

What should the transition services clause cover?

• Access. Named users of the divested business keep access for a defined period that matches the transition services agreement term.
• Price. Those users stay at the current contract rate for the full period, with no reprice on the parent's order form.
• Permitted use. After closing, the divested company is no longer an affiliate, and the standard MSA bars using the services for the benefit of anyone other than the customer or its affiliates unless an order form says otherwise. Its staff can still be users as third parties you do business with, but the clause must expressly permit their work for the new owner.
• Data. The standard MSA gives 30 days after termination to request a data export. Ask for a longer window, and plan the org split or data extraction well before the last day.
• New contract. The divested business gets a quote for its own agreement before the transition ends, at a rate agreed in advance.

What contract wording should you ask for?

Ask for terms that protect the sequence you have chosen. Each of these goes into an amendment or the next order form, because only signed paper counts. Our list of ten Salesforce contract clauses covers the ordinary renewal terms in more depth.

• Bridge extension. Extend the earlier contract to the later anniversary at the current rate, with no uplift for the bridge period.
• Rate portability. Where the same product sits on both contracts, the consolidated order form uses the lower of the two per unit rates.
• No forced true forward. Seat additions during the integration period may be deferred to the aligned renewal date, without a mid term reconciliation.
• Partial assignment. The right to assign specific order forms to a divested entity, with consent given in advance.
• Rate hold on reduction. The per unit price stays at the prior rate when the overlap review removes duplicate seats, overriding the standard right to reprice a smaller renewal.
• Renewal cap. A written ceiling on the increase at the first consolidated renewal, applied to the combined order form.
• Notice window. A notice period long enough for a merger team to act, confirmed in writing for every order form. Our renewal notice windows calendar helps track them.

What should happen before and after the deal closes?

Most of the work falls before Salesforce hears about the deal. This is the sequence we run when a client is buying or merging with a Salesforce customer.

What to do next

1. Align the renewals before you disclose combined volume. Doing it the other way round is where most of the avoidable cost came from in our situations.
2. Read the assignment clause in both agreements in week one. An asset deal often needs vendor consent, and consent gives Salesforce something to trade.
3. Refuse a mid term true forward where the contract allows it. Ask for the additions to be deferred to the aligned renewal instead.
4. Negotiate the transition services clause before announcement. On a divestiture, access risk is priced against you once the deal is public.
5. Consolidate at the later anniversary, on evidence. Our Salesforce practice runs the overlap review before the account team is told anything, and our Salesforce M&A advisory covers the full deal cycle.

Frequently asked questions