High Performance Technologies - High Performance Technologies Blog , Tableau Cloud MigrationHigh Performance Technologies - High Performance Technologies Blog , Tableau Cloud Migrationhttps://www.highperformance.tech/blogs/tableau-cloud-migrationThu, 23 Apr 2026 22:05:34 -0700http://zoho.com/sites/<![CDATA[Understanding User License Dependencies in Cloud Migrations]]>https://www.highperformance.tech/blogs/post/understanding-user-license-dependencies-in-cloud-migrationsWhen migrating from Tableau Server to Cloud, content owned by unlicensed users creates roadblocks. Before you start audit user licenses, clean up unlicensed content, and reassign ownership pre-migration — ensuring nothing valuable gets left behind.]]>

When you switch from Server to Cloud, getting your users licensed properly is essential. Tableau recommends setting up your Creator users first, and we agree! Working with your Creators, the Content Authors, throughout the migration process is vital to a successful migration. Once your Creators are added then you want to migrate the content so it keeps the correct ownership.


If you migrate manually, this looks like asking each of your Creators to download their content from the Tableau Server and republish to the new Cloud location, recreating any extract refreshes and custom views in the process.


One thing that is different about user set up in Cloud vs. Server is that Cloud requires users to sign in with full email addresses (ex: johnsmith@company.com), whereas Server requires just a username (ex: johnsmith) and password. If your Server currently has users signing in with simple usernames, they will need email-based credentials for Cloud, and it’s important to communicate any new sign-on procedures to your users during migration.


Unlicensed Users with Content

But what about the content sitting on your Tableau Server owned by an unlicensed user – either they have left the company or changed roles – and their legacy dashboards exist without continued ownership? How will their content get migrated?


