AI Mode: Claude
1 · Connect › 2 · Discover › 3 · Map Users › 4 · Migrate

Choose What Migrates

Load the source content tree, then scope by project or cherry-pick workbooks, data sources and flows. Leave everything unticked to migrate the whole site.

Connect — Source & Destination

Sign in to both Tableau endpoints with a Personal Access Token. Either endpoint can be Tableau Server or Tableau Cloud. Nothing writes to either site until Step 4.

① Source
Base URL only — no site path.
The site URL slug, not the display name.
The name you gave the token in Tableau.
Shown once when the token was created.
② Destination
Base URL only — no site path.
The site URL slug, not the display name.
The name you gave the token in Tableau.
Shown once when the token was created.
✨ AI-enhanced diagnostics — optional
Enriches error diagnosis. Mapping always uses the local Ollama model.

Map Users

Map every source username to its destination Tableau ID. The AI suggests matches based on name similarity and email patterns — you review and edit each one before anything executes. AI is never in the write path.

Set a destination email domain, then Map content owners — each owner is mapped to username@yourcompany.com so its content migrates with the original owner. AI-suggest and Load all users are alternatives. Edit any row below.
Source username Destination email / username Conf. AI reason

Paste a Tableau CMT-format mapping CSV (no header required): 

user,local\hwilson,henry.wilson@acme.com
user,local\jjohnson,janna.johnson@acme.com
group,local\Finance Team,Finance Group
domain,dev.mycompany,prod.mycompany

Export the current mapping grid as a Tableau CMT-compatible CSV. Full round-trip — re-import on a future run or use it with Tableau's own Content Migration Tool.

Additional options

Tick exactly what to include. Workbooks, data sources, flows and their permissions are governed by your selections above; these ride alongside.
The schedule/task types often have no direct Cloud equivalent and may report expected errors in the manifest. Custom views are on by default.
On (default): copy who can access each item (users/groups + capabilities); grantees that don't transfer are skipped. Off: all source grants — item and project-default — are cleared, so content takes the destination project's existing access instead.
Off (default): content publishes without embedded credentials; users re-enter each connection's credentials once on the destination. On: Tableau requires the source site to be enrolled in keychain sharing; without enrollment, items report keychain errors.
"Preserve" keeps each item's source owner on the destination — those owner accounts are auto-included in the user scope so the run won't fail on a missing owner. "Publish as connecting user" makes the PAT account the owner.
"Mapped only" is required for Custom Views to migrate correctly on scoped runs.

Review, Approve & Migrate

Nothing is written until you approve. Review the pre-flight risk preview below, optionally run the SDK structural dry-run, then sign off. The migration runs as deterministic Tableau Migration SDK calls — AI is never on this path — and every run produces a downloadable compliance audit.