Salesforce has closed the Contentful acquisition: what changes today

Salesforce completed its acquisition of Contentful on 1 September 2026. As of 3 September 2026 no closing 8-K had been filed to record it; the last 8-K Salesforce filed before the close, on 26 August 2026, covered its Q2 FY2027 earnings (items 2.02 and 9.01), and no Item 1.01 8-K was ever filed for this transaction. The filing that records the completion is Salesforce’s Form S-8, filed 1 September 2026, which states: “On September 1, 2026, the Company completed the acquisition of Contentful pursuant to the Merger Agreement.” The Merger Agreement itself was entered on 29 May 2026; 1 June 2026 was the day Salesforce announced it. The close lands inside the window Salesforce guided from the start — its fiscal Q3 2027, 1 August to 31 October 2026.

The consideration is approximately $1.5 billion in cash, net of the value of shares already owned by Salesforce, subject to customary purchase price adjustments, as disclosed in Salesforce’s 10-Q for the quarter ended 31 July 2026, filed 27 August 2026, which described the transaction as then pending.

We published a full audit of the situation in July and an action plan for the open window in August. Both were written for this moment: the audit’s postures and the checklist items below assume a close and say what to do when it arrives. This piece covers what the close itself changes.

What changed at close

Through the pending period, Contentful set its own prices, contracts, and roadmap; a buyer reaching into them early is what regulators call gun jumping, and the interim rules kept the companies at arm’s length. That period is over. Salesforce now owns those decisions.

Concretely, three things are new today:

• Roadmap authority. Salesforce’s stated intent — integrating Contentful “natively across Customer 360” — moves from announcement language to something an owner can execute.
• Packaging and pricing for new terms. New deals and renewals are now written by a Salesforce company. Existing terms run as signed.
• The watch items switch registers. Pre-close, the signal worth watching was the SEC docket. Post-close, it is Salesforce’s active product retirement register — where a Contentful entry, if one ever appears, would carry the notice periods of Salesforce’s published Retirement Philosophy. No such entry exists at close.

What did not change

Your contract. The close transfers ownership of the company, not the terms you signed. Entitlements, prices, support commitments, and the EU Data Act Addendum (if you signed one) govern as written until your term ends. Contentful’s published assignment language permitted transfer to a successor without customer consent, and that transfer has now happened. What your own paper says decides your position.

The product also did not change today. The documented export surfaces, the API, and the documented non-exportables (version history, scheduled releases, tasks and workflows, custom apps, author attribution, SSO configuration, the GraphQL schema registry) are what they were last week.

Five checks worth running this week

1. Put your renewal date against the next two quarters. A renewal or notice-to-non-renew deadline in that window is the one condition that moves you from watching to assessing. Everyone else has time.
2. Diff the pricing and usage-limits pages against your saved baseline. If you saved copies during the open window per the action plan, this is the week they start earning their keep. Entitlement changes have historically appeared on those pages without an announcement.
3. Check the retirement registers once, then calendar it monthly. The active register is the highest-signal surface that exists for acquired Salesforce products.
4. Re-date the Compose deadline. Compose’s end-of-2026 date was set before the close and is unaffected by it; Compose-dependent teams are on that clock regardless of the acquisition.
5. If you never ran the export dry-run, run it now. The gap count between what the APIs return and what your team depends on is your exit price, and you want it as a planning input while nothing is urgent.

Our read

The likely outcome was always that this deal completes and most Contentful owners stay. That has not changed with the close. The open questions are now about execution: the pace of integration, what packaging looks like at renewal, and how long the current product surface holds still. Each of those shows up on a dated public surface, which is what the checks above track.

For the platform decision, compare Contentful and Payload against your hosting, editorial, and engineering requirements.

Where the assessment says move, migrating from Contentful to Payload is the technical reference, and /migrate/contentful is where to tell us what you are running. A free consultation and a scoped, fixed quote come before any commitment. Read about our CMS migration service, or talk through your assessment with us.

FAQ

What changes for Contentful customers now that the deal has closed? Ownership and direction. Salesforce now sets Contentful’s roadmap, packaging, and pricing for new terms — the gun-jumping constraints that applied while the deal was pending have ended. Your existing contract is unchanged by the close itself: current entitlements, prices, and terms run as written until renewal or amendment.

Can Salesforce change my Contentful pricing immediately? Not inside a signed term. Your Service Order governs until it expires or you agree to new terms. What the close changes is who decides what renewal looks like — which is why the renewal date and the notice-to-non-renew deadline in your own paperwork are the facts that matter this week.

Is Contentful going to be retired? No such signal exists at close. The definitive indicator would be a Contentful entry on Salesforce’s active product retirement register, which carries notice periods under Salesforce’s published Retirement Philosophy. Watching that register is now a standing item; treating retirement as inevitable is not supported by the record.

Should we migrate off Contentful now? The pre-close base rate still holds: most enterprise Contentful owners are best served by staying on a platform they have made work, and pricing the alternative is what turns staying into a decision rather than a default. Assessment is warranted when your renewal or notice deadline falls within the next two quarters, when you are Compose-dependent, or when your export dry-run shows material dependence on the categories that do not export.

Sources

• Salesforce, Form S-8 registration statement (1 September 2026) — the filing that records the completion; as of 3 September 2026 no closing 8-K had been filed
• Salesforce, Form 10-Q for the quarter ended 31 July 2026 (filed 27 August 2026) — first SEC filing to disclose the consideration, filed while the deal was still pending
• Salesforce, Salesforce Signs Definitive Agreement to Acquire Contentful (1 June 2026)
• WAYF, Salesforce has not yet acquired Contentful: what to audit before the deal closes (28 July 2026)
• WAYF, Contentful and Salesforce: what to do while the deal is open (23 August 2026)
• Salesforce, active product retirements register
• Salesforce, past product retirements register
• Salesforce, Product & Feature Retirement Philosophy