Contentful and Salesforce: the page is not a lead

A campaign is due on Monday. On Friday a project channel says the Salesforce CMS sandbox now contains Contentful, because the acquisition has closed, so the editors should publish only in the CMS. They do. The public site still reads the content platform. Monday morning the campaign URL is blank. The CMS preview looks finished, which makes the blank page harder to believe. In parallel, an administrator exports the entries as a spreadsheet and imports them as leads, because the brief said content migration to Salesforce. The leads are page titles and hero text. Sales calls one of them. There is no person on the other end. Two mistakes, one cause. A content platform was treated as a CRM tenant, and a page was treated as a customer.

Salesforce completed the Contentful acquisition on 1 September 2026. Contentful is a composable content platform. The close does not drop that platform into a CMS sandbox. It does not turn an entry into a lead. The work, if you have any, is to say where a given page is published, who may publish it, and which Salesforce object must not receive a copy of the prose.

#A completion date, not a sandbox feature

The close is one sentence: "Salesforce completed its acquisition of Contentful on September 1, 2026." Read it as a date. 1 September 2026. The sentence does not name your spaces, your content types, or your site. It does not say a Salesforce CMS sandbox now contains Contentful. Do not claim that it does. If a partner's diagram shows the space inside the sandbox, ask them to open the sandbox and show the space. The absence is the finding. You still publish in the product the site reads, until you have a written change to that wiring, tested on a page you can afford to break.

Composable content means the page is assembled from entries of types you defined: a headline, a body, a reference to another entry, a call to action. The assembly can be rendered by a site that is not the CRM. Salesforce can still hold the lead a person submits after they read the page. Those are neighbours. They are not the same record. A headline is not a name. A body is not a company. An import that pretends otherwise fills the CRM with ghosts and empties the page the customer was meant to see.

People will search for a migration because the word Salesforce now sits near the product. The honest scope is often smaller than a migration. Keep the content types. Name the site that reads them. Name the person who publishes. Leave the CRM for facts about people and deals. If you later decide a particular fact on the page must also exist on an account, that is one field, one owner, and one direction. It is not an export of the library.

#What you are not copying

Do not copy entries into leads to satisfy a keyword. A lead is a person you might sell to. An entry is content you might render. Mixing them trains sales to distrust the object, and it trains editors to think the CRM is the preview. When the import is reversed, the page is still blank if you published in the wrong product, and the leads are still junk if you have not deleted them. Undo both. Then write the rule that forbids the import.

Do not assume a full copy of production content exists in a Salesforce sandbox. Even when the CRM sandbox is rich, the content space is a different store. A refresh of the org does not refresh the space, does not publish a draft, and does not point the public site at the sandbox. Editors who test in a sandbox CRM and publish in a live space are testing two environments and calling it one. Name the space the test uses. Name the site the test hits. If either name is production, say so in the test plan before someone publishes a draft to the world.

Do not retire the content types because a CMS object can hold rich text. A long text field on a Salesforce record is a field. It does not give you a preview, a reference between entries, or the publish button the editors already trust. Rebuilding that in the CRM can be a real project if the editors ask for it. The acquisition does not require the rebuild, and a blank Monday is a bad moment to start it. Keep the types. Change the wiring only when the new wiring has rendered the same page.

A document the sales team argues in is a different kind of page again. Do not fold a working draft into a content type because both contain sentences. The neighbouring mistake is Quip, where a document is not the opportunity. A public page and an internal price argument need different owners. They do not need one migration.

#What the bill is made of

Implementation cost means the parts of the bill. This page will not invent a price per entry, a page count, or a licence figure. Your contract and your space are the places those numbers live, if they live anywhere.

Discovery is the content types the site actually renders, not every experimental type in the space. For each type: the fields, the references, and the person who may publish. A type nobody renders is a candidate to leave out. Write "not rendered" on the line. Do not migrate it in case. Dead types become dead leads if you export them, and dead pages if you rebuild them.

