Boreon MCP Layer · Migrations
Most of our migrations take Tableau Server to Tableau Cloud, with firm fixed prices, because Tableau is home for most teams. We also move one Tableau Cloud site into another, rebuild Databricks AI/BI dashboards in Tableau, bring Tableau content to Databricks, Snowflake or Tableau Next whenever you want it there too, and bring Salesforce CRM and CRM Analytics dashboards into Tableau Next. Every move is planned with you, rehearsed first and checked against the original.
From Tableau ServerMost teams start here
Tableau is home for most teams. We move your whole Tableau Server site to Tableau Cloud with firm fixed prices: content and extracts, people and permissions, schedules and subscriptions.
See how it works
From Tableau Cloud
Move content from one Tableau Cloud site to another, or promote it from dev to test to production, even between projects on one site. A repeat run carries only what changed since the last one.
See how it works
From Databricks
A Databricks AI/BI dashboard becomes a Tableau workbook with its dashboard, reading the same tables live through a published Tableau data source.
See how it works
From Tableau Server or Tableau Cloud
Dashboards become AI/BI dashboards with Genie built in. Prep flows become materialized views.
See how it works
From Tableau Server or Tableau Cloud
Dashboards become Streamlit in Snowflake apps. Prep flows become dynamic tables.
See how it works
From Tableau Server or Tableau Cloud
Tableau worksheets, Salesforce CRM reports and CRM Analytics widgets become Tableau Next visualizations, and their dashboards become Tableau Next dashboards, inside Salesforce.
See how it works
Most of our migrations are this one. We read everything on your Tableau Server site, plan the move with you and rehearse it in full without writing a thing. It starts only when you approve, and afterwards we read both sites back and compare them, so you get a report for your change record.
We read your site
Every project, workbook, data source and schedule, before anything moves.
You read the plan
What moves, where it lands, and anything that needs you.
We rehearse it
A full dry run that writes nothing.
You approve
The move starts only when you say so.
We compare both sites
Read back and checked, with a report for your records.
We move content from one Tableau Cloud site to another, or promote it from dev to test to production, with the same plan, rehearsal and approval. Each view is checked against the original, and a repeat run carries only what changed since the last one.
Some teams want their Databricks work in front of the people who live in Tableau. An AI/BI dashboard becomes a Tableau workbook with its dashboard, reading the same tables live through a published Tableau data source. Every sheet is checked against the original before it can publish, and it publishes only when an administrator on your side approves it.
| On Databricks | In Tableau |
|---|---|
| An AI/BI dashboard | A Tableau workbook with its dashboard |
| Counter, bar, line, area, pie, scatter and table widgets | Tableau sheets, each checked against the original |
| Text boxes and the grid layout | The same, on the dashboard |
| The dashboard's tables | A published Tableau data source, read live |
If you want dashboards on Databricks or Snowflake too, here is where each piece ends up.
| On Tableau | On Databricks | On Snowflake |
|---|---|---|
| Dashboards | AI/BI dashboards, with Genie built in | Streamlit in Snowflake apps |
| Prep flows (.tfl) | Materialized views | Dynamic tables, or a materialized view where Snowflake allows one |
| Published data sources (.tds) | The Unity Catalog tables the data already sits in | The Snowflake tables the data already sits in |
| Measures, colors and number formats | The same, down to dual axes | The same, down to marks and sort order |
| Filters | The same filters, on the dashboard | Live selectors in the app |
| Sign-in and roles | SSO roles carried through, no second sign-in | Key pair, OAuth, or each person through Snowflake OAuth |
A workbook and the Prep flow behind it move together. The table or view is built and checked first, then the dashboard is rebuilt on top of it. Nothing is published until every sheet checks out.
Plans change, and sometimes the warehouse does too. The Boreon MCP Layer lifts your tables, views and SQL from Databricks to Snowflake, or from Snowflake to Databricks, and rewrites the SQL for the other dialect as it goes. Afterwards the same semantic layer sits over both warehouses, so your people keep asking their questions the way they always have.
Databricks Tables, views and SQL Snowflake
Start there. We'll put the layer over it and answer its questions in natural language, and if you ever want it on another platform too, every number is checked against Tableau first.