Salesforce has not yet acquired Contentful: what to audit before the deal closes

Salesforce signed a definitive agreement to acquire Contentful on 1 June 2026. As of 28 July 2026 the transaction has not closed. That distinction carries most of what a Contentful owner needs to decide this quarter.

Salesforce’s own wording is that the deal “is expected to close in the third quarter of Salesforce’s fiscal year 2027, subject to customary closing conditions, including the receipt of required regulatory approvals.” Salesforce’s fiscal year ends on 31 January, so that quarter runs from 1 August to 31 October 2026. At least one outlet has translated the same sentence into 2027, and several already describe the acquisition as completed. The error matters, because a signed agreement and a closed one put a customer in materially different positions.

Follow-up (23 August 2026): the action plan and dated watch calendar for the open close window.

This piece sets out what the public record establishes, what that record shows can change once an acquisition closes, and a full audit of what leaving Contentful would actually cost you. The conclusion it reaches for most enterprise Contentful owners is to stay put and watch specific things. The audit is worth running anyway, because almost every item in it is work you would want done regardless of who owns your vendor.

The public record as it stands today

No purchase price has been disclosed. The words “purchase price” and “financial terms” appear nowhere in Salesforce’s announcement, and no Salesforce filing with the SEC mentions Contentful at all, including no Item 1.01 filing for entry into a material definitive agreement. For a company of Salesforce’s scale a transaction of this size may simply not meet the materiality threshold that would compel one. The Information reported a range of $1bn to $1.5bn on the day of the announcement, and every other outlet carrying a number attributes it there. Treat it as reported and uncorroborated.

The deal is under active regulatory assessment in at least one jurisdiction. Australia’s competition regulator lists it on its public acquisitions register as case MN-95025, notified on 13 July 2026, at “Phase 1 - initial assessment,” with the end of the determination period recorded as 24 August 2026. In describing the target, the register refers to “digital experience software, specifically, a content management system (CMS).”

Whether filings exist in the EU, Germany, the UK or the United States is not publicly determinable. US premerger filings are not published, UK notification is voluntary, and no European case number has surfaced. Absence of a public record in those jurisdictions establishes nothing in either direction.

Contentful published one customer-facing post, a founders’ letter from co-founder Sascha Konietzke, on the day of the announcement. Its only commitment to customers is a single sentence: “As we begin this journey, Contentful customers remain our top priority. We are fully committed to delivering the same level of innovation, flexibility, and enterprise-grade support customers have come to expect from our team.”

On Contentful’s public marketing site, newsroom, changelog and blog index, there is no acquisition FAQ, no statement on pricing continuity, no statement that existing contracts will be honoured, and no integration timeline. Account teams may well have said more privately to named customers; a briefing delivered through a customer success manager or a support portal would not be visible from outside. If your account team has given you something in writing, it is worth more than anything in this section.

Salesforce’s own forward-looking sentence is that “Following the close of the transaction, Contentful will be integrated natively across Customer 360 while preserving the composability that developers and digital teams expect from a modern headless platform.” The sentence is conditioned on a close that has not happened, and Salesforce published it with no forward-looking-statements caveat attached. Read it as intent.

The interim period constrains what a buyer can do

No merger agreement between Salesforce and Contentful is public, and no premerger filing is public either. Nothing below describes what Salesforce specifically agreed. It describes how transactions of this kind normally work, which is the most that can be responsibly said from outside.

In the ordinary course, a buyer that takes control of a target’s day-to-day business decisions before closing risks what US antitrust agencies call gun jumping. The enforcement record covers the conduct customers tend to worry about, including coordinating on the target’s customer contracts and prices. European regulators reached a comparable conclusion in the Altice case, where veto rights over a target’s pricing were treated as improper early control. This restraint does not depend on the two companies competing with each other, and Salesforce and Contentful are not alleged to compete. It applies because one company does not yet own the other.

Contentful’s pricing, contracts and roadmap are therefore not Salesforce’s to set until the transaction closes. Contentful can still change its own terms on its own initiative, exactly as it always could.

It has, though not on this deal’s clock. Contentful’s published entry-tier pricing has been stable for roughly nineteen months, with the Lite plan holding at $300 per month across archived captures from December 2024 through July 2026. Entitlements have moved in both directions since January 2024. The free plan went from five users to ten while dropping from four included roles to two, and the paid entry tier went from four roles and four locales to three of each, in the same change that renamed it from Basic to Lite, well before the acquisition was announced.

Neither of those entitlement changes was ever announced in the changelog. The changelog is a record of features, and the pricing page and the contractually incorporated usage-limits page are the surfaces where entitlements actually move. All of those examples also sit on the free and entry tiers, which limits what they tell an enterprise reader.

Salesforce’s record with the products it acquires

Salesforce publishes a Product & Feature Retirement Philosophy. It commits to “written notice to system administrators with sufficient time before the product or feature is retired,” sets no fixed notice period, and reserves the right to change the policy at any time, including “decreases in the length of the notice and/or support periods described above,” with changes effective 30 days after posting. That document is the answer to what Salesforce would owe you later, and it is weaker than most buyers assume.

Salesforce has retired acquired products. Social Studio, which descended from the Radian6 and Buddy Media acquisitions, was retired on 18 November 2024, with customer data deleted 90 days after. Audience Studio, formerly Krux, was retired on 1 February 2024; Salesforce offered affected customers a swap into other eligible Salesforce products for the remainder of their subscription, subject to additional terms. Quip is in a defined wind-down announced in early 2026, closed to new customers since 17 February 2026, with Salesforce stating that subscriptions will not be renewable after 1 March 2027 and free users losing access at the end of March 2027, giving roughly thirteen months of notice. Salesforce framed that one as a decision to “reimagine the most common Quip use cases in Slack, Agentforce Sales, and the rest of our product portfolio.”

Those three cases share a feature that limits how far they travel. A social listening tool, a data management platform and a documents app are all products whose whole category moved on. None of them is a developer platform with an API contract underneath it, which is the thing a Contentful owner is actually asking about.

On that question the record is more reassuring. Tableau closed on 1 August 2019, still carries its own brand nearly seven years later, and shipped Tableau Next to general availability in April 2025. Heroku shipped Fir to general availability in April 2025 and AppLink that July. MuleSoft, acquired in 2018, appears on neither of Salesforce’s retirement registers eight years on, though it is not a nothing-changed case either: Anypoint Platform is sold today as Integration Starter and Integration Advanced packages “charged on a subscription basis and measured by the amount of Mule Flow and Mule Message capacity needed,” which is a usage-metered model. Salesforce completed its acquisition of Informatica in November 2025, so this is a company still buying and building platforms.

Pricing has moved on acquired products, on no reliable clock. Salesforce raised list prices an average of 9% in 2023, four years after acquiring Tableau, and named Tableau explicitly among the affected products. A separate announcement in June 2025 raised list prices an average of 6% on selected clouds; Tableau was not named in that one. Slack, acquired in 2021, was repriced in 2022 and again in June 2025, when Business+ went from $12.50 to $15 per user per month. Heroku’s free plans were removed in 2022, roughly eleven years after that acquisition. Three cases spanning about one to eleven years is a spread, not a base rate, and nobody can honestly tell you which end of it Contentful sits at.

These are list price changes. Salesforce’s 2023 announcement described the increase as being in effect for new customers and existing customers purchasing new clouds, and said nothing about pricing at renewal for existing subscriptions. If you hold a multi-year Service Order, a list movement is an input to your next negotiation.

In February 2026 Heroku announced a shift to “a sustaining engineering model focused on stability, security, reliability, and support,” describing itself as remaining “an actively supported, production-ready platform” with the emphasis on operational excellence over new features. Enterprise contracts stopped being offered to new customers, while existing subscriptions “will continue to be fully honored and may renew as usual.” Heroku is not on either of Salesforce’s retirement registers. That middle state, supported and maintained while the new work goes elsewhere, is the outcome most worth watching for.

The audit worth running now

What follows is a dependency and contract audit in six phases. It is a set of things to count and read, and running it commits you to nothing. Phase 1 is a morning of reading; Phases 2 to 5 scale with the size of your estate; Phase 6 prices staying, which is the likelier outcome.

Nothing in this section is legal advice. The contractual mechanics described are general, and your own agreement governs.

Phase 1 — Establish what governs you

Everything downstream is scoped by this, so do it first.

1. Identify your contracting entity. Contentful Inc. and Contentful GmbH sit under different governing law. Contentful’s published terms put GmbH agreements, covering customers in Europe, the UK, the Middle East, Africa and Asia, under the laws of England and Wales, and Inc. agreements under Delaware law. Analysis written for one does not carry to the other, which is worth knowing before you read anything else published about this deal.

