# Datorama is Marketing Cloud Intelligence

Datorama became Marketing Cloud Intelligence, and Datorama Reports for Marketing Cloud became Intelligence Reports for Engagement. The rename does not replace Tableau.

**Published:** 2025-11-26
**Canonical:** https://synconai.com/datorama-marketing-cloud-intelligence
**Author:** SynconAI Architecture Team

## In short

Datorama became Marketing Cloud Intelligence. Datorama Reports for Marketing Cloud became Intelligence Reports for Engagement. Neither rename replaces Tableau. A quote that prices a Tableau shutdown, or one migration covering Intelligence and Engagement, has mixed products. Cost is scope, licences you already pay, people, and cutover. This page will not print a number.

## Sources

- **The ultimate guide to Salesforce product rebrands** (retrieved 2026-10-10)
  https://gearset.com/blog/salesforce-product-rebrands/
  > Datorama, part of the suite of tools that formed CRM Analytics, became Marketing Cloud Intelligence and its reporting tool, Datorama Reports for Marketing Cloud, became Intelligence Reports for Engagement.

## What to take away

- Datorama became Marketing Cloud Intelligence. The old report name became Intelligence Reports for Engagement.
- The rename does not replace Tableau. A quote that retires Tableau because of Datorama has mixed two products.
- Intelligence Reports for Engagement are not a shutdown of Marketing Cloud Engagement.
- A partner passes by naming the current products and by refusing a blended migration they cannot separate.

## The guide

An analytics lead asks three firms for a quote to replace Tableau, because "Datorama is the Salesforce analytics now" and the old name should be cleaned up. The first firm prices a Tableau exit. The second prices a rebuild of every dashboard in a new workspace and a cutover weekend. The third asks which workspace people still open, and whether anyone has decided to stop using Tableau for a reason that is not the logo. The third question is the brief. The first two have welded a rename to a retirement nobody documented.

The dashboards people argued about in the meeting are still in the tool they were built in. Some are Intelligence. Some are Tableau. A single migration services line cannot see the difference, so it prices both as one departure.

## The name on the workspace

Datorama's path is stated in one sentence, and the sentence does two jobs: "Datorama, part of the suite of tools that formed CRM Analytics, became Marketing Cloud Intelligence and its reporting tool, Datorama Reports for Marketing Cloud, became Intelligence Reports for Engagement." The product name now is Marketing Cloud Intelligence. The report name that used to say Datorama Reports for Marketing Cloud now says Intelligence Reports for Engagement. Quote that whole sentence in the statement of work if you need the history. Then use the current names for the work. A partner who still scopes "a Datorama build" in 2026 is scoping a label. Ask them to say Marketing Cloud Intelligence out loud, and to say Intelligence Reports for Engagement when they mean that report product. If they cannot, they are pricing a search term.

The sentence also places Datorama in the suite of tools that formed CRM Analytics, before the Intelligence name. Do not stretch that clause into a story this page does not have. It does not say CRM Analytics was switched off on a date. It does not say every CRM Analytics asset became an Intelligence dashboard. It says where Datorama sat, and what Datorama and its Marketing Cloud reports became. Stay inside that.

People keep the old login bookmark. The bookmark is not a second product. If the workspace opens, you are in the current product under an old habit. A migration quote that begins by exporting "all of Datorama" without opening the workspace will export a fear, not a list. Open it. Write the workspace name. Write who still has access. That list is the start of scope, and it is often shorter than the folder of old screenshots.

## It does not replace Tableau

Tableau is still Tableau. Marketing Cloud Intelligence does not replace it. A quote that retires Tableau licences because an acquired analytics name now sits in the marketing family has invented a product map. Some organisations use both, for different jobs. Some use one. The quote has to say which job is moving, which job stays, and which job is being stopped because nobody reads it. "Salesforce analytics" is not a job. It is a blur.

Do not describe a silent copy from one into the other. If a number, a campaign result, or a definition is maintained in both places, say which place is allowed to win an argument. If you have never connected them, do not let a proposal assume the connection exists and then price a repair of it. A repair of a link you do not have is a build, and it belongs in its own scope, with a reason.

Intelligence Reports for Engagement are reports. The name points at Engagement. It does not close Engagement, and it does not move email, mobile, or journeys. Those tools sit in Marketing Cloud Engagement, which is the ExactTarget story, not this one. Read that boundary in [the ExactTarget guide](/exacttarget-marketing-cloud-engagement) before you accept a quote that "migrates Datorama and ExactTarget together". They can appear in the same marketing conversation. They are not one cutover. A partner who needs them to be one cutover is protecting a staffing plan, not your calendar.

