Contentful and Salesforce: what to do while the deal is open

Salesforce signed a definitive agreement to acquire Contentful on 1 June 2026. As of 23 August 2026 the transaction has not closed. Salesforce’s stated expectation is a close in the third quarter of its fiscal year 2027, which runs from 1 August to 31 October 2026, subject to regulatory approvals. That window is open now.

We published a full audit of the situation in late July: the public record, what a buyer can and cannot do before closing, Salesforce’s dated record with acquired products, and a six-phase exit-cost audit. Its conclusion stands, and most enterprise Contentful owners should stay and watch specific things. This piece is the shorter companion for the weeks the window is open: what to do, in what order, against which dates.

This week: pull your own paper

Everything that decides your position in this deal is already in documents you hold. The coverage cannot tell you your renewal date; your Service Order can.

• Answer the six contract items from Phase 1 of the audit against your Service Order and negotiated agreement, and give the job to whoever owns the Contentful relationship. The output is one page: renewal date, notice deadline, term, price protections, assignment and change-of-control language, and which entity’s paper you are on. Contentful’s published terms permit assignment to a successor without customer consent, and enterprise agreements take precedence over everything published, so what yours says is the fact that matters.
• If you are on Contentful Inc. paper without a signed EU Data Act Addendum, sign it. It converts a deletion commitment into a retrieval right, and it may settle the exit question on its own.
• Put your renewal date against the window. A renewal or notice deadline falling inside 1 August to 31 October 2026, or the quarter after it, is the single condition that moves you from watching to assessing.

This month: know what would have to move

None of this commits you to anything, and all of it is work worth having done under any owner.

• Run the export dry-run. Pull a full space export through the APIs and count what does not come with you. The documented gaps are specific: version history, scheduled releases, tasks and workflows, custom apps and UI extensions, author attribution, SSO configuration, the GraphQL schema registry. Material dependence on any of them changes your exit price, and you want that number while it is a planning input rather than a deadline.
• Map the coupling outside Contentful. Front ends, middleware, personalisation, search, and preview flows that assume Contentful’s APIs are where migration cost actually lives; the Phase 3 and 4 arithmetic in the audit walks the pricing.
• Diff the pricing and usage-limits pages against today. Entitlements have historically moved on those pages without an announcement, and a saved copy from this month is the baseline that makes any later change visible.

The calendar to 31 October

The useful signals are public and dated. Between now and the end of the window:

• Salesforce’s SEC filings. A closing 8-K is the definitive close signal. The Q2 FY2027 10-Q, expected on Salesforce’s usual pattern in late August or early September, is the next periodic filing that could disclose consideration.
• Australia’s ACCC register, where the deal is listed under active Phase 1 assessment with the determination period recorded to 24 August 2026 — the first dated regulatory checkpoint of the window.
• Salesforce’s product retirement registers. A Contentful entry appearing on the active register would be the highest-signal event available, and Salesforce’s own Retirement Philosophy defines how much notice it would carry. Nothing of the kind exists today.
• Contentful’s pricing pages, against the baseline you saved above.

Until the close, the ordinary interim-period rules apply: Contentful’s pricing, contracts and roadmap remain its own to set, and a buyer that reached into them early would be inviting the gun-jumping enforcement the audit describes. Price and packaging changes before close would be Contentful’s initiative, exactly as they always could have been.

Stay or assess

The audit’s postures, condensed to their conditions:

Stay when your renewal sits outside the window and its notice period, and your export dry-run shows no material dependence on the non-exportable categories. The observable evidence supports it: Contentful kept shipping enterprise governance work after the announcement and continued hiring for the core Content API.

Assess when any of these is true: your renewal or notice deadline falls inside the window or the quarter after it; you are Compose-dependent, whose end-of-2026 date forces a decision on its own timetable; your gap count shows material dependence on the documented non-exportables; or your content pipeline feeds a direct Salesforce competitor, which makes the stated intent to integrate Contentful “natively across Customer 360” an architectural consideration rather than a headline.

Assessing means pricing the alternative accurately enough that the option is real. It is a quote and a plan, and having one changes your renewal negotiation whether or not you ever use it.

If the assessment says move

A Contentful to Payload move is a transfer between two structured systems: content models map to typed collections, entries move through APIs, and the work concentrates in the coupling outside the CMS. Our migration guide covers the field mapping, export, import, and cutover in detail, and the /migrate/contentful page is where to tell us what you are running — a free consultation and a scoped, fixed quote come before any commitment, so pricing the option costs you a conversation.

The honest base rate from the audit bears repeating: the overwhelmingly likely outcome is that this deal completes roughly on schedule, and the majority of Contentful owners will be best served by staying on a platform they have already made work. The point of the window is that it is the cheapest time you will ever have to find out which group you are in.

FAQ

Has Salesforce completed the Contentful acquisition? No. The agreement was signed on 1 June 2026; as of 23 August 2026 no close has been announced. Salesforce expects the close in its fiscal Q3 2027, which is 1 August to 31 October 2026, subject to regulatory approvals.

Can prices change before the deal closes? Contentful can change its own terms on its own initiative, exactly as before the agreement. Salesforce cannot set Contentful’s pricing until it owns the company; premature control is what regulators call gun jumping. Historically, Contentful entitlement changes have appeared on its pricing and usage-limits pages without an announcement, which is why a saved baseline of those pages is worth keeping.

Do I need to decide anything before the close? Only if your renewal or its notice deadline falls inside the close window or the quarter after it. Everyone else’s work before the close is inventory: contract terms, an export dry-run, and a saved pricing baseline.

What is the single highest signal to watch? A Contentful entry on Salesforce’s active product retirement register. It does not exist today, and Salesforce’s Retirement Philosophy governs how much notice such an entry would carry. The definitive close signal is a Salesforce 8-K filing.

Sources

• Salesforce, Salesforce Signs Definitive Agreement to Acquire Contentful (1 June 2026)
• Contentful, A New Chapter for Contentful (1 June 2026)
• WAYF, Salesforce has not yet acquired Contentful: what to audit before the deal closes (28 July 2026) — the full public-record review, the six-phase audit, and the sources behind every claim condensed here