Skip to content
NewNeenOpal Earns ISO 42001 Certification for AI GovernanceKnow More

Tableau Cloud Migration Services Delivered Without Breaking a Report

NeenOpal is a certified Tableau Partner. We migrate Tableau Server to Tableau Cloud end-to-end, covering content, data connectivity, identity, and refresh schedules, checking each one against your live Server environment before a single report goes live.

How it works

What a Tableau Server to Tableau Cloud Migration Involves

Migrating from Tableau Server to Tableau Cloud touches content, data connectivity, identity, and scheduling as one connected process, each with its own way of breaking if it's rushed. We map that risk upfront, for the leads who drive this move ahead of a licensing renewal or version end-of-life. Here are the Tableau Server to Cloud migration steps we run, and why.

  • 01

    Assess readiness

    Run the Tableau Cloud Migration Readiness Assessment to confirm your data sources, compliance posture, and authentication model are compatible with Tableau Cloud before a single item moves.

  • 02

    Transition your licensing

    Convert your perpetual or core-based licenses to role-based subscription licensing and run both in parallel for 60 days while you switch. Extendable through your Account Manager.

  • 03

    Configure the Cloud site

    Set up authentication (SAML or OIDC with Okta, Azure AD, or another supported identity provider), multi-factor authentication, project structure, and site settings.

  • 04

    Migrate virtual connections

    Virtual connections don't export and import directly. We manually recreate each one on Tableau Cloud so nothing breaks.

  • 05

    Migrate content

    Download workbooks and data sources from Tableau Server and republish them to Tableau Cloud, automating the process for larger content libraries.

  • 06

    Recreate refresh schedules

    Extract refresh schedules don't carry over automatically. We rebuild each one natively inside Tableau Cloud, so refreshes keep running on time.

  • 07

    Provision users and permissions

    Provision users via SCIM, SAML, or manual import, and reconfigure site roles and permissions in the new site to match your governance model.

  • 08

    Hand off to end users

    Guide users through reconfiguring personal items like webhooks, subscriptions, embedding, and API scripts that don't migrate automatically.

Outcomes

Outcomes Enterprise Leaders Measure Us By

Financial Impact Delivered to Clients
$750M+
Of engagements reached North Star outcomes within 90 days
85%
Average cloud cost savings across client operations
60%
Tableau dashboards delivered by 30+ certified Tableau experts
900+

Decision frame

Where Tableau Migrations Break, and How We Fix It

Most Tableau Server to Cloud migrations start for one of two reasons. Either because staying on Server costs too much in licensing, or because a Server environment stops delivering expected outcomes. That business case is usually the easy part. The bigger risk sits in the technical details below where a self-run migration loses the most time.

AreaWhat breaksHow we de-risk it
Data connectivityCube data sources, Kerberos DB auth, and .taco custom connectors are unsupported on Tableau Cloud; Prep flows over Bridge can't reach flat filesMap every source to the Cloud connector/Bridge support list before starting, and move any flat-file inputs to cloud storage first.
AuthenticationActive Directory, Kerberos and LDAP are not supportedReplace with a cloud IdP (Azure AD via SAML, Okta) before migrating content.
MFAUsers used to no MFA get blockedConfigure SSO or TableauID with MFA early and communicate in advance.
API & automationServer-level REST APIs, Web Data Connectors and Exchange connectors don't carry over; API auth must move to PATsAudit and refactor all scripts before cutover.
IP allowlistsTableau Cloud moved to Salesforce Hyperforce (Aug 2024–Apr 2025), changing IPs; stale allowlists break connections.Update firewall/data-provider allowlists with current Hyperforce IPs before go-live.
PerformanceCloud is multitenant; other tenants on the same pod can affect performanceOptimise slow dashboards on Server before migrating. They won't improve automatically once they're in Cloud.
Admin observabilityDirect PostgreSQL repository access doesn't exist in CloudRebuild admin views using Admin Insights; consider Advanced Management for 365-day retention.
LicensingLegacy perpetual/core-based licenses and Guest access are unsupportedConvert to role-based subscription and replace Guest access with Connected Apps ahead of time.

Which tool should you use to migrate Tableau Server to Tableau Cloud?

For Server-to-Cloud moves, Tableau recommends the Tableau Migration SDK or the Cloud Migration App. The Content Migration Tool is meant for Server-to-Server or Cloud-to-Cloud transfers and isn't recommended for Server-to-Cloud. Because the SDK relies entirely on the REST API, any content type without REST API support has to be migrated manually.

Manual work

Beyond the SDK: What We Migrate Manually

