A Tableau Cloud migration is the process of moving your analytics environment from a self-hosted Tableau Server deployment to Tableau's fully managed SaaS platform. It involves transferring your workbooks, data sources, users, permissions, and configurations to the cloud — and, when planned correctly, it can be completed in days rather than weeks.
This guide covers everything you need to know: from assessing readiness and planning your approach, to choosing the right tools and avoiding the most common pitfalls.
What is a Tableau Cloud migration?
Tableau Cloud (formerly Tableau Online) is Salesforce's fully managed, cloud-hosted version of Tableau. Unlike Tableau Server — which your IT team installs, maintains, and upgrades on-premises or in a private cloud — Tableau Cloud is a SaaS product. Salesforce handles all infrastructure, updates, backups, and performance tuning on your behalf.
A Tableau Cloud migration is the act of transitioning from that self-managed model to the fully hosted one. In practice, this means moving your content (workbooks, data sources, Prep flows), your users and permission structures, and your operational configurations (schedules, subscriptions, authentication) from Tableau Server to a new Tableau Cloud site.
The scope and complexity of that move depends heavily on your environment size. A small team with 50 users and 100 workbooks faces a very different challenge than an enterprise running 2,500 users across multiple sites. Your migration plan — and the tools you choose — should reflect that reality.
Why migrate to Tableau Cloud? Key benefits
The reasons for a Tableau Cloud migration goes well beyond "it's in the cloud." Organizations making the switch are reporting meaningful operational and strategic gains.
No more server management. With Tableau Cloud, there is no hardware to refresh, no upgrade cycles to plan, and no patches to apply. Tableau is always running the latest version — including new features like Tableau Pulse and Tableau AI — available to your users the moment they ship. For IT teams spending significant time keeping the lights on, this alone justifies the move.
Predictable, scalable costs. Tableau Cloud converts capital expenditure into a predictable operational subscription. You eliminate the hardware, the sysadmin overhead, and the cost of unplanned downtime. According to Tableau's own migration data, customers like Splunk have saved $300,000 per year in platform administration after migrating — alongside a 2x improvement in dashboard performance.
Automatic scalability. Tableau Cloud adapts to your user load and workbook complexity without any intervention required. There is no need to size servers ahead of demand spikes or over-provision capacity as a buffer.
Reduced environmental impact. Migrating from a self-hosted deployment to Tableau Cloud can reduce your carbon footprint by more than 80% — a meaningful consideration for organizations with sustainability commitments.
Access to the future of analytics. Tableau's AI-powered features and innovations are delivered to Tableau Cloud first. Organizations still on Tableau Server are waiting longer and longer to access capabilities their cloud-native competitors already use daily.
Are you ready? How to assess migration readiness
Before you move a single workbook, you need to know whether your environment is actually ready for Tableau Cloud. Most organizations are — but there are specific scenarios where migration requires extra planning, or where it may not yet be the right move.
Check your data connectivity options
This is the most common readiness blocker. Tableau Cloud connects directly to cloud-based data sources — Snowflake, Databricks, Google BigQuery, Salesforce, and others — without additional setup. But if your data lives on-premises (SQL Server behind a firewall, local Oracle databases, internal Excel files), you will need to configure Tableau Bridge: a lightweight application installed inside your network that creates a secure connection between your private data and Tableau Cloud.
Tableau Prep Flows that rely on on-premises data via Bridge require careful evaluation — not all flow types are supported in that configuration.
Review your authentication requirements
Tableau Cloud supports SAML-based SSO and integrates with identity providers including Azure AD, Okta, and OneLogin for automated user provisioning. However, if your organization relies on LDAP or Kerberos authentication, these are not currently supported by Tableau Cloud. That is a hard blocker until your authentication strategy is updated.
Audit your content and users
Run Tableau Server's built-in admin views to identify stale content — workbooks that haven't been accessed in six months or more are prime candidates for archiving rather than migrating. This is also the moment to review your user base: who is active, what roles they hold, and how permissions are structured across projects.
Tableau provides a Cloud Migration Technical Readiness Assessment to help identify assets that need adaptation before you migrate. Use it early.
Compliance and hosting considerations
Tableau Cloud currently runs exclusively on Amazon Web Services. If your organization has policies restricting AWS-hosted products, or if you operate under FedRAMP compliance requirements, you are not presently a candidate for standard Tableau Cloud migration. Contact your Tableau account team for current guidance on these cases.
How to plan a Tableau Cloud migration: Step-by-Step
A successful Tableau Cloud migration follows a clear, staged process. Rushing any phase — especially planning and validation — is where projects run into trouble.
Step 1: Inventory your Tableau Server environment.Catalog everything: workbooks, published data sources, Prep flows, users, groups, permission sets, projects, subscriptions, and scheduled extract refreshes. Document dependencies between workbooks and data sources. This inventory becomes your migration manifest — and reveals surprises you didn't know were there.
Step 2: Define your data connectivity strategy.For each data source in your inventory, determine how it will connect to Tableau Cloud. Cloud-native sources are straightforward. On-premises sources need a Tableau Bridge deployment plan. Flag any data sources that use Web Data Connectors — these require Bridge in Tableau Cloud and need individual validation.
Step 3: Set up and configure your Tableau Cloud site.Work with your Tableau account manager to transition your licensing from Server to Cloud. You receive 60 days of concurrent access to both environments — enough runway for a thorough migration. Configure authentication, set up your project structure, and create initial user accounts in Tableau Cloud before content arrives.
Step 4: Clean up stale content.A migration is the best forcing function for a content audit you've been putting off. Archive or delete unused workbooks and data sources before migrating. Fewer objects means faster migration, less noise in your new environment, and a cleaner starting point for governance on Tableau Cloud.
Step 5: Migrate content, users, and permissions.This is where your chosen migration approach matters enormously (more on that in the next section). Content needs to move with its permissions, data source connections, and metadata intact. Users need to land in Tableau Cloud with the right roles and access to the right projects. Subscriptions and schedules need to be recreated or migrated. Each of these is straightforward in isolation — the complexity is doing them all correctly, at scale, without breaking things for your users.
Step 6: Validate and hand over to end users.Before decommissioning Tableau Server, validate that dashboards render correctly, data connections are live, extract schedules are running, and user access matches what was in place on Server. Give end users a clear cutover date and communicate what — if anything — they need to do on their end (recreate custom views, update saved credentials, etc.).
Manual migration vs. automated tools: What's the difference?
The honest answer: manual migration works for small, simple environments, and becomes increasingly painful — and risky — as complexity grows.
Tableau's own manual migration guide is designed for deployments with fewer than 100 users. For those teams, a self-service approach is feasible: administrators download workbooks from Server, re-publish them to Cloud, reconnect data sources, and recreate schedules one by one. It takes time, but it is manageable.
For anything beyond that — multiple sites, complex permission hierarchies, hundreds of workbooks, embedded credentials, or large user bases — manual migration creates serious risk. A single missed permission configuration can silently break row-level security for an entire group of users. Recreating subscriptions and schedules by hand at scale is error-prone and time-consuming. And extended migration timelines mean extended periods where two environments need to stay in sync, multiplying the administrative burden.
That is the gap that purpose-built migration tools were designed to fill.
How TabMove accelerates your Tableau Cloud migration
TabMove, developed by Biztory — Tableau's #1 partner in EMEA — is the leading dedicated migration tool for Tableau Cloud. It automates up to 90% of migration tasks, handling the movement of workbooks, data sources, users, groups, permission sets, projects, subscriptions, and scheduled jobs from Tableau Server to Tableau Cloud with minimal manual effort.
The results speak for themselves. TVH — a global parts specialist with 2,500 users, 2,000 workbooks, 450 data sources, and a hierarchy of 250 projects across multiple sites — completed their entire Tableau Cloud migration in a single day using TabMove, saving 80 working days compared to a manual approach. Veygo, a UK insurer under Admiral Group, completed a migration that would have taken six weeks internally in just a few days.
TabMove follows a proven four-stage methodology:
- Assess — A comprehensive audit of your Tableau Server environment identifies active content, redundant assets, and dependencies that could complicate the move.
- Plan & Map — Users, permissions, and project structures are mapped to Tableau Cloud's architecture, ensuring continuity of access and metadata consistency.
- Migrate — Automated migration moves content and configurations to Tableau Cloud efficiently, with minimal disruption to end users.
- Validate — Post-migration validation confirms dashboards render correctly, data connections are live, and refresh schedules are functioning as expected.
For a deeper look at how TabMove compares to other migration approaches, see The best Tableau Cloud migration tools in 2026.
Common challenges and how to avoid them
Even well-planned migrations encounter obstacles. These are the ones that catch teams most often.
Data source dependencies. Workbooks that reference published data sources need those data sources to be migrated first — and in the right sequence. Migrating workbooks before their underlying data sources are live on Tableau Cloud results in broken connections that need to be manually repaired. Map your dependency chain before you begin.
Permission structure complexity. Permissions in Tableau are inherited, nested, and can behave differently depending on project configuration. Organizations that have customized permissions over years of Tableau Server use often discover inconsistencies during migration. A pre-migration permissions audit — and the use of an automated tool that migrates permissions as part of a structured workflow — prevents most of these issues from surfacing post-go-live.
Authentication mapping. Usernames on Tableau Server may not match the email-based identity expected by Tableau Cloud, especially when moving from Active Directory authentication to SAML-based SSO. TabMove handles AD username-to-email mapping as part of its migration process — this is one of the areas where manual migration is most error-prone.
Change management and user adoption. A technically flawless migration can still feel like a failure if users are confused or unprepared. Communicate the migration timeline early. Explain what users need to do (if anything) when they first log in to Tableau Cloud. Identify power users who can act as internal champions. The 3 Reasons to migrate from Tableau Server to Tableau Cloud explores the organizational side of this transition in more detail.
Frequently Asked Questions
How long does a Tableau Cloud migration take?
It depends on the size and complexity of your environment. Small deployments with fewer than 100 users typically complete migration within a week using a manual approach. Larger organizations using automated tools like TabMove have completed migrations of thousands of workbooks and users in a single day. The planning phase — inventory, readiness assessment, data connectivity strategy — typically takes one to three weeks regardless of deployment size, and should not be rushed.
What gets migrated automatically vs. what needs to be recreated?
Workbooks, published data sources, users, groups, projects, permissions, subscriptions, and scheduled extract refreshes can all be migrated — either manually or via a tool like TabMove. Items that typically need to be recreated manually include custom views, Ask Data lenses, favorites, collections, saved credentials, dashboard extension configurations, and webhooks. Row-level security rules using user or group names may also need updating if those identifiers change during migration.
Do I need Tableau Bridge after migrating to Tableau Cloud?
Only if you have on-premises or private network data sources. Tableau Cloud connects directly to cloud data platforms (Snowflake, BigQuery, Databricks, Salesforce, and others) without Bridge. If your organization's data lives behind a firewall — on-premises SQL Server, local Oracle databases, or internal file stores — you will need to install and configure Tableau Bridge within your network to maintain live connectivity.
Is Tableau Cloud right for every organization?
Most organizations are strong candidates, but there are exceptions. If your compliance framework requires FedRAMP authorization, or if organizational policy prevents using AWS-hosted products, you are not currently a fit for standard Tableau Cloud. Similarly, if your environment relies heavily on LDAP or Kerberos authentication, you will need to update your identity strategy first. For everyone else, the operational and financial case for Tableau Cloud is compelling — and getting stronger as Tableau continues to prioritize cloud-first feature development.
