Salesforce bought Contentful to add a headless content layer to its own platform, connected to its customer data and its Agentforce AI agents. The plan, as described at announcement, is for agents to query and assemble content from Contentful and deliver it across channels, personalised with Salesforce data.
If you already run Salesforce, that could be useful. If you chose Contentful precisely because it was independent of any one marketing or CRM suite, it changes the picture, even if nothing changes in the product this year.
What has not changed
Contentful's APIs, content model and editing interface are the same as they were in the summer. Existing contracts run on their existing terms. There is no public sign so far of forced moves onto Salesforce contracts or broad price rises. That gives customers time to review calmly rather than react.
What to review before renewal
- When your contract renews, and what notice period and price protections it includes
- Where your content is hosted and processed, and whether that still meets your data residency needs
- Which integrations depend on Contentful-specific features, apps or webhooks
- Whether you can export your full content model, entries and assets, and have tested doing so
- Whether deeper Salesforce integration would help you, or is a direction you would rather avoid
Sovereignty is a real question for some
Contentful began in Berlin, and some European public sector and regulated customers chose it partly for that. Drupal's founder, Dries Buytaert, has argued that US ownership brings Contentful under US law, including the CLOUD Act, and that those customers should reassess. For most organisations this will not decide anything. For a few, it will be the main question.
The best time to check you can leave a platform is when you have no plans to.
If you do decide to move
Contentful's structured content model makes leaving easier than leaving a page-based CMS, because the content is already separated from its presentation. The usual destinations are a headless WordPress or Drupal build, which you can host where you choose, or another headless platform. The work is in mapping content types, moving assets and rich text, and rebuilding the integrations and previews editors rely on.
We help organisations review exactly this: what staying would cost, what moving would involve, and what the decision depends on. Sometimes the answer is to stay and simply renegotiate with better information.