Some items simply can't be automated, so we migrate them manually. Here's how we handle each of the six categories:

  • Governance & structure

    We manually rebuild collections, site/server customizations, data policies, and data roles against your new Cloud governance model.

  • Automation & interactivity

    We reconfigure and retest data-driven alerts, URL actions, and extensions once content is live on Cloud.

  • Virtual connections & Prep flows

    We recreate these natively in Cloud as part of the migration as the SDK doesn't carry them over.

  • Collaboration history

    Comments, revisions, saved user filters, and personal settings reset for end users on Cloud. We flag this before cutover so it doesn't land as a surprise support ticket later.

  • Personal spaces

    The SDK skips these unless they're published to a project first. We coordinate with your team so owners publish before migration day.

  • Usage, quality & embeds

    We rebuild usage/engagement history and data-quality warnings via Admin Insights, and re-point embedded solutions to Cloud URLs and authentication.

Meet the team

The People Behind Your Tableau Server to Cloud Migration

NeenOpal is a certified Tableau Partner, with 30+ certified Tableau experts who've delivered 900+ Tableau dashboards for enterprise clients. Hear directly from the analytics and cloud engineers at NeenOpal on what building and maintaining enterprise data platforms actually takes.

Timeline

Tableau Server to Cloud Migration Timeline

Under 100 users, Tableau's manual path takes one to two weeks, from assessing readiness to handing off to end users, with 60 days of dual access to both environments while you switch. Larger, more complex estates run for several weeks to months.

Tableau Cloud migration timeline: a Week 1 to Week 2 schedule from Assess Readiness through Configure Cloud & Licensing, Migrate Content & Connections, Provision Users & Permissions, to Hand Off to End Users, with a 60-day license dual-access window and go-live flag

Case studies

Related Case Studies

Client reviews

What clients say about working with us

Each member of the team is interested and knowledgeable about the process!

NeenOpal Intelligent Solutions is understanding and invests heavily in the project at hand. The engagement resulted in an optimized inventory and increased sales, meeting the expectations of our internal team!

Kapila PereraIT DirectorSinger Sri Lanka PLCVerified review on Clutch

They are attentive to detail and have shown us they can solve difficult problems.

We’re excited to partner with NeenOpal for their collaborative approach, on-time delivery, clear communication, and attention to detail. Their ability to solve complex problems, paired with creative design and forward thinking, sets them apart.

Joyce Ann McGinnFounder & COOCompris, Inc.Verified review on Clutch

I like that the team is incredibly hard-working, talented, and good with people.

NeenOpal is a hard-working, talented team that consistently brings fresh ideas. Their domain experience reshaped our MIS reporting and delivered deeper insights, helping us approach complex business challenges with greater clarity and improved resource productivity.

Saransh ChaudharyCEOVenus Remedies LimitedVerified review on Clutch

NeenOpal delivers high-accuracy analytics that drive reliable, KPI-driven outcomes.

It’s been a pleasure working with NeenOpal from the outset. They delivered our data lake on time and consistently demonstrate high numerical accuracy and strong analytical expertise. By meeting key KPIs, they support smooth operations and measurable business outcomes.

Saurabh BholaCTOThe Healthy Mummy Pvt. Ltd.Verified review on Clutch

Move to Tableau Cloud without breaking a report

Tell us about your Tableau Server estate and your timeline. A certified Tableau consultant will follow up with next steps.

Executive FAQ

Tableau Cloud Migration FAQs

Direct answers to the concerns that matter before committing time and budget.

How long does a Tableau Server to Tableau Cloud migration take?

Under 100 users, Tableau's manual path takes one to two weeks. Larger, more complex estates run for several weeks to months and benefit from a professional-services engagement backed by a proper Tableau Cloud migration readiness assessment.

Do virtual connections migrate automatically?

No. Virtual connections can't be exported from Tableau Server and imported into Tableau Cloud; they must be manually recreated as part of your migration checklist.

Will my extract refresh schedules carry over?

No. Extract refresh schedules don't carry over; they need to be rebuilt natively in Tableau Cloud after content is republished.

What breaks most often when you migrate Tableau Server to Tableau Cloud?

Unsupported authentication (AD, Kerberos, LDAP), unsupported connections (cube sources, .taco connectors, Kerberos DB auth), stale IP allowlists post-Hyperforce, and legacy perpetual licensing are the usual blockers. A readiness assessment catches all of them before cutover.

Can I run both environments during migration?

Yes. Tableau's license transition gives you 60 days of dual access to both environments, extendable through your Account Manager if your migration timeline runs long.

What's the difference between the Tableau Migration SDK and the Content Migration Tool?

The Tableau Migration SDK (and its Migration App) is the right tool for Server-to-Cloud moves. It's API-driven and built for a one-time migration. The Content Migration Tool is for Server-to-Server or Cloud-to-Cloud content moves, not for migrating Tableau Server to Tableau Cloud.

Is Tableau Cloud the same as Tableau Online?

Yes. Tableau Cloud is the current name for the product formerly called Tableau Online; Tableau renamed it in 2022. If your team or your documentation still refers to Tableau Online, the migration steps on this page are the same ones that apply.