Design a Tableau Infrastructure22% of the exam

Migration paths, identity stores and Content Migration Tool

Pick the right method for each migration path (Cloud and Server in either direction, Windows and Linux, identity-store changes, consolidation) and plan Content Migration Tool runs: site scope, permission mappings, project options and pre- and post-migration scripts.

Official exam objective
1.3 Plan a migration: 1.3.1 Plan a migration of Tableau Cloud to Tableau Server; 1.3.2 Plan a migration of Tableau Server to Tableau Cloud; 1.3.3 Plan a migration from Windows to Linux; 1.3.4 Plan a migration from Linux to Windows; 1.3.5 Plan a migration from one identity store to another; 1.3.6 Plan a consolidation of multiple Tableau servers or sites into fewer servers or sites; 1.3.7 Plan a migration from one Tableau Server environment to another; 1.3.8 Create scripts for migration; 1.3.9 Use the Tableau Content Migration Tool.

~7 min read · 16 practice questions

What the exam expects

  • Plan moves between Tableau Cloud and Tableau Server in both directions, including what the platform differences break.
  • Plan Windows-to-Linux and Linux-to-Windows moves by backup and restore, with the acceptance tests the restore does not cover.
  • Plan an identity-store change and tell it apart from the Identity Migration.
  • Plan consolidations and Server-to-Server moves with the Content Migration Tool (CMT), including permission mappings and project options.
  • Write pre- and post-migration scripts for a CMT plan.

Key terms:

  • Content Migration Tool (CMT): a Windows application, part of Advanced Management, that copies content between Tableau Server sites through a migration plan; between separate installations it needs user-based licensing.
  • Tableau Migration SDK: a framework for custom-coded Server-to-Cloud migration applications.
  • Identity store: where Tableau Server keeps users and groups, either local or external (Active Directory or LDAP).
  • Permission mapping: a CMT rule that translates a source domain, user or group to its destination equivalent.

Key facts

Server to Cloud tool
Detail
Migration SDK; CMT not recommended
Cloud REST scope
Detail
Site-level administration; refactor tooling to PATs
Cloud provider backups
Detail
Restore the whole system, not your files
Cross-OS restore
Detail
Supported both ways with the same identity-store type
What a restore leaves out
Detail
Customizations and additional nodes
Identity-store change
Detail
Reinstall; site export and import with user mapping
Identity Migration
Detail
Fills Identity Service tables; does not change store type
CMT site scope
Detail
One source site per migration
Empty projects
Detail
Not migrated
Mapping order
Detail
First mapping that handles an identity wins
Missing destination user
Detail
Migration stops; rerun the plan
Custom script
Detail
Runs as a .cmd file
Sources for this section (10)
  • What does the account that signs in to CMT need on the source and on the destination?
  • Why is the Migration SDK not an option for moving content between two Tableau Server deployments?
  • When does a fresh installation with users republishing suit an identity-store change?
  • Why should no users or content be created on the fresh target installation before restoring the backup?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Tableau Architect pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 18 lessons of the Tableau Architect guide, with reading progress
  • Interactive decision walks and step-by-step sequence steppers
  • Practice exams purchase adds inline bank questions and topic practice (16 questions for this lesson)
  • An official source cited for every claim
  • An AI tutor that answers from the guide
  • Choose guide-only, practice-only, or save $4 with both

Practice for the Tableau Architect exam