## What the cost is made of

This page refuses a number. Analytics quotes attract round figures because dashboards photograph well. The photograph is not the cost. The cost is scope, licences you already pay, people, and cutover.

Scope is the workspace, the streams or sources you will change, and the reports a named person still uses. It is also the Tableau workbooks you are explicitly not touching. Write the exclusions. A scope that says "all marketing numbers" will absorb Engagement, the core org, and Tableau before the second workshop. Bring it back to a list. If the list is only "rename the deck that still says Datorama", the scope is a wording change. Price a wording change as time to edit the deck and the contract language. Do not price a new platform under it.

Licences are the Intelligence contract you already have, and the Tableau contract you already have, kept on separate lines. A rename does not merge the invoices. A proposal that shows a saving from cancelling Tableau must show the workbook that will no longer be opened, and the person who agreed to stop. Without that person, the saving is a hope. Leave the hope off the cost page. Add-on products, if someone wants them, are extra lines with reasons. "Because Datorama is the old name" is not a reason to buy anything.

People are the analyst who can say which dashboard is trusted, the marketer who uses Intelligence Reports for Engagement in a weekly meeting, and the owner of each contract. A rebuild staffed only with engineers will recreate charts nobody opens, and will miss the chart a director actually challenges. Internal review time is part of the cost. So is the time to agree a definition. If two dashboards disagree and nobody will decide which is right, you are not in a migration. You are in an argument. Do not pay implementation rates to sit in the argument unless the outcome is a written rule.

Cutover is the morning a team stops opening one place and starts opening another. A rename does not require it. You need it when a report they use will be served from somewhere else, and you can name the report and the somewhere. If the cutover plan is "Tableau goes off, Intelligence is the analytics", you have skipped the list. There is no weekend to book until the list exists. Booking the weekend first is how a team loses a workbook they still needed on Monday.

## What migration services would move

Migration services should say, in verbs, what happens to a given dashboard. It stays in Marketing Cloud Intelligence under the current name. It stays in Tableau. It is rebuilt, and the old one is retired on a date the owner signed. It is archived as a file because the question it answered has gone. Those are different services. A single "Datorama data migration to Salesforce" package usually means the bidder has not picked one.

Data, if you move data, is the data behind a report you named. This page will not invent a row limit, a connector cap, or a daily API allowance. Look those up on your contract if a design depends on them, and write the date you looked. A timeline justified by a cap from a blog is not a timeline you can defend. Ask the partner what they will do when a source is late. The answer should name your source, not a generic lake.

Definitions are the part that makes numbers fight. If Intelligence and Tableau both show pipeline, or both show campaign spend, the quote says whether this work includes making those definitions match. If it does not, say that both numbers will continue, and that the project will not pretend they are one number. Pretending is how a steering pack gets a chart that nobody will sign in the room and everybody will forward afterwards.

Access is in scope if people cannot get into the workspace, or can get into too much of it. It is not in scope by default. A rename does not reset permissions. If the quote includes a new permission model, ask which role changes, and why the old name triggered it. Often the trigger was a new starter who could not find the bookmark. That is a floor guide, not a migration.

## The partner test

The search is for the best Datorama agency. Ignore the ranking, including any ranking that would flatter SynconAI. The test fits in a short call. They say Marketing Cloud Intelligence. They say Intelligence Reports for Engagement when that is the report. They say Tableau is a different product and they will not retire it inside this quote. They say what they will not take on: an Engagement rebuild, a shutdown date for Intelligence that they cannot show you, a blended figure that hides Tableau licences inside a marketing migration.

Hire on that test, not on a gallery of dashboards from another organisation. Their gallery does not know which of your reports is trusted. A consultant who asks for the trusted list before the architecture picture is the one to keep talking to. A consultant who opens with a replacement of Tableau has failed before the architecture slide.

An implementation partner, for this old name, is often a partner for a small change: labels, a source you are genuinely adding, a report you are genuinely retiring. The word implementation makes teams expect a programme. If the programme's only fuel is the word Datorama, do not start it. Pay for the list. Then decide if any row on the list is a build.

## How the quote should read

