Tableau Server remains deeply embedded in South African enterprise analytics, but it carries a real operational cost. Infrastructure management, patch coordination, and upgrade cycles consume significant IT capacity.
Tableau Cloud eliminates that overhead. Built on Salesforce's Hyperforce infrastructure, it delivers enterprise-grade availability with automatic upgrades, immediate access to new features like Tableau Next and Pulse, and built-in security including SAML authentication, SCIM provisioning, and MFA - all without managing a single server.
For South African BI teams asked to deliver more with the same headcount, that shift matters. But migration is a meaningful technical undertaking.
Ten challenges we see most frequently, and what you should know before you start:
1. Legacy extract formats (.tde)
Tableau Cloud does not support the deprecated .tde format. Every data source using it must be manually converted to Hyper before migration.
Solution
Keyrus conducts a full content audit as part of every migration engagement, identifying all legacy extract formats and managing the conversion to Hyperforce. We automate where possible and prioritise by business, so conversion work does not become a blocker to your migration timeline.
2. Site capacity limits
Tableau Cloud operates within defined capacity boundaries on extract row limits, number of concurrent jobs, and storage thresholds - varying by licence tier. Migrating without checking these against your current usage risks disruption post-go-live.
Solution
Keyrus performs a usage and capacity assessment against your current Tableau Server environment before any migration begins. We map refresh schedules, extract sizes, and concurrent job volumes to the appropriate Tableau Cloud licence tier, so you are not over-licensed or caught short after go-live.
3. Private and on-premises data connections
Sensitive data in on-premises databases, common in South African financial services and healthcare, requires Tableau Bridge or Data Connect post-migration. Configuring these for many sources is a significant workload. Plan for it early.
Solution
Keyrus designs and implements Bridge and Data Connect architectures tailored to your network and compliance requirements, including POPIA considerations relevant to South African organisations. We treat private data connectivity as a dedicated workstream, ensuring your most sensitive data sources are stable and secure before cutover.
4. Custom scripts and API integrations
REST API scripts, Hyper API workflows, and metadata integrations all need to be ported to point at the new Cloud environment. Authentication flows, URLs, and site references all change. The larger your automation footprint, the more time you should allocate to this work.
Solution
As part of our pre-migration scoping, Keyrus inventories all existing API integrations and automation scripts. We handle the porting, testing, and validation of those scripts against the Cloud environment, and document the updated integration layer so your team has full visibility and ownership after the project closes.
5. Live data connections
Tableau Server users often rely on live connections to on-premises sources require Bridge or Data Connect in Tableau Cloud. Cloud-native platforms like Snowflake connect natively (no Bridge required) which is one reason a modern cloud data stack simplifies overall migration considerably.
Solution
Keyrus assesses every live connection in your environment and determines the right path: native cloud connection, Bridge-enabled live query, or a scheduled extract where a live connection is not practical. As both a Tableau Premier Partner and a Snowflake SELECT Partner, we guide clients toward a data architecture that supports live analytics at scale without unnecessary complexity.
6. Content Migration Tool licensing
The Content Migration Tool (CMT) is the most reliable way to move content between Tableau environments at scale, but it requires Advanced Management licensing on both source and destination environments. Without it, migration becomes a largely manual process. As a Tableau Premier Partner, Keyrus provides access to the CMT as part of the engagement, which typically saves significant time and reduces risk during the migration window.
Solution
Keyrus brings CMT access to every migration engagement. Beyond the tooling, our team has refined a migration methodology built around iterative CMT runs, allowing us to move content in waves, validate at each stage and course-correct before the final cutover. This significantly reduces downtime and risk of content loss.
7. IP allowlisting
Tableau Cloud operates from defined IP ranges. If your data sources or connected systems use allowlists to control inbound traffic, those lists must be updated before go-live. This is one of the most common causes of post-migration disruption.
Solution
Keyrus includes IP allowlist review and update planning as a standard part of the pre-migration checklist. We work with your network and security teams to identify every system that requires an update, document the required Tableau Cloud IP ranges, and validate connectivity in a staging environment before any production cutover takes place.
8. Embedded analytics
Embedded Tableau dashboards require changes to URL structure, authentication configuration, and Connected Apps setup. This is a high-value delivery model for many of our clients and we treat this as a dedicated workstream in any migration project.
Solution
Keyrus has deep experience designing and migrating embedded analytics environments. We audit your existing embedded integrations, redesign the authentication and URL architecture for Tableau Cloud, and test against your applications before go-live.
9. User training and change management
A technically clean migration can still feel disruptive if users aren't prepared. Navigation, scheduling, alerts, and personalisation all behave differently in Tableau Cloud. Proactive communication, training, and access to support resources before and after cutover make a material difference to adoption outcomes.
Solution
Keyrus offers structured Tableau training as a core service line, delivered to client teams across South Africa. We tailor training sessions to each user group: admin and governance training for IT teams, developer-focused sessions for content creators, and end-user orientation for business consumers. Training is scheduled around your go-live timeline to ensure adoption hits the ground running.
10. Subscriptions, alerts, and custom views
The CMT moves workbooks and datasources. It does not migrate subscriptions, data-driven alerts, or custom views. These must be recreated manually, a gap that's easy to miss until after go-live.
Solution
Keyrus builds a subscriptions and alerts register as part of the migration inventory, capturing every active schedule and recipient list before migration begins. We recreate these in Tableau Cloud and, where volumes are high, use scripted approaches to reduce manual effort. Public custom views are also migrated as part of our standard process.
Getting the migration right
A Tableau Cloud migration is as much a planning exercise as a technical one. Organisations that navigate it smoothly are those that audit their current environment thoroughly, identify dependencies early, and work through a structured migration process rather than a lift-and-shift.
As a Tableau Premier Partner, Keyrus has supported Tableau Cloud migrations across industries including entertainment provider, retail, and healthcare. If you are evaluating the move or already partway through it, speak to our team. We can help you assess your current environment, identify the issues most likely to affect your specific setup, and design a migration approach that minimises disruption. Contact us at sales@keyrus.co.za