A curated guide for a Tableau Server to Tableau Cloud Migration
Key takeaways
- Over 90% of net-new Tableau customers now choose Tableau Cloud, driven by innovation, ROI, security, and scale.
- A successful migration follows three phases: Preparation, Execution, and Validation & Monitoring.
- Small environments (under 20 workbooks) can migrate manually; larger ones should use Tableau’s Content Migration Tool (CMT), Migration SDK, or Migration App.
- Refresh schedules, permissions, and subscriptions do not carry over automatically and must be recreated in Tableau Cloud.
- Testing is the single most critical success factor: regression, performance, functional, and accuracy testing should all happen before and continue after go-live.
- Post-migration, ongoing monitoring is essential because Tableau Cloud auto-upgrades, which can introduce unannounced regressions.
Why Are Organizations Migrating to Tableau Cloud?
Tableau Server used to be the default deployment option, but that has flipped: today, over 90% of net-new Tableau customers choose to deploy on Tableau Cloud, and a growing share of existing Server customers are migrating too. According to Scott Smith, Senior Product Manager at Salesforce, four themes typically drive the decision.
Innovation
Tableau Cloud always runs the latest version, so capabilities, including Tableau AI features like Tableau Pulse and Tableau Agent, become available to your teams as soon as they’re released, with no upgrade project required.
Increased ROI
Moving to analytics as a service removes the burden of hosting and hardware costs. Organizations also report productivity gains from tools like Tableau Pulse, which increases the volume of data-driven decisions and the overall value extracted from analytics investments.
Security
Tableau Cloud inherits Salesforce’s Trust posture and unified security team, along with compliance certifications such as SOC 2 and HIPAA compliance, available to every customer simply by using the platform, without additional configuration.
Scale
Tableau Cloud runs on pods distributed globally, ensuring performance and resiliency regardless of where users are located. Instead of running IT capacity-planning cycles for new hardware, organizations can simply add users and have them running the same day.
The Three Phases of a Tableau Cloud Migration
A successful migration breaks down into three phases: Preparation (planning and readiness), Execution (the technical migration itself), and Validation & Monitoring (confirming everything works, and keeping it that way). Below is the full eight-step process.
Phase 1: Preparation
Step 1: Plan Your Migration
Before touching Tableau Cloud, work through this pre-migration checklist:
- Migration type: Decide between a full “lift & shift” or a partial migration. Either way, you’ll likely land on a newer Tableau version in the process.
- Multi-environment vs. single site: Tableau Cloud offers a single site, unlike Server’s multiple Dev/Test/Prod environments. Most organizations recreate that structure using project folders (multi-site is possible too, but requires a licensing conversation with Salesforce).
- Data sources: Inventory every database, application, and file source, and check which are supported by Tableau Cloud. On-premises sources need Tableau Bridge; cloud sources can often connect directly once whitelisted. Also check how many workbooks use embedded (rather than published) data sources.
- Authentication: Choose between Tableau’s built-in TableauID (with MFA) or your existing identity provider; IdP integration is required regardless of the SAML method (Okta, Salesforce, Google, etc.).
- Server extensions: Inventory all Tableau Server extensions in use and confirm they’re supported on Tableau Cloud.
- Content cleanup: Use Tableau Server’s “Stale Content” view to find unused workbooks, data sources, and flows before migrating; cloud storage isn’t free, and content untouched for 13+ months is generally safe to leave behind.
- Timelines: This is typically an IT-led project, not a business one. Align with business stakeholders on timing that minimizes disruption.
- Backup: Take a full backup of your Tableau Server content as a safety net before decommissioning anything.
Step 2: Identify Content and Its Elements for Testing
Before migrating, map out what needs testing after the fact, working with consumers, developers, and testers across the business:
- Operational reporting: mission-critical reports used for daily operations.
- Self-service dashboards: user-created dashboards in frequent use for analysis.
- Embedded analytics content: Tableau dashboards embedded in other applications or customer-facing portals.
Tableau Server Admin Views can help here, surfacing usage metadata like last-accessed date and view counts. For a fuller picture, some organizations combine Tableau’s Data Extract API with other data (such as access logs) to build custom usage views.
Once migrated, plan to test these specific elements of every dashboard:
- Visualizations (charts render correctly, no unintended formatting changes)
- Data representation (displayed data matches the underlying source)
- Worksheet structure (nothing has shifted that would affect the dashboard view)
- Functionality (interactions work as expected)
- Filter and parameter values (nothing was modified during migration)
- Performance (loading time under realistic scenarios)
Step 3: Create and Configure a Tableau Cloud Site
Site creation itself is handled by Tableau. From there, you’ll configure authentication, Bridge, extensions, integrations, connected apps, and mobile access — all well documented directly on Tableau’s website.
Phase 2: Execution
Step 4 — Migrate Data Sources and Workbooks to Tableau Cloud
Before migrating, make sure Tableau Bridge is set up for local data sources (cloud sources can connect directly). Note that Bridge-managed data sources must be published separately — they can’t be embedded in workbooks and won’t refresh automatically through Bridge.
There are two ways to move content, depending on environment size:
- Manual migration — for small environments (under 20 workbooks), download each workbook from Tableau Server and upload it to Tableau Cloud individually.
- Content Migration Tool (CMT) — for larger environments. This requires admin permissions on both Server and Cloud, and a location with access to both. The CMT moves sites, projects, and workbooks, but has known limitations moving users, groups, site settings, project permissions and locked states, and subscriptions — and can struggle with very large object volumes.
Data extract schedules do not carry over from Tableau Server to Tableau Cloud. As you migrate projects, pay close attention to workbooks with embedded data sources (this is a good moment to repoint them to a new source) and to your published data sources generally.
Step 5 — Recreate Refresh Schedules for Tableau Cloud
Since refresh schedules don’t transfer automatically, you’ll need to recreate them in Tableau Cloud for every data source and workbook that requires one — matching the original frequency, day, and time as closely as possible. Depending on the source type, Tableau Bridge may be required to maintain live connections to on-premises data.
Two items are easy to overlook at this stage:
- Tableau Prep Flows — check that any scheduled flow tasks have migrated correctly.
- Workbook subscriptions — confirm subscriptions carried over so users keep receiving their scheduled workbooks.
Step 6 — Configure Permission and Content Access for Migrated Users
Migrating users is only half the job — they also need access to the right content. If permissions didn’t transfer cleanly, work through the following:
- Pre-defined roles: use Tableau Cloud’s built-in site roles (Viewer, Explorer, Analyst, Publisher) for a fast baseline.
- Granular control (optional): set permissions at the project, workbook, or data source level for finer-tuned access.
- Project access: assign users to the relevant projects — they’ll only see content within projects they belong to.
- Content sharing (optional): let content owners share specific workbooks or data sources directly with users or groups.
- Row-level security: revisit and re-validate RLS permissions and calculations post-migration.
Phase 3: Validation & Monitoring
Step 7 — Test and Validate Your Migration
Once migration is complete, the priority shifts to testing — proving, with documented results, that the move was successful. Tableau typically allows Server and Cloud to run side by side during this period, which makes direct comparison possible.
Side-by-side regression testing
Comparing Server and Cloud content directly helps surface:
- Visual differences
- Worksheet data differences
- Metadata differences (filter types and values, parameter types and values, column counts, etc.)
- Functional issues (e.g., dashboards failing to open)
Results should be documented to justify the migration’s accuracy, and dashboards should be certified once they pass — reinforcing reliability and stakeholder trust.
Performance testing
After confirming a dashboard opens, performance is usually the next thing users notice. Business stakeholders will expect Tableau Cloud to match — or beat — Tableau Server’s speed, so performance testing against defined SLAs is essential.
Functional testing
Confirm dashboards and views open successfully, refresh correctly, and that filter, parameter, and mark selection navigation all behave as expected.
Accuracy testing
Three checks matter most here:
- Comparing visualized data against the backend database tables
- Validating both aggregate and row-level data against defined business rules
- Confirming users only see the data they’re authorized to see
Content certification or decertification
Business stakeholders need confidence that dashboards remain accurate, current, and reliable after migration. Dynamic certification — and decertification when something breaks — lets teams get ahead of errors before stakeholders notice them. Two levels typically apply: certifying data sources for developers/Creators, and certifying dashboards for the broader base of content consumers.
Step 8: Post-Migration Continuous Monitoring
Completing the migration is a milestone, not a finish line. Tableau Cloud applies upgrades automatically, which means new functionality can arrive without warning, and occasionally with unintended regressions. Ongoing testing (daily, weekly, or on whatever cadence fits your organization) should focus on:
- Data integrity and accuracy: confirming dashboards and data sources continue populating correctly, including through SQL-based testing against sources like Snowflake, Databricks, or CSV.
- Performance optimization: validating SLA adherence under realistic concurrent-user load.
- Dashboard functionality validation: checking filters, parameters, and custom calculations after every forced upgrade.
- Regression testing: comparing dashboards before and after each Cloud upgrade, since these are largely outside your control.
- Regulatory compliance: verifying security settings and access permissions remain correctly applied; Tableau Cloud’s Admin Insights tool helps track user roles and sign-in activity.
Tableau’s Native Migration Tools
Tableau Migration SDK
Released in early 2024, the Migration SDK lets technical teams automate and customize their own migration process for moving users, groups, content (data sources and workbooks), and governance structures into Tableau Cloud. It’s built for teams comfortable working with Python and .NET, and, like any migration path, still requires dedicated post-migration data validation, which Tableau doesn’t natively automate at scale.
Tableau Migration App
Released in late 2024 in response to customer feedback, the Migration App is an open-source tool aimed at organizations with smaller environments that lack the technical depth to use the SDK directly.
Tips & Tricks for a Successful Tableau Cloud Migration
Benny Benford, former CDO at Jaguar Land Rover, shared these lessons from leading a real-world Server-to-Cloud migration.
- Focus on the value the migration brings, not just performance. Teams often over-index on platform performance and usage concerns. Let Tableau own performance, and keep your own focus on the value the data delivers to the organization.
- Engage with your community. Use the migration as an opportunity to ask users about their frustrations. You won’t be able to fix everything, so avoid overpromising, but involvement itself builds goodwill.
- Take the opportunity to restructure. Jaguar Land Rover used their migration to redesign their site structure and security model, informed by years of accumulated Tableau experience and direct community feedback.
- Test, test, test. Migrating without testing leaves you with no way to confirm anything actually works as intended.
- Make the community part of the migration. Frame it as: “you told us about problem X, we’re fixing it, but we need your help testing it.” Involving users in testing builds ownership and surfaces issues you’d otherwise miss.
How Wiiisdom Supports a Tableau Cloud Migration
Wiiisdom for Tableau provides automated validation, certification and decertification, and continuous monitoring at scale, designed to catch and resolve issues before business stakeholders ever notice them. In practice, that means:
- Defining testing strategies: planning test complexity and cadence (hourly, daily, weekly, monthly).
- Continuous testing: combining automated testing, monitoring, and CI/CD integration for faster development cycles and earlier issue detection.
- Real-time alerting: via Email, Slack, Microsoft Teams, or webhook integrations, so teams can troubleshoot proactively.
- Historical tracking: documenting test rules and results over time, which supports audits and regulatory requirements while surfacing longer-term trends.
Frequently Asked Questions
1. Do Tableau Server refresh schedules carry over to Tableau Cloud?
No. Refresh schedules do not automatically migrate. Each data source or workbook that needs refreshing must have its schedule recreated manually in Tableau Cloud, matching the original frequency, day, and time.
2. What's the difference between the Content Migration Tool, the Migration SDK, and the Migration App?
The Content Migration Tool (CMT) is built for larger environments and moves sites, projects, and workbooks, though it has limitations around users, groups, and permissions. The Migration SDK, released in 2024, lets technical teams (using Python and .NET) build a fully custom migration process. The Migration App, released later that year, is an open-source tool aimed at smaller organizations without the technical resources to use the SDK directly.
3. How do you migrate a small Tableau environment to Tableau Cloud?
For environments with fewer than 20 workbooks, manual migration is usually simplest: download each workbook from Tableau Server and upload it directly to Tableau Cloud. Larger environments should use the Content Migration Tool, the Migration SDK, or the Migration App instead.
4. What should you test after migrating to Tableau Cloud?
Four types of testing matter most: regression testing (comparing Server and Cloud side by side), performance testing (against defined SLAs), functional testing (dashboards open, refresh, and respond to filters/parameters correctly), and accuracy testing (validating data against the source and against access rules).
5. Why does testing need to continue after the migration is complete?
Tableau Cloud applies upgrades automatically, and organizations can’t control when those upgrades happen. New functionality can occasionally introduce regressions, so ongoing testing, data integrity, performance, functionality, and regression is necessary to catch issues before they reach business stakeholders.