The site line names which frontend reads the space, and how you know a publish succeeded. A preview that only the CMS shows is not success if the public URL is the one in the campaign. Put the URL in the test. The CRM line names the objects you will not copy content into, in writing, so a later import has a refusal to point at. If one field is allowed, name the field and the direction. Page to account is a different decision from account to page. Pick one.

Permissions name who publishes, who previews, and who can see a draft. A draft shared to a public site by a mis-set environment is an incident. The quote should include a check that the test space cannot publish to the production host. Environments are part of the cost. A single space used for drafts and production is a design you should challenge before you add Salesforce to it.

Cutover, if you ever change where the site reads, is one page first, then the campaign, then the rest. Hypercare is the next publish, watched by the editor and by someone who can read the site logs. Training is the next editor in the organisation who can publish without the partner. A quote that says "Contentful migration" and lists none of these is a deposit.

#The week the URL was blank

Monday the campaign is blank and the ad is already running. Tuesday editors republish in the CMS because that is what the channel told them to do. The URL stays blank. Wednesday someone imports another spreadsheet of entries, and sales logs ten calls against page titles. Thursday a developer finds the site is still pointed at the content space, which has the old campaign, not the new one. Friday you republish in the space the site reads, delete the ghost leads, and explain that the sandbox never contained the space.

Write that week into the risk section. The prevention is a sentence in the quote: the CMS sandbox does not contain Contentful, and the site is the test. A firm that will not write the sentence will repeat the week. Ask them to write it. If they say the acquisition put the space inside the org, they are inventing a feature the close notice does not contain.

#The test a buyer should use

Searches ask for the best Contentful Salesforce integration agency, for a consultant to hire, and for an implementation partner. Test them on one content type you already publish.

Ask which type stays in Contentful. Ask which Salesforce object they will not copy it into. Ask them to say that a CMS sandbox does not contain the space. Ask which URL proves a publish. A partner who wants to start by loading entries as leads has failed. A partner who wants to start by rebuilding the types inside the CRM, without an editor asking for that, has changed the project. The acquisition on 1 September 2026 is a date. It is not a rebuild order.

Ask who publishes after the partner leaves. A name in the organisation. If the name is missing, the next campaign depends on a consultancy login. That is not an implementation. It is a queue. Do not rank firms, including this one. Compare them on the URL test and on the list of objects they refuse to fill with prose.

#What you settle before the next campaign

List the types the home page and the campaign page actually use. Name the publisher. Name the production host and the test host. Write the objects that must not receive a copy. If one field is shared, write the direction and the owner. Publish a single harmless change to the test host and read it on the URL, not in a preview that the site does not use.

Then leave the CRM import job unbuilt. A page can mention a product you sell. The mention is not a lead. The form on the page can create a lead, and that form is a different piece of work: fields, consent, and a queue. Do not confuse the form with the body text around it. Scope the form only if you have one. Scope the text as content.

Count the entries you will not move. A space collects drafts, tests, and campaigns that ended. Moving all of them because an export is easy copies the clutter, and it feeds a lead import with still more ghosts. Mark each type as rendered, draft-only, or unused. Unused stays until someone deletes it on purpose. Draft-only stays in the test space. Only a rendered type belongs in a cutover. That split is what a quote should show. A line that says to migrate the space is a line to send back. The editor who publishes the next campaign should be able to point at the short list. If they cannot, you are not late. You have not started.

The quote is ready when an editor can see where to publish, which URL proves it, and which CRM object is off limits. If the page still says the sandbox now includes the space, send it back. The close on 1 September 2026 made Contentful part of Salesforce's story. It did not make a content entry into a customer, and it did not move the space into the sandbox.

#The other searches

The project quote is on contentful implementation cost. That page does not print a figure. Who bought the company is on what happened to contentful. The connector is on integrating contentful with Salesforce. Whether to move is on should I migrate from contentful. The customer fee is on contentful licence cost. Who to hire is on hiring for contentful. This page does not rank an agency.