ChatGPT
Claude
Google AI
Copilot
The Monday pipeline meeting opens on a blank screen. On Friday a steering note said Tableau was finished. Tableau Next would replace it, and the Data Cloud rename meant the numbers now lived in Salesforce. Someone archived the workbook the meeting had used for two years. The analyst who published it was told not to refresh the extract. The seller who asks for the number gets a shrug, then an agent that has no workbook to read. The figure they needed was a filter on last quarter, maintained by one person, on a product that still has its name. Nothing replaced it. The meeting is the failure. The slide caused it.
A procurement lead then asks three firms for a Tableau data migration quote. Two of them price a load of dashboard images into a Salesforce file library. The third asks which meeting breaks if the workbook stays closed for a week. Only the third question can be answered from the room you are in. The other two have invented a destination. This page is about refusing that invention before the workbook is switched off for good.
The name Tableau kept
Tableau was acquired in 2019 and kept its name. You still ask for it by that name. A rebrand of a different product does not retire it. A workbook is a set of questions pointed at a data source, published by a person, and opened by a meeting. Changing the logo on a slide does not move those questions into an opportunity field.
Tableau Next does not replace Tableau. Treat any sentence that says it does as a claim you have not been shown. If a partner draws one arrow from Tableau to Tableau Next and leaves the current workbook off the page, they have skipped the thing the meeting uses. Next can be a separate conversation, with its own reason, its own licence check, and its own owner. It is not the automatic next step of an acquisition that kept the original name.
Write down the workbooks that are still opened. Not the catalogue of every file anyone saved. The ones a meeting asks for by name. For each, the question it answers, the data source it reads, and the person who can publish a change. If that person has left the organisation, the workbook is already a risk. Switching the product off does not remove the risk. It removes the number and leaves the meeting with nothing.
A search for migration services often assumes the workbook is a pile of rows waiting to be loaded. Some workbooks sit on an extract. Some sit on a live source. Some sit on a spreadsheet a person still edits. Those are different jobs. A quote that says "move Tableau into Salesforce" has not chosen among them. Ask which source. If the answer is "all of them", you are looking at a slogan.
Data 360 is a rename, not a new home for the workbook
People mix Tableau into the Data Cloud story because both words appear in the same programmes. The help page states a rename, and only a rename: "As of October 14, 2025, Data Cloud has been rebranded to Data 360." Use that sentence to correct a label on a diagram. Do not use it to tell an analyst to stop publishing. The sentence does not mention Tableau. It does not say a workbook has become a CRM record. It does not say Tableau Next has taken the meeting.
On 14 October 2025 the product formerly called Data Cloud took the name Data 360. Update the words on the architecture slide if they still say Data Cloud. Leave the workbook where it is until you have a written replacement for the question it answers. A new label on a different product is not a cutover plan. Old labels may still appear in the application during a transition. That is a wording issue. It is not permission to archive the extract.
If Data 360 is genuinely in the programme, give it a question that is not the workbook's question. One sentence. Who waits on the answer, and in which screen. If the sentence is "the same pipeline number the workbook already shows", you do not have a second product. You have a proposal to rebuild a meeting inside a rename. Rebuilds are allowed when the meeting agrees the new place is the place they will open. They are not allowed because a slide ran out of boxes.
Do not describe a Tableau workbook as identity resolution, and do not describe a dashboard filter as a master record. The workbook shows a cut of data someone chose. It does not decide which customer is the real customer. If a project needs that decision, it is a different page, with a different owner. Keep it off this quote.
What the migration keyword is asking you to buy
The search phrase asks for a data migration quote, an implementation cost, and migration services. Read those as a request for a list, not a request for a single number. This page will not invent a dollar figure. Cost means the parts of the bill.
The inventory is the workbooks the meetings still open, not every stale file on a server. Each line names the question, the source, and the publisher. A workbook with no publisher is a finding. Write "no publisher" on the line. Do not hire a firm to guess who owns it.
The source work is access, refresh, and what happens when the source is late. An extract that fails on Sunday night is a Monday meeting with yesterday's number, or with no number. The quote should say which of those the business accepts. A partner who promises the dashboard will always be current, without naming the source, is selling a wish.
The people work is who may publish, who may view, and who is on leave. A view right that includes the whole organisation because the sandbox was loose is a design. It may be the wrong one. Field-level rules in Salesforce do not automatically apply to a workbook that reads a warehouse. Say, in the quote, which cut of the data a seller may see. Test it as that seller.
Cutover, if you ever have one, is the week both places stay available. The meeting uses the old workbook. A named person checks the new place against it. You switch the meeting only when the numbers match for the questions you wrote down, not when a project plan says the week has ended. Hypercare is the following meetings, with the publisher still available. Training is the next person who can refresh the extract without calling the partner.
| Line on the quote | What you are buying | Send it back if |
|---|---|---|
| Inventory | Meetings, workbooks, questions | The list is "all dashboards" |
| Source | Where the workbook reads, and who owns that source | The source is "Salesforce" with no object |
| Publisher | The person who may change the workbook | The publisher is a shared mailbox |
| Overlap | A week both places stay open | The plan switches Tableau off on day one |
| Viewers | Who may see which cut | Everyone in the org can open every workbook |
| Out of scope | Tableau Next, unless it has its own reason | Next is drawn as the replacement |
What a closed workbook does to the week
Picture the week after the archive, without a replacement anyone has agreed. On Monday the pipeline meeting shares a screenshot from someone's inbox, taken last month. The filter is wrong for this quarter. Two regions argue from two screenshots. On Tuesday a seller builds a report in Salesforce that counts opportunities. The count is not the workbook. The workbook excluded a record type the business does not forecast. The report includes it. The number is higher, and it is wrong in a way that looks like good news.
On Wednesday finance asks why the extract stopped. The answer is that a project plan said the product was retired. Finance still ties a commentary to that extract. They do not have a new commentary. On Thursday an administrator deletes the data source credentials because nothing is scheduled to use them. The publisher, who was told to stop, can no longer refresh even if the meeting begs. Friday is spent asking for the credentials back. None of this is a migration. It is the cost of switching a product off before the question has a new home.
Write that week down before you accept a quote that starts with a shutdown date. The shutdown date is the risky line. The safe line is the overlap: the workbook stays, the publisher stays, and any new place has to match on the questions you listed. If a firm will not put the overlap on the page, they are pricing the archive, not the implementation. Ask them to remove the shutdown date. If they will not, they are the wrong firm for this decision, whatever their other work looks like.
A workbook can also be wrong while it stays on. A filter that hides a region, a join that doubles a row, an extract that has been failing quietly. Those defects are worth a ticket. They are not a reason to declare the product replaced. Fix the filter in the place the meeting already opens. Moving a broken question into a new product moves the defect and adds a second place to be wrong.
The test a buyer should use
Searches ask for the best Tableau Salesforce integration agency, for a consultant to hire, and for an implementation partner. There is no league table that knows your meetings. Use a test on your workbooks, not a sample the firm brought with them.
Ask which workbook stays in Tableau. A partner who says none of them, because Next replaces Tableau, has failed the test. Ask which single question, if any, Data 360 is meant to answer that the workbook does not. If they cannot separate the two, they will price one project and deliver a rename. Ask what breaks if Tableau is off for a week. The right answer names a meeting and a person. The wrong answer is "nothing, because the data is in Salesforce now."
Ask them to leave a dollar figure off the first page until the inventory exists. A number without the list is not a cheaper quote. It is an unfinished one. Ask who publishes after the partner leaves. A name in the organisation, not a rota called "the analytics team". If the name is missing, the workbook will rot the way the archived one already has.
Do not accept a ranking, including a ranking that flatters the firm publishing this page. Two firms that can name the same three workbooks can be compared on the overlap week and the publisher. Two firms that offer a badge cannot. A reference call comes after the list. Ask the reference which meeting they almost broke, and whether the old workbook was still open that week.
What you settle before you switch anything off
Pick five workbooks the business would notice by Wednesday if they vanished on Monday. For each, write the question, the source, the publisher, and the meeting. If you cannot fill the publisher, that is the first job, and it is not a migration. It is a name.
Leave those workbooks on while you do it. Archiving them to force the conversation removes the only evidence you have. Run the Monday meeting on the existing workbook. In parallel, write the sentence for any Data 360 question that is truly different. If you cannot finish the sentence, Data 360 is not part of this quote yet.
A backup of the CRM will not redraw the workbook, and a restore will not take the meeting. That neighbouring mistake is set out in Own, backup, and Recover. Do not add a backup line to a Tableau quote because both products were acquired. They answer different fears. One fear is a missing number in a meeting. The other is a missing record after a bad day. Keep the quotes apart.
The quote is ready when a new analyst can see which workbooks stay, who publishes them, and which questions are explicitly not moving. If the page still says data migration and names no meeting, send it back. The 2019 acquisition kept the product's name. It did not appoint Tableau Next as a replacement, and it did not make a workbook into a CRM row.
The other searches
The project quote is on tableau implementation cost. That page does not print a figure. Who bought the company is on what happened to tableau. The connector is on integrating tableau with Salesforce. Whether to move is on should I migrate from tableau. The customer fee is on tableau licence cost. Who to hire is on hiring for tableau. This page does not rank an agency.