| Line they wrote | What it actually is | What you send back |
| --- | --- | --- |
| Replace Tableau with Datorama | Two products, one of them already renamed | Split them. Tableau stays unless a named owner stops a named workbook |
| Migrate Datorama into Salesforce | Marketing Cloud Intelligence, already a Salesforce product | Ask which workspace and which report changes home |
| One cutover for ExactTarget and Datorama | Engagement and Intelligence, different tools | Separate the quotes. Read the Engagement boundary first |
| All dashboards rebuilt | An unbounded scope | List the reports a person still uses. Archive or ignore the rest |
| A single analytics number | Scope, two licence estates, people, and a maybe-cutover | Four lines. No total until the exclusions are written |

::: note
Marketing Cloud Intelligence does not replace Tableau. Intelligence Reports for Engagement does not replace Engagement. If a quote needs those replacements to make sense, the quote is about a different project from the rename.
:::

Write the brief as a table before you ask for money. Column one, the current product name. Column two, what a named person does there on a Monday. Column three, stay, change, or archive. Column four, the licence you already pay. Anything that cannot fill column two is not ready for column three. A partner who prices the blank rows is pricing folklore about Datorama.

When the replies come back, read the first paragraph only. The pass names Marketing Cloud Intelligence and refuses the Tableau exit. The fail says the old analytics should be consolidated so the stack is clean. Clean is not a requirement you wrote. The requirement is that a person can still open the number they trust, under a name that matches the product, without a weekend that turns the other tool off.

Keep the old name in a glossary if your contracts need it. Glossary is not scope. The moment the glossary becomes a workstream, you are paying people to narrate a rebrand you could have finished in the first meeting with the sentence this page quotes. Use the sentence. Then get back to the report someone actually misses when it is late.

## The other searches

The project quote is on [datorama implementation cost](/datorama-salesforce-implementation-cost). That page does not print a figure. Who bought the company is on [what happened to datorama](/what-happened-to-datorama). The connector is on [integrating datorama with Salesforce](/integrating-datorama-with-salesforce). Whether to move is on [should I migrate from datorama](/should-i-migrate-from-datorama). The customer fee is on [datorama licence cost](/datorama-salesforce-licence-cost). Who to hire is on [hiring for datorama](/hire-datorama-salesforce-partner). This page does not rank an agency.


## Questions

### What should a Datorama data migration quote include?

It should name the Marketing Cloud Intelligence workspace and say which reports stay, change, or are archived. It should name Intelligence Reports for Engagement if those are in scope, and it should leave Tableau out unless a named owner is stopping a named workbook. It should not bundle Engagement into the same cutover. Split scope, licences, people, and cutover.

### What is a Datorama implementation cost made of?

Scope of the reports you will actually change, the Intelligence and Tableau licences you already pay on separate lines, the analysts and marketers who know which dashboard is trusted, and a cutover only when a report changes the place it is opened. A wording fix for the old name is not a new platform. This page will not print a price.

### Does Datorama migration replace Tableau?

No. Datorama became Marketing Cloud Intelligence, and its Marketing Cloud reports became Intelligence Reports for Engagement. Tableau is a different product. A quote that cancels Tableau because of this rename has mixed the map. Keep both licence lines visible until a person agrees to stop using a specific workbook.

### How do you judge the best Datorama integration agency?

Do not rank agencies, including SynconAI. A partner passes if they say Marketing Cloud Intelligence, distinguish Intelligence Reports for Engagement, refuse to retire Tableau inside this quote, and refuse a blended Engagement migration. They name what they will not take on. A dashboard gallery from another organisation does not pass.

### When should you hire a Datorama consultant or implementation partner?

Hire when you have a list of reports a named person still uses, marked stay, change, or archive. Hire a partner who asks for that list before drawing a replacement architecture. If the only brief is that the old name should be cleaned up, do not hire an implementation. Fix the words, then see if any row is still a build.

### Is datorama owned by Salesforce?

Yes. Datorama was bought and renamed. The full account is at https://synconai.com/what-happened-to-datorama.

### When did Salesforce acquire datorama?

The rebrand record places the rename with the Marketing Cloud intelligence tools.

### What happened to datorama after the Salesforce acquisition?

Datorama became Marketing Cloud Intelligence. Datorama Reports for Marketing Cloud became Intelligence Reports for Engagement. It does not replace Tableau.

### Should I migrate from datorama to Salesforce?

Move the report, not the brand name. If the number still lives in Intelligence, leave it there until the replacement report matches.

### What is the datorama licence cost, or the price Salesforce paid?

The page this guide cites does not publish a purchase price or a licence fee. The licence read is at https://synconai.com/datorama-salesforce-licence-cost.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Marketing Cloud Next (https://synconai.com/salesforce-marketing-cloud-next).