Tableau dashboards
Sheets become AI/BI widgets with the same measures, filters, colours, dual axes and number formats, and open in the portal with Genie built in.
Tableau to Databricks
Move Tableau to Databricks in one conversation.
The Boreon MCP Layer reads each workbook on your Tableau Server or Tableau Cloud site, turns the Prep flow under it into a Databricks materialized view, rebuilds the dashboard as a Databricks AI/BI dashboard and proves every number against Tableau before it publishes. No scripts and no hand-written SQL.
Go live in one month
- Weeks 1 to 2MVPThe Boreon MCP Layer inside your firewall, with your priority dashboards moved and every number proven.
- Weeks 3 to 4Final deploymentThe rest of your priority workbooks, hardening, sign-off and training.
- Day 30Go liveYour team runs it in chat, and every future move is yours.
Measured on a real workbook
Three sheets, identical to Tableau
DBX Platform Latency Calls & Uptime, moved to a Databricks AI/BI dashboard by the Boreon MCP Layer, in one conversation.
- Read the workbook. The Databricks Latency Dashboard: three sheets, with their shelves, filters and calculations.
- Found the Prep flow. Its data source is a flow output on Databricks.
- Flow to view. One SQL statement, one CTE per flow step: a materialized view of 20 million rows, built in 72 seconds.
- Proven and checked. Every sheet’s query ran with zero SQL errors, and 41 of 41 rows matched Tableau’s own answer.
- Published. A Databricks AI/BI dashboard, with a fidelity score of 96%.
Row by row, against Tableau
Each sheet’s rows compared with Tableau’s own answer, through the VizQL Data Service.
| Rows matched | Result | |
|---|---|---|
| Sheet 1 | 12 / 12 | Identical |
| Sheet 2 | 5 / 5 | Identical |
| Sheet 3 | 24 / 24 | Identical |
| All three sheets | 41 / 41 | Identical, fidelity 96% |
What moves
Dashboards, Prep flows and the chain between them
Four kinds of work from Tableau Server or Tableau Cloud, all started from the same chat.
Tableau Prep flows
Each flow step becomes a CTE in one SQL statement, created as a Databricks materialized view.
The whole chain
A workbook fed by a Prep flow moves as one job: the view is created and verified first, then the dashboard is pointed at it.
Answers publish to Tableau too
From the same chat, Render & Publish sends any answer to your Tableau site as a workbook, without adding a second data source.
Genie, built in
It opens in the portal, with Genie in line
Every Databricks dashboard the portal renders comes with Genie beside it. Your people keep putting questions to the dashboard itself, in plain words, long after the migration. The portal is the same chat that moved it. See the LLM Portal
Access
Your roles, on Databricks too
It reads your workspace and Unity Catalog with the credentials you choose.
What it reads
Unity Catalog tables and SQL warehouses, with every query over the Statement Execution API.
How it signs in
A personal access token, OAuth or a service principal.
Your SSO roles
SSO roles carry through to Databricks, and embedded dashboards open without a second sign-in.
Audited writes
The only writes are the ones you ask for: a published dashboard or a created view, each one audited.
MVP in two weeks. Go live in one month.
Tell us which dashboards on your Tableau Server or Tableau Cloud site you would move first. We scope them, stand up the Boreon MCP Layer inside your firewall and put a working MVP in front of your team in two weeks, with final deployment and go-live inside the month.