The best thing to do is take inventory of all content owned by unlicensed users and evaluate if that content is still relevant and needed. Are those workbooks being accessed and used regularly?

  • If yes, then a Tableau Admin can reassign that content to a licensed owner so it can be migrated to Cloud.
  • If not, then the content can be decommissioned and flagged to not migrate to Cloud.

    • Clean House Before You Move

    Not only can you clean up unlicensed users’ content but think of your Tableau Cloud migration like moving to a new home - it's the perfect opportunity to declutter! Why spend the time to migrate (and then maintain) dozens of outdated dashboards that nobody's looked at in months?


    It's common for Tableau Servers to accumulate digital dust over time. That quarterly report from 2019? The prototype dashboard someone built but never finished? The "test" workbooks scattered across projects? Migration is your chance to leave them behind.


    Before moving anything to Cloud, we recommend auditing your content usage. Look for:

    • Workbooks with zero views in the last 6-12 months
    • "Test" or "Draft" content that never went live
    • Dashboards created by employees who've left the company
    • Multiple versions of the same analysis

    Starting fresh in Tableau Cloud with only your active, valuable content means:

    • Faster migration process
    • Cleaner, more organized environment
    • Easier maintenance and governance
    You can use your Server's admin views or repository data to identify unused content before migration.

    Get a Jump Start

    As mentioned in our introduction post to this series, auditing your Server content and creating a Content Readiness Dashboard provides insight to which content on your Server is owned by an unlicensed user, so you can zoom in on the relevant content to make license changes before migrating. 


    When we handle migrations for our clients, we migrate content and make necessary changes at scale. This includes moving active users with proper licenses, content, and permissions. If needed, we can automatically reassign orphaned content to valid licensed users in Cloud during the migration process.


    To get a Content Readiness Dashboard for your Server and see your unlicensed users' content, schedule a call with our migration experts below. 


    Talk to a Migration Expert

    This is part two of our ongoing series on Tableau Cloud Migration Roadmap. Up next: Font Compatibility: The Hidden Migration Complexity.





    This can be a pretty tedious process depending on how much content you have on your Server.












    Taking the time to evaluate if content is still needed is well worth it in the long run — and will save you time on your migration journey.



















    CobWEBS...am I right?!?






    Your future self will thank you for the squeaky clean Cloud environment.






    If you get to Cloud and realize you've forgotten something, we can help you restore it from a pre-migration backup!

    ]]>    Fri, 15 Aug 2025 14:39:53 -0500    <![CDATA[Tableau Cloud Migrations: Mapping Your Migration Journey]]>https://www.highperformance.tech/blogs/post/tableau-cloud-migrations-mapping-your-migration-journeyMigrating from Tableau Server to Cloud is like planning a road trip — you need to spot the roadblocks ahead. We've identified 6 common delays that can slow your migration. Our Content Readiness Dashboard maps your route and shows exactly what needs fixing before you move.]]>

    In the age of GPS-enabled smartphones, it’s rare to plan a trip without first checking your favorite mapping app. Whether you’re avoiding tolls, aiming for a specific arrival time, or want the fastest route, the app gives directions to meet your needs.


    Migrating from Tableau Server to Tableau Cloud works the same way. You know your starting point and your destination — but what about the delays that could slow you down?


    When you’re mapping your route from Server to Cloud, considering the unique details of your Tableau environment will help you avoid the most common (and costly) slow-downs you could encounter. In this ongoing blog series, we will show you how to identify these road hazards ahead of time so you can travel with confidence (and have the right ETA).


    So, buckle up, and let’s begin.

    The Route Overview

    We find that most Tableau Server --> Tableau Cloud migration routes are made up of five key segments. They're all important, but the first, Planning and Analysis, is essential so you can get the best possible route customized to your unique environment, avoiding any potential roadblocks along the way.



    During the Planning & Analysis phase, you need to answer two critical questions:

  • What is your strategy for data connectivity in Tableau Cloud?
  • Is your content compatible with Tableau Cloud?


    • To answer those questions, you'll want to audit your Tableau Server content, looking for things that could cause you to veer from the standard route. Think of this phase like checking the route before departing on a road trip — this is where you spot the construction zones, detours, and traffic jams. With that visibility, you can adjust your timeline, reroute where needed, and plan smarter. The result: a clearer picture of what’s ahead and a more accurate ETA for reaching Tableau Cloud.


    Potential Route Delays

    Here are six potential delays we’ve identified to be on the lookout for:

    1. User License Dependencies
    2. Unsupported Fonts
    3. Broken URL Connections
    4. Database Connection Failures
    5. Flat File Refresh Failures
    6. Private Data Connectivity

    Each of these items may appear straightforward on the surface, but with the complexity of each dashboard and data source, they can end up being quite nuanced in how you approach a solution before and during migration.


    Taking Inventory

    When we plan successful Cloud migrations for clients, we start by creating a complete Content Inventory of all the users, data sources (and their connections), and workbooks on the Server, looking for the six potential delays we listed above. Once we've gathered our inventory, we visualize it in a Tableau Dashboard. The Content Readiness Dashboard helps us quickly see areas where remediation, or a reroute, is needed and plan accordingly.







    » We'll keep adding to this series as we uncover more potential delays to look out for.




































    » This blog series will dive into each of these in more detail, ensuring you have the knowledge and tools needed to prepare for your journey. 










    » We get this information from the Tableau Server API, but you can also get the details from the Tableau Repository for your Tableau Server.






    The Content Readiness Dashboard breaks down:

  • Content needing remediation vs. Content ready for migration
  • Content and remediation type needed by author
  • Recommended timeline for when to remediate certain roadblocks


    • We also give each Tableau content author a custom checklist with their specific fixes and clear steps to take. Getting content ready for migration is a team effort. Migrations are most successful when everyone pitches in to clear the roadblocks ahead of time.



    Planning a migration without knowing what's ahead is like driving cross-country without checking traffic. Taking an inventory and identifying the potential roadblocks we've outlined will show you exactly what to expect from your unique environment as you plan your migration.


    Want to see what roadblocks might be waiting in your migration? We can help you out with your content inventory and provide you with a Content Readiness Dashboard for Server content.

    Talk to a Migration Expert

    This is part one of our ongoing series on creating your Tableau Cloud Migration Roadmap. Up next: Understanding User License Dependencies in Cloud Migrations.

    ]]>    Wed, 13 Aug 2025 11:11:08 -0500