Migrate · Govern
Choose What Migrates
Load the source content tree, then scope by project or cherry-pick workbooks, data sources and flows.
Platform guarantee
Nothing changes until a person says so.
The AI reads, explains and proposes. Anything it suggests arrives as a card that routes into the same approval gate a person would use, with the same signature and dual-control rules. Publishing always creates a new copy and never overwrites your work.
In the product
Migrate, as it actually looks.
The register
What Migrate does for you.
Every line below was read out of the product’s own source on 14 August 2026.
Runs the official Tableau Migration SDK on .NET 8 inside the same container.
Cherry-picks are keyed by LUID, so renames and duplicate names cannot select the wrong content, and parent projects are included automatically.
A two-layer dry run precedes a hard approval gate with three enforced conditions.
The audit is written in JSON and Markdown, and PAT names and secrets never enter it.
Specification
- Version3.7.1
Shipping at the 24 August 2026 research pass.
- Packageboreon-tabmigrate
The repository this behaviour lives in. Every claim above has somewhere to be checked.
- Model useOptional, on your own key
Switched on by you, running on the provider key you supply.
Assurance
The AI is yours to switch on.
Where Migrate uses AI, it runs on the provider key you supply. Your prompts go to the provider you picked, and nowhere else.
The model drafts. Anything that would change your Tableau content arrives as a card that routes into the same approval gate a person would use, with the same signature and dual-control rules you already run. Your team keeps the pen.
Govern
Prove what changed, who can reach it, and what it exposes.
Migrate sits with these, and one login opens all of them with your Tableau permissions.
See Migrate in your own Tableau Environment.
A month on your own content is a better test than any description of it.