After years of managing both environments at enterprise scale, here is our honest assessment of when to migrate to Tableau Cloud — and when to stay on Server.
The question we get asked most
After a decade running Tableau Server environments and managing Tableau Cloud migrations, we hear this question constantly: should we move to Tableau Cloud?
The honest answer is: it depends. And we are going to give you the actual framework we use to make that call, not the one Tableau's sales team would give you.
What Tableau Cloud is genuinely better at
Tableau Cloud has made significant strides since it was Tableau Online. The areas where it now legitimately wins:
**Maintenance overhead.** This is real. Server upgrades, patch management, infrastructure monitoring — these all disappear on Cloud. If your organisation does not have dedicated Tableau Server administration capacity, the operational savings are material.
**Automatic updates.** You are always on the current version. For most organisations, this is a feature, not a risk.
**Scalability.** Cloud scales elastically. If your usage spikes during reporting cycles, Cloud handles it without you having to plan capacity.
**Total cost at small scale.** Below roughly 50 users, the economics of Cloud are almost always better than Server once you factor in infrastructure and administration time.
Where Tableau Server still wins
**Data sovereignty and security requirements.** If your data cannot leave your network — financial services, healthcare, government — Server is often the only viable option. Cloud has improved its data residency options but it is not equivalent to on-premise control.
**Embedded analytics at scale.** If you are embedding Tableau in a customer-facing product at significant volume, Server economics are dramatically better than Cloud. The Cloud embedded licensing model can become very expensive very quickly.
**Complex authentication environments.** Kerberos, complex Active Directory configurations, legacy SAML implementations — these are all easier on Server. Cloud has improved, but integrating with complex enterprise identity infrastructure is still harder.
**Large-scale extract performance.** Very large extracts (50GB+) still perform more reliably on Server with dedicated hardware than on Cloud. This is improving but it is a real consideration for data-heavy environments.
**Custom data connectors.** If you rely on Tableau's custom connector SDK or community connectors that are not certified for Cloud, you may be stuck on Server until those connectors are updated or replaced.
The migration traps nobody warns you about
We have run dozens of Tableau Server to Cloud migrations. Here is what typically causes problems:
**Embedded credentials in workbooks.** Many Server environments have database credentials embedded in workbooks from years ago. Cloud handles credentials differently and requires credential clean-up before migration.
**Extract schedules.** Your carefully tuned extract refresh schedules do not transfer automatically. Plan to rebuild your schedule logic.
**Site configuration.** Server site configuration does not map 1:1 to Cloud. Authentication settings, guest access, and custom logos all need to be reconfigured.
**User onboarding.** Moving from Active Directory authentication on Server to SAML or SSO on Cloud requires coordination with your identity team and often affects more than just Tableau.
Our recommendation framework
Move to Cloud if: you have fewer than 100 users, no strict data residency requirements, limited internal IT capacity for Server administration, and no embedded analytics at scale.
Stay on Server if: you have strict security requirements, large extract volumes, complex embedded analytics, or heavily customised authentication infrastructure.
Hybrid is underrated: many organisations run Server for sensitive or high-volume workloads and Cloud for self-service analytics with lower compliance requirements. Tableau supports this and it is often the most pragmatic answer.
The migration process
If you do decide to migrate, the process we follow:
1. Audit your current Server environment — workbooks, users, data sources, extract schedules, and authentication configuration
2. Identify migration blockers — embedded credentials, unsupported connectors, compliance considerations
3. Plan your authentication architecture on Cloud — this is where most migrations hit unexpected complexity
4. Run a parallel environment during transition — do not cut over until Cloud is validated
5. Migrate content in phases by department or risk level
6. Decommission Server once Cloud is stable under real load
The migration itself is not technically difficult — it is the planning and the edge cases that determine whether it goes smoothly.
For context on the Server EOL timeline and what it means for your specific environment, Tableau Server end of life: what it means and what to do next covers the deadline, your options, and the decision framework. If Server performance is driving the conversation, Tableau Server performance tuning covers the diagnostic framework we use before recommending migration.
Our Tableau consulting team has run migrations on both sides of this decision — organisations that should have moved earlier and organisations that were pushed to Cloud before they were ready. If you are working through this decision, we are happy to talk it through. Book a free 30-minute audit and we will give you an honest assessment of which path makes sense for your specific environment.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →