Salesforce bought Contentful. The lock-in just moved up the stack.

The Salesforce Contentful acquisition is being written up as the moment enterprise content finally got intelligent. It is also the moment a lot of enterprises quietly hand one company their data, their content, and the AI that sits on both. Same event. Almost nobody is saying the second half out loud.

Salesforce signed to buy Contentful on June 1 and will fold it into Customer 360 as a native layer its Agentforce agents can assemble from on demand. It closes in Salesforce's fiscal Q3 2027, and more than 4,800 brands run on Contentful, by Salesforce's own count. The coverage has the capability right. It is strangely calm about the cost.

Here is my read. This is the consolidation play the content market already ran a decade ago, heading for the same ending, with one twist that makes this round bite harder.

Adobe and Sitecore already ran this consolidation play

Adobe built its experience suite by shopping: Omniture, Magento, Marketo, Target, all pulled under one roof and one invoice. Sitecore did it faster. After a $1.2 billion raise in early 2021 (reported by MarTech), it spent a year absorbing a customer data platform, a commerce engine, an email tool, and a search product.

Each time, the pitch was seamlessness. Each time, the prize was the layer that decides what every customer sees. A CMS you can replace over a long weekend. The model of your customer and the years tuning it, you do not replace. You move in with it.

Composable content did not end lock-in. It moved it.

Notice what changed. Back then the monolith's pitch was blunt: move in with us, hand over your data, watch us work. Enterprises were the cautious ones, and over a decade they left, going headless and composable for one reason, to stop a single vendor owning everything. They won that argument. So the monolith stopped making it and started buying the winners. Now Salesforce hands you exactly what you left for: headless, composable, API-first, with itself sitting underneath.

That confidence is the weak point. Beat lock-in once and you stop watching for it, which is exactly when it returns.

What Salesforce bought is composable on purpose. Your content sits in structured fields you can export whenever you leave, and Salesforce has promised to keep it that way. Your content is portable. Relax.

That portability is real, and it is a decoy. Moving content was always easy: pull the JSON, map it, go. What you cannot move is what Salesforce is actually building. Agentforce reaching into your unified data and content together, learning what works and deciding what to serve to whom. That intelligence has no export button. The engine that made your content perform stays behind.

So the lock-in did not loosen when content went composable. It moved up a floor, into the agentic layer nobody inspects, while everyone admires how easily the furniture comes out the front door.

The Contentful migration cost nobody puts on the slide: the exit

Discounts on a deal this size are real, and a consultant will walk your steering committee through a slide where the move clearly pays. The slide prices moving in. It never prices moving out. Lock-in does not show on the entry invoice. It arrives years later in two shapes: the premium you pay at every renewal once leaving is unthinkable, and the bill to leave anyway. CloudBees' 2025 DevOps Migration Index (n=300+ enterprise IT leaders) put the average loss on a single platform migration at $315,000, before the months of search ranking you claw back. The discount buys the entrance. The exit is always full price.

What the acquisition does to Contentful data residency, GDPR, and the CLOUD Act

European buyers carry a third bill. Contentful was founded in Berlin and spent a decade as a European choice for teams treating data residency and jurisdiction as non-negotiable. Once this closes, it answers to US ownership and US legal reach, the CLOUD Act included, which can compel a US provider to surrender data wherever it sits. The EU data residency add-on still pins storage to Ireland and Frankfurt, but residency is about where the bytes sit. Jurisdiction is about who can reach them. The acquisition changes the second without touching the first.

Dries Buytaert, Drupal's founder, made the point, and it holds even though he competes with Contentful. Choosing a vendor by passport was never durable, because the passport belongs to the owner, and owners change. One acquisition can rewrite your governance, legal exposure, and compliance position overnight while the product on your screen looks identical. If your sovereignty case rested on where your CMS was born, it expired in an announcement you never got to vote on.

What Contentful customers should do now

None of this argues for fear, or for standing still. Every stack runs on vendors, and concentration pays. The discipline is narrower: never let one company own every layer that matters at once.

• Map your stack by layer: data, content, decisioning, delivery. If one vendor owned all four, what could you still replace inside 90 days?

• Keep the decisioning logic where you can export it. The personalization rules are the asset. Do not let them dissolve into an agent you cannot take with you.

• Running Contentful already? Get answers in writing now, while you are still a customer worth keeping: the twelve-month roadmap, pricing under Salesforce, your residency and compliance certifications, and a documented exit path.

• Price the exit before you sign the entry. If nobody can tell you what leaving will cost, you have found the number that matters most.

• If you are weighing Contentful alternatives, weigh them on independence, not just features. An independent composable platform like Storyblok keeps the content layer separable from whoever owns your data and your agents. We wrote a longer comparison in Storyblok vs Contentful for Enterprise.

A vendor that makes those answers easy is telling you something good. So is one that stalls.

The deal builds something real. Data, content, and agents in one place is power, and for some it will be the right trade made with open eyes. It is also a commitment of the same size, and only the power makes the pitch. The dependence was always going to live one floor up, in the layer that learns on everything you own and answers to one company.

Convenience and captivity look identical right up until you try to leave.

Building the foundation for agentic AI

Structured content is no longer just about the search bar; it is a prerequisite for the future of work. As Gartner projects that 15% of day-to-day work decisions will be made autonomously by AI agents by 2028, these agents will rely entirely on a machine-readable content model.

The search bar already works. To unlock its value, you must fix the content it searches. This foundation determines whether AI delivers ROI today and whether agentic AI can function safely tomorrow.

Frequently asked questions

Trying to work out what this consolidation means for your own stack? Worth pressure-testing the architecture, and pricing the exit, before the next renewal makes the call for you. That is the conversation we have with enterprise teams thinking past the contract in front of them. If that is where you are, let's talk.

Is my Contentful content still portable after the Salesforce acquisition?

Your content sits in structured fields and exports as JSON, and Salesforce has committed to keeping it that way. Portability is not the risk. The decisioning and personalization intelligence built on top of your content is what has no export button.

What happens to Contentful EU data residency under US ownership?

The EU data residency add-on still stores content in Ireland and Frankfurt. What changes is jurisdiction. US ownership brings US legal reach, including the CLOUD Act, which can compel a US provider to surrender data regardless of where it physically sits. Residency and jurisdiction are not the same question.

Will Contentful pricing change under Salesforce?

Nobody can promise it will not. When a focused platform is folded into a suite, renewal pricing tends to rise once leaving becomes unthinkable. Get your pricing terms, lock period, and billing relationship in writing now, while you are still a customer worth keeping.

Should we migrate off Contentful now?

Not reflexively. The discipline is keeping your layers separable, not fleeing the product. Map what you could replace inside 90 days, keep your decisioning logic exportable, and price the exit before the next renewal prices it for you. If you do evaluate a move, see our enterprise CMS replatforming guide and our note on content governance for composable platforms.