Use case – Tableau Cloud Migration
Reach for the sky. Migrate to Tableau Cloud without losing a number.
Moving from Tableau Server to Tableau Cloud opens real doors. It also puts every workbook you own onto a platform that behaves slightly differently, and most of what changes is invisible. Wiiisdom compares the two environments side by side, so you commit to the cutover on evidence rather than on optimism.
Trusted by more than 600 leading companies and organizations
Dimensions that matter most for a Cloud migration
What it does
Commit to the cutover on evidence, not on optimism.
Compare the two environments, side by side
Wiiisdom provides automated regression testing with side-by-side comparison between your Server environment and your Tableau Cloud target. Every difference in data, layout, performance and access is surfaced and isolated, workbook by workbook, so the migration is validated rather than sampled.
Prove the success to stakeholders and auditors
Once the migration is over you will be asked to demonstrate it worked. Document your test cases and the results of their execution, confirm you meet SLA requirements, and show that performance is at least equal, data accurate and complete, security validated, and behaviour unchanged. The evidence is a by-product of the testing, so it exists when the question is asked.
Recycle the tests, and stay ahead of what comes next
On Tableau Cloud, upgrades stop being events you schedule and become releases you receive. The pipelines you built to validate the migration are the same that protect you from every forced upgrade afterwards. The migration is not the end of the testing programme, it is what pays for it.
Take the validation burden off your people
Manual dashboard checking is the hidden cost of every migration, and it lands on the developers and business users who have other work. Automating it relieves them of the task while reassuring them of the result, and removes the largest variable cost in the validation phase.
Wiiisdom is recommended by Tableau for Tableau Cloud migrations
“Provides validation capabilities that are extremely useful in reassuring business stakeholders.”
Ali Tore, former SVP Advanced Analytics at Tableau
What we test
Five things you need to test for a successful migration
Data accuracy and completeness
Measures and marks compared against a pre-migration baseline, workbook by workbook, on the Cloud target.
Render and query performance
Response times measured on Cloud against your Server figures, with Apdex scores held to your SLA.
Permissions and row-level security
Access re-verified per user profile, because the Cloud permission and site model is not the Server one.
Functional behaviour
The view opens, and filters, parameters and actions behave as they should on the new platform.
Visual and layout parity
Sheets present, positions consistent, visual elements intact after the move.
How it works
Four steps, before and after the cutover
Step 01
Baseline on Tableau Server
Capture results, performance and access behaviour on the environment you are leaving, workbook by workbook. This is the reference the Cloud environment will be measured against.
Step 02
Compare side by side
Run the same pipelines against the Cloud target and compare. Wiiisdom highlights every difference in data, performance, access and layout, and isolates it to the asset.
Step 03
Remediate and re-test
Work through the differences, fix, and re-run until the estate is green. Nothing goes to cutover on a partial result.
Step 04
Keep the pipelines running
After go-live, the same pipelines become your defence against forced Cloud upgrades, and your evidence trail for compliance.
The payoff
From a cutover you hope went well to one you can demonstrate went well.
Tableau Server-to-Cloud migrations rarely fail visibly. They fail as a few measures that no longer reconcile, a set of dashboards that got slower, and permissions that did not survive the change of model. All three are findable before the cutover, and none of them are findable by sampling.
- A subset of dashboards is checked by hand, because checking all of them is not feasible
- Discrepancies surface after go-live, when a business user disputes a figure
- Nobody knows whether Tableau Cloud is faster or slower until users say so
- Permissions are assumed to have survived the move to the Tableau Cloud site model
- When the first forced upgrade lands, the validation work starts again from nothing
- Every workbook compared side by side, Tableau Server against Tableau Cloud, automatically
- Discrepancies found and remediated before cutover, not after
- Render and query performance measured on Cloud against the Server baseline
- Permissions and row-level security re-verified per user profile on the new model
- The same pipelines re-run on every forced upgrade, so the work compounds instead of repeating
Keep exploring