We run a parallel environment through the entire migration. No cutover until Cloud is validated under real load. No surprises on go-live day.
We audit your complete Server environment: workbooks, data sources, users, extract schedules, authentication configuration, custom connectors, and embedded analytics. Every migration blocker is identified and documented before we begin.
Authentication is where most Tableau migrations hit unexpected complexity. We design and implement your Cloud authentication architecture — SAML, SSO, or MFA — and validate it against your identity infrastructure before any content moves.
We configure your Tableau Cloud environment to match your Server governance settings: site configuration, project hierarchy, permission structure, and custom branding. We also configure data source connections and validate credentials before content migration begins.
Content migrates in phases by department or risk level. Low-complexity, low-criticality content first. High-criticality financial and operational content last, after the migration process is validated. Users run both environments in parallel during this phase.
Final cutover to Cloud once all content is validated under real load. Server decommission follows after a defined stabilisation period — typically 30 days. We remain on standby for the full stabilisation period.
We identify and clean every embedded credential in the pre-migration audit. Cloud handles credentials differently — migrating without this step breaks data sources silently.
SAML and SSO configurations behave differently on Cloud vs. Server. We test authentication against your identity provider in the parallel environment weeks before cutover.
Extract schedules do not transfer automatically. We rebuild all schedules in Cloud — and optimise them in the process. Poorly configured extract schedules are a top source of Cloud cost overruns.
Custom connectors not certified for Cloud are identified in the pre-migration assessment. We document replacements or build-outs before migration begins — not after a failed cutover.
We never do big-bang cutovers. Phased migration by department with parallel environments means your users are never at risk of a failed cutover with no fallback.
Cloud handles large extracts and high-concurrency workloads differently than Server. We performance-test your most critical workbooks in Cloud before cutover.
A straightforward migration for a single-site environment typically takes 4–8 weeks from scoping to go-live. Complex environments with multiple sites, custom authentication, embedded analytics, or large extract volumes can take 12–20 weeks. We always run a parallel environment before cutover — no big-bang cutovers.
The most common migration failures involve authentication architecture (SAML and SSO configurations behave differently on Cloud), embedded credentials in workbooks, unsupported custom connectors, and extract schedules that need to be rebuilt. We identify and resolve all of these in our pre-migration assessment before any content moves.
We give you an honest answer, not a sales pitch. Cloud wins when you have fewer than 100 users, no strict data residency requirements, limited internal Server admin capacity, and no embedded analytics at scale. Server wins when financial services or healthcare data sovereignty requirements apply, extract volumes are very large, or embedded analytics licensing makes Cloud prohibitively expensive.
Most content migrates cleanly using Tableau's built-in migration tools. The exceptions — workbooks with embedded credentials, custom connector dependencies, or Server-specific features — are identified in the pre-migration audit and resolved before migration begins.
Extract schedules do not transfer automatically from Server to Cloud. We rebuild all schedules as part of the migration — this is an opportunity to optimise them. Poorly configured extract schedules are one of the most common causes of Cloud cost overruns.