Migrating from Tableau Server to Tableau Cloud: What to Expect and How to Do It

The quick answer

Migrating from Tableau Server to Tableau Cloud involves moving your published content (workbooks, data sources, flows), user accounts, permissions, scheduled extracts, and governance settings to Salesforce-managed cloud infrastructure. The migration itself is manageable with the right tooling (Tableau Content Migration Tool). What requires more planning is addressing the feature gaps between platforms, the data connectivity changes (no direct database access from Tableau Cloud without a Tableau Bridge), and the licensing cost change. Most organisations complete the core migration in 3–6 months; full parity and optimisation takes 6–12 months.

Why organisations are migrating now

Tableau Server end-of-life (announced for 2027 with Tableau Desktop and Prep aligning to similar timelines) removes the extended support path for on-premise Tableau. Salesforce's strategic investment is in Tableau Cloud — new features (AI-powered analytics, Pulse, Salesforce integration) are being built for Cloud first or Cloud only. Organisations on Server are increasingly on a diverging path from the product roadmap.

Separately, the operational overhead of running Tableau Server — patching, upgrades, hardware, the RMT (Resource Monitoring Tool), backgrounder management — has become expensive to justify as Cloud pricing has become more competitive. The removal of server administration is a meaningful operational cost reduction for many IT teams.

What the migration involves

**Content migration**: workbooks, published data sources, flows, and metrics move from Tableau Server to Tableau Cloud using the Tableau Content Migration Tool (CMT). CMT runs on a machine with access to both the source Server and the target Cloud site. It handles workbook republication, permission mapping, and project structure migration. CMT does not migrate all settings automatically — custom SSL certificates, SAML configurations, and some server-level settings require manual reconfiguration.

**User migration**: users are recreated in Tableau Cloud with the same roles (Creator, Explorer, Viewer) and permissions. If your organisation uses Salesforce Identity, Google Workspace, or another identity provider for SSO, configure that integration before migrating users. User passwords are not migrated — users log in with SSO or set new Tableau Cloud passwords.

**Permissions and groups**: CMT migrates project permissions and content permissions. Group structures need to be recreated or imported from your identity provider via SCIM provisioning. Review permissions carefully post-migration — Server-to-Cloud mapping is not always 1:1 for complex permission configurations.

**Scheduled extract refreshes**: extract refresh schedules are migrated, but the schedules available in Tableau Cloud differ from Server (Cloud offers fixed schedule options; Server allows fully custom cron-style schedules). Review any non-standard refresh schedules before migration.

**Flows**: Tableau Prep Flows migrate but require Tableau Prep Conductor (included in Creator licences) for scheduling. Flows that write output to file locations on the Server (local paths) need to be reconfigured to write to cloud storage (S3, GCS, SharePoint) or Tableau Cloud's built-in storage.

Data connectivity — the most complex part

Tableau Cloud does not have direct network access to on-premise databases or databases in private VPCs/VNets. This is the migration challenge most commonly underestimated.

**Tableau Bridge**: Tableau Bridge is a client application that runs on a machine with network access to the private data source and establishes an outbound connection to Tableau Cloud. Extract refreshes and live queries for private data sources route through Bridge. Bridge must be installed, configured, and maintained on a machine (or multiple machines for redundancy and load balancing) with persistent access to the private network.

**Cloud-hosted databases**: for data already in cloud services with public endpoints (Snowflake, BigQuery, Redshift with public access, AWS RDS in a public subnet, Azure SQL Database), no Bridge is required — Tableau Cloud connects directly. Migrating your data sources from on-premise to cloud-hosted databases (if not already done) removes the Bridge dependency entirely.

**Published data sources**: published data sources with live connections that pointed to Server's LAN-accessible databases need to be reconfigured to either use Bridge (if staying on-premise databases) or updated connection strings (if moving to cloud databases). This is typically the most labour-intensive part of the migration.

**OAuth connectors**: Tableau Cloud supports OAuth for Google BigQuery, Snowflake, Azure Synapse, and other cloud databases. OAuth connections are more secure than embedded credentials and simpler to manage than Tableau Bridge for cloud data sources. Configure OAuth connections as part of the migration.

Feature gaps to plan for

Tableau Cloud does not have all Tableau Server features. Key gaps as of 2025–2026:

**Custom geocoding**: Tableau Server supports custom geographic roles and custom geocoding files. Tableau Cloud has limited support for custom geocoding — plan alternatives if your dashboards use custom geo shapes or geographic roles not in Tableau's default set.

**Extensions that require server-side execution**: some Tableau Dashboard Extensions and Viz Extensions have dependencies on server-side infrastructure. Validate all extensions used in your dashboards are compatible with Tableau Cloud.

**SMTP email customisation**: Tableau Server allows full SMTP configuration for subscription emails, including custom from addresses and email domains. Tableau Cloud has more limited email customisation — subscriptions come from Tableau Cloud's email domain.

**Certain REST API capabilities**: some Tableau Server REST API endpoints have no equivalent in Tableau Cloud. If you have automation built on the REST API, audit against the Tableau Cloud REST API documentation before migrating.

**Site management**: for organisations using multiple Tableau Server sites, each migrates to a separate Tableau Cloud site. Cross-site content sharing and some multi-site administration capabilities differ between platforms.

Licensing and cost

Tableau Cloud is typically licensed per role per year: Creator (~$70/user/month), Explorer (~$42/user/month), Viewer (~$15/user/month). Tableau Server is licensed per core (for on-prem) or per-user in a SaaS model. The total cost comparison depends heavily on user count, licence mix, and current Server infrastructure costs.

For organisations currently running Tableau Server on-prem, cloud hosting cost elimination often partially offsets Cloud licence cost increases. For organisations on Tableau Server hosted in a cloud VM, the total cost comparison is more direct — model both scenarios at your actual user counts.

Tableau offers migration incentives periodically for customers committed to moving from Server to Cloud — engage your Tableau account team before purchasing Cloud licences independently.

Migration timeline

**Months 1–2**: assessment and planning. Inventory content (workbook count, data source count, flow count, user count). Assess data connectivity (identify all private data sources, plan Bridge deployment). Identify feature gaps. Set up a Tableau Cloud trial site.

**Months 2–3**: pilot migration. Migrate a subset of workbooks (30–50 non-critical dashboards), configure one data source, migrate a user group. Validate functionality, identify issues, refine the process.

**Month 3–5**: bulk migration. Migrate remaining content in phases by business domain or team. Run Server and Cloud in parallel — users can continue using Server while Cloud is being validated. Establish Bridge infrastructure for private data sources.

**Month 5–6**: cutover. Redirect users to Tableau Cloud as their primary platform. Decommission Tableau Server or enter maintenance-only mode pending full cutover validation.

For the broader Tableau Server context and end-of-life planning, see tableau server end of life. For post-migration cost management, see tableau cloud migration cost. For Server administration concepts that translate to Cloud, see tableau server admin guide.

Our Tableau consulting practice manages Server-to-Cloud migrations — from content inventory and connectivity assessment through CMT-based migration, Bridge configuration, and user cutover. We have migrated environments ranging from 50 to 2,000+ published workbooks. Book a free 30-minute audit to scope your migration.

A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.