2. Determine whether you are on the published terms or a negotiated agreement. Contentful states that which applies depends on your tier. On an enterprise agreement, nothing published on the website is authoritative for you, and the rest of this audit becomes a set of questions to ask of your own document.

3. Read your change-of-control and assignment clauses. There are two patterns worth looking for: an anti-assignment clause that treats a change of control as an assignment requiring your consent, and a standalone change-of-control termination right. Contentful’s published terms contain neither.

4. Pull your Service Order and compare it to the published limits. Contentful states in two places that the Service Order takes precedence, over both the technical-limits page and the contractually incorporated usage-limits page.

5. Locate your renewal date and your notice-to-non-renew period, and place both against 1 August to 31 October 2026. AT&T held pre-acquisition terms through the Broadcom–VMware transaction and still ended up litigating over a claimed 1,050% increase, so a renewal date is not full protection. Work backwards from your notice deadline, commonly 60 to 90 days before renewal, put that date in a calendar with a named owner, and decide before it what you will ask for.

6. Check whether you have a signed EU Data Act Addendum. Contentful publishes it for signature and pre-incorporates it into GmbH contract templates. It defines a switching process with actual numbers attached, set out in Phase 5 below. Without it, the only published post-termination number is the data processing addendum’s commitment to delete all customer content within 35 days of a written request, which is a deletion obligation rather than a retrieval right. If you are on Contentful Inc. paper without the addendum, signing it closes that gap without a migration, and that is the cheapest item on this list by a wide margin.

Phase 2 — Measure what would have to move

Contentful’s contractual export register enumerates roughly twenty-five categories of customer data and states which are exportable. Seven of them come out through the standard space export: entries, assets, the content model, tags, locales, webhooks and roles. The contentful-export tool’s own README lists eight, adding editor interfaces, which is a live inconsistency between two Contentful documents and worth resolving with your account team before relying on either number.

Contentful’s import and export documentation is specific about what does not survive the round trip. Version history starts fresh on import. Scheduled releases, tasks and workflows are not carried and must be scripted afterwards. Custom apps and UI extensions must be reinstalled manually. Webhook credentials are stripped, and author attribution is recreated under whichever token ran the import. Contentful separately lists categories it will not export at all, among them SSO configuration, audit log configuration, the GraphQL schema registry, vectorized content, and personal and API tokens.

These are the limits of Contentful’s own tooling moving content between spaces, so the same gaps appear in a space-to-space move inside Contentful, and they are not exit penalties invented for people who leave. Nothing in Contentful’s documentation states whether entry and asset identifiers survive an export and re-import, so do not assume they do without testing it.

Then count the things that determine effort:

• Content types, fields and records. Published ceilings for scale reference are 1,000 content types per environment, 50 fields per type, and 5,000,000 records per space.
• Locales and fallback chains. The fallbackCode can only be read or set through the API, so a UI-only audit will miss it. Note your default locale as well; it is permanent and cannot be changed.
• Rich text density and reference depth. Rich Text is a Contentful-specific JSON structure with embedded entries stored as references and resolved separately, so every rich-text field is re-render work wherever it lands. Ceilings are 200,000 characters or 1MB per field, and 1,000 total links across all fields of an entry.
• Configuration objects the export does not carry, counted individually: scheduled actions, workflows, releases, tasks, comments, app installations and app definitions, and webhooks.
• Compose usage. Compose is deprecated and in maintenance mode, with current installations documented to work until the end of 2026. That is a dated decision you owe yourself regardless of what Salesforce does. Launch is not deprecated, and the two are easy to confuse.
• Studio Experiences and Personalization. Studio experiences are entries backed by an auto-generated content type, and the design components they reference live in your codebase, so the layout tree exports as JSON that is only meaningful to Contentful’s SDK.
• Your editorial operation, as distinct from your content. Count editors, the workflows they run daily, and the approval chains behind them. None of that is in an export file, and for a team of any size the retraining and workflow-parity cost is a larger switching cost than the API arithmetic in Phase 4.

Phase 3 — Find the coupling that lives outside Contentful

None of the coupling below appears in the Contentful UI. Each item is a grep or an API call against your own estate.

• Grep the whole estate for ctfassets.net. Asset URLs default to that domain, and every one that has leaked into content bodies, email templates, feeds, PIM records or partner systems is a hard dependency. If you have the custom domain entitlement, this looks different for you, so check that first.
• Grep for CRN identifiers in the crn:contentful:::content:spaces/... form. Cross-space references embed Contentful space and environment identity directly into stored content.
• Audit your GraphQL layer for Contentful’s naming transform. Type names are derived from content type IDs by a specific transformation, with prefixed collision handling, so every query is coupled to that mapping and not only to your field names. Rich text arrives as JSON plus a separate links sub-tree that has to be stitched back together.
• Audit your link-resolution assumptions. The Content Delivery API returns linked entries and assets in a separate includes array, with depth defaulting to one and capping at ten. Any replacement either reproduces that or pushes the work into your front end.
• Count the preview path separately. The Preview API is a distinct host with its own token, and production tokens do not work against it.
• List every third-party integration touching Contentful. Contentful’s EU Data Act Addendum states plainly that it “is not responsible for Switching or deleting any data that exists in third party integrations with the Subscription Services, including Customer Applications.” Each integration is your own workstream. If you run a translation management system against several locales, treat that connector as its own line: per-locale publishing state and locale-scoped workflow are where these integrations bind tightest, and none of it is in the export.

Phase 4 — Price the extraction

Three published limits make the estimate arithmetic. The Content Management API is rate limited to 10 requests per second per space on paid plans, and that is the binding throughput constraint on any per-resource extraction. Bulk entry export is capped at 10,000 entries per job. Signed asset download URLs expire after one hour and are re-signed on each request, so an asset pull has to be orchestrated rather than queued up front. Divide your record and asset counts by those numbers and you have a defensible window.

Check the rate limit against your own Service Order before you rely on it. The same precedence rule that governs your entitlements governs this number, and a negotiated agreement may raise it, which moves the estimate by an order of magnitude.

If you are on EU data residency, point any tooling at the EU hosts rather than the defaults, or the extraction will quietly target the wrong region.

An extraction estimate is half a migration estimate. The other half is the rebuild on the far side: re-rendering every rich-text field, reproducing link resolution and preview, rebuilding roles, and retraining editors. This audit does not size that, and any number that prices only the exit will make a move look cheaper than it is, whichever platform you land on.

Phase 5 — Model the exit clock and the standing hygiene

The exit clock below is published, dated and billable, and it is the figure that turns optionality into a line item. It applies where the EU Data Act Addendum is in place, which means pre-incorporated for Contentful GmbH customers and signed for everyone else.

The addendum defines three periods and chains them. The Maximum Notice Period is “two (2) months commencing from Contentful’s receipt of a request” to switch. The Maximum Transitional Period is “thirty (30) calendar days, to be initiated after the Maximum Notice Period.” The Retrieval Period is “at least thirty (30) calendar days, starting after the termination of the Maximum Transitional Period.” The addendum then states that “during the entirety of the Maximum Notice Period, Maximum Transitional Period, and Retrieval Period, the Customer is responsible for payment of then-current fees,” with the provisioning document auto-renewing if it expires mid-sequence. Run end to end, that is roughly four months of billed switching before any of it is finished.

Two things stretch it. Where Contentful judges the 30-day transitional period technically unfeasible, it may indicate “an alternative transitional period, which shall not exceed seven (7) months,” which pushes the sequence past ten. And there is no published ceiling at all: the addendum allows further extension where Contentful’s questions to you or your new provider go unanswered within 14 business days, and your own one-time extension right runs “for a period that the Customer reasonably considers more appropriate for its own purposes.” Put the four months in the plan and the absent ceiling in the risk register.

Terminating mid-term for reasons other than Contentful’s uncured material breach obliges payment of the remaining provisioning document fees with no refund, and Contentful expressly states that this is not a switching charge.

Contentful’s terms put the backup obligation on the customer, requiring you to “back up any data and information used in conjunction with the Subscription Services separately and at regular intervals,” and no retention window, recovery objective or restore commitment appears in the published terms. A negotiated agreement may carry service levels that the published pages do not, so check yours before assuming the gap is real. If you do not have a scheduled export running into your own storage, that is a gap in your disaster recovery position that has nothing to do with Salesforce. And if you are on a self-serve plan rather than an enterprise agreement, understand what cancellation drops you into, because the free tier’s ceilings are far below a production estate and what happens to over-limit content is not documented.

Phase 6 — Price the stay

Phases 2 to 5 price leaving. The more likely outcome is that you stay, and that position is worth costing with the same discipline.

