Scope argued from evidence
Move what is used. Archive what is not, with the usage to back it.
What actually has to move, and what breaks on the way
A Server to Cloud migration is rarely blocked by the content. What hangs off the content blocks it: extract schedules, subscriptions, permissions, custom views, and the connections that only worked because of where the Server sat.
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.
Know the shape before you commit
A read-only inventory shows what exists, who owns it, what is still used, and what has no owner at all. You get it before any decision about scope.
- Usage read from the site before scope is agreed
- Ownership resolved, including the content nobody has claimed
- Everything stays where it is during discovery
The things that do not travel
Custom views, subscriptions, alerts and schedules turn a migration into a support queue. They are listed first, before a user finds them on the Monday.
- Custom views listed per workbook and per owner
- Schedules and subscriptions listed with their owners
- Connection changes named before the cutover
Approve every step
The migration engine wraps the official Tableau Migration SDK. Every stage is a plan, and a person approves it.
- Built on the official migration SDK, not a rebuild
- Each stage approved, each stage recorded
- A record of what moved, for the questions that follow
What changes
Fewer Monday surprises
The attachments are listed before the cutover.
A record of the whole move
What moved, when, and who approved it.
Run the inventory first
Connect a site read-only. See what a migration would really involve.