Tableau to Snowflake

Move Tableau to Snowflake 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 Snowflake dynamic table, rebuilds the dashboard as a Streamlit in Snowflake app and checks every number against Tableau before it publishes. No scripts and no hand-written SQL.

Talk to us about the Boreon MCP Layer See the whole chain

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.

The whole chain

The flow becomes a table, then the app follows

A workbook fed by a Prep flow moves from Tableau Server or Tableau Cloud as one job, in build order.

Each flow step becomes a CTE in one SQL statement, created as a Snowflake dynamic table, or as a materialized view where Snowflake allows one. The table is created and verified first, and only then is the Streamlit in Snowflake app built on it. The app reads a table that has already been checked.

The statement it writes, one CTE per flow step

CREATE DYNAMIC TABLE sales.pipeline_dt
  TARGET_LAG = '1 hour'
  WAREHOUSE = compute_wh
AS
WITH clean AS ( … ),
     joined AS ( … )
SELECT … FROM joined;

What moves

Dashboards become Streamlit apps

Four kinds of work from Tableau Server or Tableau Cloud, all started from the same chat.

Tableau dashboards

The layout, marks, colours, sort and number formats become a Streamlit in Snowflake app, with its filters as live selectors.

workbook → Streamlit app

Tableau Prep flows

Each flow step becomes a CTE in one SQL statement, created as a Snowflake dynamic table, or a materialized view where Snowflake allows one.

.tfl → dynamic table

The whole chain

A workbook fed by a Prep flow moves as one job: the table is created and verified first, then the app is built on it.

flow → table → app

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.

answer → Tableau workbook

The Boreon MCP Layer speaks Tableau and Snowflake

It reads both sides through their own APIs, keeps a semantic model of how they map, and writes only when you ask it to.

What the Boreon MCP Layer reads on each side, and how it signs in
	What it reads	How it signs in
Tableau	Workbooks and dashboards, published data sources, Prep flows, the VizQL Data Service and the Metadata API, on your Tableau Server or Tableau Cloud site.	A personal access token, a Connected App JWT or a central service account.
Snowflake	Your account, databases, schemas and virtual warehouses, with every query over the SQL API.	A key pair or OAuth, or as each person through Snowflake OAuth, with their own roles applied.
Boreon MCP Layer	Tableau fields mapped to Snowflake columns, per license, with lineage from flow to data source to workbook.	Your own SSO, with every write audited.

Proof on Snowflake

Proven on Snowflake before it publishes

Every migration hands you its proof, measured on your own workbooks.

Its own tables. A dashboard is rebuilt only on the Snowflake tables its data already sits in.
All or nothing. If one sheet has no faithful match, nothing is published and the agent says why.
Numbers first. Averages, distinct counts and medians stay exact under dashboard filters, checked against Tableau’s own answer.
Queries proven first. Every sheet’s query runs on Snowflake before publishing, and the app opens without SQL errors.
Audited writes. The only writes are the ones you ask for: a published app or a created table, each one audited.

After the move

The portal stays, for Snowflake and Databricks too

When the migration window closes, the Boreon MCP Layer stays onsite as the chat portal for your data warehouses: Snowflake, and Databricks too, where every dashboard the portal renders comes with Genie built in. See the LLM Portal

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.

Plan your go-live