• Measure current utilisation against your entitlements. Records, API calls, environments, spaces, users and locales, each against what the Service Order actually grants. Over-provisioning is the most common finding and the easiest thing to trade at renewal.
• Decide what you would ask for. Multi-year commitment has a price, and so does the certainty a vendor wants during a pending acquisition. Entitlement headroom, a rate-limit uplift, service levels, a change-of-control provision on your next renewal, and a contractual export commitment are all askable, and the last two directly retire items from Phase 1.
• Name an executive sponsor on both sides, and establish whether yours survives the close. Continuity of relationship is the thing most likely to change quietly.
• Write down what would have to be true for you to stay for three more years. That list is more useful than a migration estimate, because it converts into renewal asks rather than a project.
• Put the integration question to your account team in writing. Salesforce’s stated intent is native integration across Customer 360; what an enterprise owner needs to know is narrower. Ask whether the Content Delivery and Management API contracts change, whether identity or SSO is remapped, and whether the organisation and space hierarchy is restructured. Nothing public answers those, and a written answer from your account team is worth more than any analysis.

Stay, monitor, or assess

Each posture below is defined by conditions you can observe.

Stay, and the evidence behind it

Stay applies when your renewal falls outside the close window and the notice period preceding it, and your Phase 2 audit surfaces no dependence on the categories Contentful documents as non-exportable.

The observable case is strong. Contentful published 34 changelog entries between March and July 2026, with releases continuing through June and July after the announcement. Those releases are enterprise governance work: bulk entry operations through the Content Management API in June, a remote MCP server moved to general availability at no charge in July, a new Optimization SDK family for customers with a Personalization licence, and support for up to five independent SSO configurations in a single enterprise organisation. Contentful posted two engineering manager roles for the Content API, the core of the platform, in June and July after the announcement. Its leadership page lists eleven executives with no advertised vacancies, and the most recent appointment predates the announcement by fourteen months. Every governing legal document still carries a pre-June-2026 effective date.

Four surfaces worth watching

All four are public and dated.

• The ACCC acquisitions register, for any change from Phase 1 before 24 August 2026.
• Salesforce’s SEC filings. A closing 8-K is the definitive signal. The Q2 FY2027 10-Q, expected on Salesforce’s usual filing pattern in late August or early September, is the next periodic filing that could disclose consideration.
• Contentful’s pricing and usage-limits pages, diffed against today, because that is where entitlements have historically moved without an announcement.
• Salesforce’s product retirement registers, active and past. Any Contentful entry appearing on the active register is the highest-signal event available, and Salesforce’s own Retirement Philosophy is the document that tells you how much notice that entry would come with.

Base rates are worth holding alongside all of this. If the reported price is in the right range, the relevant band is $1bn to $10bn, where second requests ran to 16 of 599 filings in the US agencies’ most recent published year, and enforcement actions ran below 1% of reported transactions. The overwhelmingly likely outcome is that this deal completes roughly on the stated schedule. Treat monitoring as a way to confirm timing and prepare for it.

Give the contract audit to whoever owns the Contentful relationship, with the output due before 24 August: a one-page answer to the six items in Phase 1.

When assessing is warranted

Move to assess when one of these is true:

• Your renewal or its notice deadline falls inside 1 August to 31 October 2026, or in the quarter following it.
• You are on Contentful Inc. paper with no signed EU Data Act Addendum, which leaves you with a deletion commitment and no published retrieval right. Sign the addendum first; it may resolve the condition entirely.
• Your Phase 2 count shows material dependence on specific documented gaps: version history, scheduled releases, tasks and workflows, custom apps and UI extensions, author attribution, SSO configuration, or the GraphQL schema registry.
• You are Compose-dependent, in which case the end-of-2026 date forces a decision on its own timetable.
• Your content pipeline feeds a direct Salesforce competitor, which makes a stated intent to integrate natively across Customer 360 a genuine architectural consideration.

Assessing means pricing the alternative accurately enough that the option is real, using the Phase 4 arithmetic. The documented advisory posture from analysts covering acquired vendors is to trim and price optionality while evaluating.

The terms that decide your position are in your own paper

Section 10.4 of Contentful’s published terms carves out assignment to a successor without customer consent, and the only change-of-control provision in the document runs the other way, permitting Contentful to terminate or suspend if the customer undergoes one. That asymmetry is ordinary commercial drafting, and it was in the document before 1 June. For enterprise customers it may not even be the operative language, because the Service Order and the negotiated agreement take precedence over everything published. Pull them, answer the six items in Phase 1 against them, and you will know your position on this deal better than any coverage of it can tell you.

