Salesforce Marketing Cloud → Typeface

Catalog plan outline

General guidance from the Afterstack catalog for Salesforce Marketing Cloud → Typeface. Not Salesforce Marketing Cloud or Typeface vendor documentation.

Migration friendliness

Salesforce Marketing Cloud 4/10 · Typeface 4/10

Speed to live

Salesforce Marketing Cloud 2/10 · Typeface 5/10

Catalog migration difficulty

Salesforce Marketing Cloud high · Typeface medium

Data to export from Salesforce Marketing Cloud

• custom objects
• sequences and cadences
• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: automation, lifecycle

How the catalogs differ

• Typeface is flagged for custom objects. Collapse unused fields before loading them.
• Typeface is not flagged for: sequences and cadences, campaign and automation records, installed marketplace apps.
• Salesforce Marketing Cloud is flagged with an open API, which is the export path to test.
• Typeface is flagged with an open API for the load.
• Salesforce Marketing Cloud is cataloged as a fit for: Salesforce CRM gravity.
• Typeface is cataloged as a fit for: Enterprise brand teams.

Phases

1. Export

   Take Salesforce Marketing Cloud as the source of truth for this pair. Export custom objects; sequences and cadences; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: automation, lifecycle. Enterprise MAP incumbent — journeys, email, and a services army.

2. Map

   Load into Typeface only after the field map is written down. Enterprise generative content — on-brand AI for marketing orgs that cannot use a consumer LLM. Typeface is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Typeface scores 5/10 on speed to live and 4/10 on migration friendliness. Run one sample load and one report the team already uses in Salesforce Marketing Cloud before a full cutover.

4. Cut over

   Salesforce Marketing Cloud scores 4/10 on migration friendliness and is marked high difficulty in the catalog. Keep Salesforce Marketing Cloud readable until the team is working in Typeface. Salesforce Marketing Cloud (ExactTarget lineage) is the enterprise marketing-automation incumbent beside Marketo. Einstein and AI journeys sit on a platform that was not designed as an AI content studio. A leave-from for global lifecycle teams.

Salesforce Marketing Cloud to Typeface: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Salesforce Marketing Cloud or Typeface vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Salesforce Marketing Cloud

Two Salesforce developer URLs that used to describe a data extract activity and data-extension row retrieval both returned 404 on 2026-10-17, so this page does not invent an extract procedure. The Marketing Cloud Engagement product page that did load is a marketing narrative, not an API reference. It distinguishes Marketing Cloud Engagement, which it says is the enterprise toolset people know through Journey Builder, Content Builder, and Automation Studio, from Marketing Cloud Next, which it says is rebuilt on the Salesforce platform. It says existing Journey Builder journeys can be used inside Flow, and that Flow is the next automation engine. It says Engagement is the evolution of ExactTarget. No software fee is printed. The phone number on the page is a sales line. The catalog's empty starting price and custom model match the missing fee. A trial length is not on the page, so the catalog trial flag is unverified. Journeys, data extensions, and send definitions stay in Marketing Cloud unless a later contract says otherwise. Nothing opened here is a subscriber export.

• Marketing Cloud Engagement product page — checked 2026-10-17

How Typeface imports

Typeface's integrations library, opened the same day, has a Salesforce Marketing Cloud card whose entire text is: publish your journeys and dynamic content to activate email campaigns instantly. That is a publish-out sentence. It does not say Typeface ingests Journey Builder, a data extension, or a subscriber file. Neighboring cards include Marketo, HubSpot, Braze, Klaviyo, and Salesforce Data Cloud, each a one-line description. The Typeface homepage is a demo for an orchestration product and prints no fee. It says brand guidelines, audiences, assets, and campaign learnings are held so agents can act on them, and it says rollout uses MCP, APIs, and integrations. It does not document an import wizard. No public import docs for a Marketing Cloud cutover; onboarding is vendor-led, checked 2026-10-17. No public pricing on the homepage, checked the same day. The catalog's null price and custom model match. The catalog trial flag does not appear as a sentence on that homepage. Marketing Cloud remains the send system. Typeface is a content layer that claims it can publish into it.

• Typeface integrations — checked 2026-10-17
• Typeface homepage — checked 2026-10-17

Object and field mapping

• A Journey Builder journey is an Engagement object the Salesforce page names. Typeface's card says publish journeys and dynamic content. It does not say the journey definition is copied in.
• Content Builder assets are the closest Salesforce object to what a generative tool would emit. The card does not list Content Builder fields.
• Automation Studio is named as part of Engagement. Typeface's card does not mention automations, SQL activities, or file drops.
• Flow is the Marketing Cloud Next engine. The Salesforce page says existing Journey Builder journeys can run there. That is a Salesforce-to-Salesforce statement, not a Typeface import.
• Subscribers and data extensions were not on a page that successfully loaded. They are not mapped.
• ExactTarget is a historical name on the Salesforce FAQ. It is not a Typeface object.
• Brand guidelines on the Typeface homepage are a Typeface store. They are not a Marketing Cloud export.

What will not carry over

• A documented subscriber or data-extension extract. The two developer URLs 404'd.
• Journey logic, wait steps, and exit criteria. The Typeface card is about publishing content.
• A Typeface price.
• A trial length for either product on the pages that loaded.
• Send classification, sender authentication, and deliverability settings.
• Marketing Cloud Next as if it were Typeface. Flow is Salesforce's engine.
• A one-click cutover. The homepage describes vendor advisors and engineers beside the product.

Cutover checklist

1. Write down that Marketing Cloud stays. This pair is a content layer, not a new ESP, on the evidence opened.
2. Do not brief an extract from the 404'd developer URLs. Ask Salesforce for a current export doc before anyone promises a file.
3. Ask Typeface what publish your journeys means in the tenant you will buy. The public card is one sentence.
4. Keep Journey Builder or Flow as the sender until a test publish lands in Content Builder or the journey you named.
5. Separate Engagement from Marketing Cloud Next in the project plan. Salesforce says they are not the same product.
6. Leave sender authentication and data extensions untouched. They were not in the Typeface card.
7. Quote both products as sales-led. Neither loaded page has a dollar.
8. Ignore homepage anecdotes. They are not a migration schedule.

Common pitfalls

• Telling leadership the journeys moved because the card contains the word journeys.
• Rebuilding Flow as if it were the Typeface project. Flow is Salesforce's.
• Using a dead developer URL as proof that extracts are impossible. A 404 is a dead page, not a product limitation.
• Canceling Marketing Cloud seats before a single publish succeeds.
• Filling in a Typeface price from a third-party index. The homepage has none.

Related catalog pages

• What should replace Salesforce Marketing Cloud? — Switch narrative
• Typeface product page — Enterprise generative content — on-brand AI for marketing orgs that cannot use a consumer LLM.
• Typeface vs Salesforce Marketing Cloud — Head-to-head already in the catalog
• Marketing category — Catalog hub for this category