How WAYF can help

WAYF builds and runs enterprise content platforms and is an official Payload partner, which is worth stating before you read WAYF’s comparison of Contentful and Payload. Ingersoll Rand moved its China sites off Oracle Content Manager in five months, with WAYF on Payload, so migrations are work WAYF does.

Most Contentful owners reading this should not migrate. Two things would help more than a migration: running the audit above with your team so the numbers are yours, and standing up the scheduled export that Contentful’s own terms already make your responsibility. Where a team stays on Contentful and wants the platform around it to work harder, that is work WAYF does too. Book a call if any of that would help; scoping and a fixed price come after. If a move ever does make sense, the mechanics are written up in full in the Contentful migration reference.

FAQ

Has Salesforce acquired Contentful? Not yet. Salesforce signed a definitive agreement on 1 June 2026 and expects to close in the third quarter of its fiscal year 2027, which runs from 1 August to 31 October 2026. As of 28 July 2026 the deal remains under regulatory assessment in Australia, with the determination period running to 24 August 2026, and Salesforce has filed no closing notice. Coverage describing the acquisition as completed is inaccurate.

How much is Salesforce paying for Contentful? Neither company has disclosed a price. The Information reported a range of $1bn to $1.5bn on 1 June 2026, and other outlets carrying a figure attribute it to that report. No SEC filing corroborates it.

Can Salesforce change Contentful’s pricing before the deal closes? Not on Salesforce’s instruction. In transactions of this kind, a buyer that directs the target’s ordinary-course decisions, including pricing and customer contracts, risks gun-jumping liability under US and EU merger control. No merger agreement or premerger filing in this deal is public, so this describes normal practice rather than anything Salesforce specifically agreed. Contentful can still change its own terms independently. Its published free and entry-tier entitlements have moved in both directions since January 2024 without appearing in the changelog, which says little about enterprise agreements but does tell you which page to diff.

Does the acquisition give us the right to terminate our contract? Contentful’s published terms do not grant one. They allow assignment to a successor without customer consent, and the only change-of-control provision permits Contentful to terminate if the customer changes control. Enterprise customers are typically on a negotiated agreement whose terms may differ, which is why the audit starts with your own document.

What would it cost us to leave, in time and money? Where Contentful’s EU Data Act Addendum applies, it chains a two-month notice period, a 30-day transitional period and a retrieval period of at least 30 days, and states that the customer pays then-current fees throughout all three. That is roughly four months of billed switching before any engineering effort. Contentful may substitute a transitional period of up to seven months where it judges 30 days technically unfeasible, which pushes the same clock past ten, and there is no published ceiling. Without that addendum in place, the only published post-termination number is a commitment to delete content within 35 days of a written request.

What does Contentful’s export not carry? Seven of roughly twenty-five enumerated data categories come out through the standard space export: entries, assets, content model, tags, locales, webhooks and roles. Version history starts fresh, scheduled releases and workflows must be scripted separately, custom apps and UI extensions must be reinstalled manually, webhook credentials are stripped, and author attribution is recreated under the importing token. SSO configuration, audit log configuration and the GraphQL schema registry are listed as not exportable. The same limits apply to moves between spaces inside Contentful.

Has Contentful stopped shipping since the announcement? No. It published 34 changelog entries between March and July 2026, with releases continuing after the announcement, including bulk entry operations via the Content Management API, a generally available remote MCP server at no charge, and support for five independent SSO configurations per enterprise organisation. It also posted two Content API engineering manager roles after the announcement.

What has Salesforce done with platforms it acquired before? Both things. It retired Social Studio in November 2024 and Audience Studio in February 2024, offering Audience Studio customers a swap into other eligible Salesforce products for the remainder of their subscription, subject to additional terms. Quip is in a wind-down running to March 2027, announced with roughly thirteen months of notice. All three were products whose category had moved on, and none was a developer platform with an API contract underneath it. On that side of the ledger, Salesforce kept the Tableau brand and shipped Tableau Next in April 2025, shipped Heroku Fir and AppLink in 2025, and has never placed MuleSoft on a retirement register eight years after that close, though MuleSoft’s packaging did move to usage-metered Integration tiers. Post-acquisition pricing changes have landed anywhere from about one to eleven years after a close.

Should we migrate off Contentful because of the acquisition? For most organisations, not on this evidence. The proportionate response is the contract and dependency audit above, then watching four public surfaces. Migration is warranted by conditions in your own estate rather than by the announcement.

Verified as of 28 July 2026 against the public documents cited below. Several facts here are time-sensitive, and this piece will be revisited after the Australian determination period ends on 24 August 2026.

Sources

The transaction

• Salesforce, Salesforce Signs Definitive Agreement to Acquire Contentful (1 June 2026): https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-contentful/
• Contentful, A New Chapter for Contentful: Scaling Our Vision with Salesforce (1 June 2026): https://www.contentful.com/blog/a-new-chapter-for-contentful/
• ACCC, Acquisitions register — Salesforce / Contentful, case MN-95025: https://www.accc.gov.au/public-registers/mergers-and-acquisitions-registers/acquisitions-register/salesforce-contentful
• Salesforce, fiscal year definition, Form 10-Q for the quarter ended 30 April 2026: https://www.sec.gov/Archives/edgar/data/1108524/000110852426000127/crm-20260430.htm
• US Federal Trade Commission, Premerger notification and the merger review process: https://www.ftc.gov/advice-guidance/competition-guidance/guide-antitrust-laws/mergers/premerger-notification-merger-review-process

Contentful’s contractual and technical surface

• Contentful, Terms of Service: https://www.contentful.com/legal/terms-of-service/
• Contentful, EU Data Act Addendum: https://www.contentful.com/legal/eu-data-act-addendum/
• Contentful, Data Processing Addendum for Customers: https://www.contentful.com/legal/privacy-and-data-protection/data-processing-addendum-for-customers/
• Contentful, Usage limits: https://www.contentful.com/help/admin/usage/usage-limit/
• Contentful, Data export register: https://www.contentful.com/help/admin/data-export/
• Contentful, Import and export with the CLI: https://www.contentful.com/developers/docs/tutorials/cli/import-and-export/
• Contentful, Technical limits: https://www.contentful.com/developers/docs/platform/technical-limits/
• Contentful, Pricing: https://www.contentful.com/pricing/
• Contentful, Developer changelog: https://www.contentful.com/developers/changelog/
• Contentful, Leadership: https://www.contentful.com/leadership/

Salesforce’s record with acquired products

• Salesforce, Product & Feature Retirement Philosophy: https://help.salesforce.com/s/articleView?id=000335954&type=1&language=en_US
• Salesforce, active product retirements register: https://help.salesforce.com/s/articleView?id=000381744&language=en_US&type=1
• Salesforce, past product retirements register: https://help.salesforce.com/s/articleView?id=005132112&type=1&language=en_US
• Salesforce, Winter ‘25 Release Notes, Social Studio retirement 18 November 2024: https://resources.docs.salesforce.com/252/latest/en-us/sfdc/pdf/salesforce_winter25_release_notes.pdf
• Salesforce, Audience Studio retirement, 1 February 2024: https://help.salesforce.com/s/articleView?id=000879892&language=en_US&type=1
• Salesforce, Quip retirement plan: https://help.salesforce.com/s/articleView?id=005299603&language=en_US&type=1
• Salesforce, MuleSoft Anypoint Platform pricing: https://www.salesforce.com/mulesoft/anypoint-platform/pricing/
• Salesforce, 2023 pricing update (archived; the live URL now redirects): https://web.archive.org/web/20230726122345/https://www.salesforce.com/news/stories/pricing-update/
• Salesforce, 2025 pricing update (17 June 2025): https://www.salesforce.com/news/stories/pricing-update-2025/
• Slack, June 2025 pricing and packaging announcement: https://slack.com/blog/news/june-2025-pricing-and-packaging-announcement
• Heroku, Heroku’s Next Chapter, free plan removal (25 August 2022): https://blog.heroku.com/next-chapter
• Heroku, An update on Heroku, sustaining engineering model (6 February 2026): https://www.heroku.com/blog/an-update-on-heroku/
• Heroku, Fir general availability changelog item: https://devcenter.heroku.com/changelog-items/3188
• Salesforce, Tableau Next general availability (15 April 2025): https://www.salesforce.com/news/stories/tableau-next-announcement/
• Informatica, Salesforce Completes Acquisition of Informatica (18 November 2025): https://www.informatica.com/about-us/news/news-releases/2025/11/20251118-salesforce-completes-acquisition-of-informatica.html