Tableau Server Migration Guide
Tableau Server Migration Guide
Contents
Tableau Cloud Manual Migration Guide iv
Dive deeper v
Post-migration vii
Licensing viii
Migration workflow ix
Tableau Software i
Tableau Cloud Manual Migration Guide
Migration workflow xx
Migrate Data Sources, Workbooks, and Prep Flows to Tableau Cloud xxi
Step 1: Create projects for your site with minimum access policy xxi
ii Tableau Software
Tableau Cloud Manual Migration Guide
If you have a lot more users and your data requirements are more complex, you may benefit
from working with professional services or an experienced migration partner to migrate to
Tableau Cloud. Further down, this topic includes guidance on how to plan your migration.
But first, let's make sure you understand why moving to Tableau Cloud is probably the smart
move for your organization.
What about bigger organizations? If your organization exceeds 100 users, then you will also
undoubtedly benefit from savings of cost and time at scale. Tableau Cloud is built to handle
big organizations, but this guide isn't. If you're looking to migrate a bigger organization, check
out Tableau Cloud Migration where you can learn more about working with professional ser-
vices or an experienced migration partner.
For many organizations, Tableau Cloud will be faster and more reliable, with less bother than
whatever you are doing now to keep your Tableau Server humming. You will never need to
iv Tableau Software
Tableau Cloud Manual Migration Guide
face another major server upgrade, or even a maintenance release update, which, as you
know, is really just an upgrade smuggled in under another name. Tableau Cloud is always run-
ning the latest release, with the most up-to-date features. Reliability and performance are
baked into the service. After the migration process, your time with Tableau Cloud will be spent
managing users and data. That's it. You won't be troubleshooting service errors or combing
logs or restarting, and restarting.
Work with your account manager to figure out the costs for supporting your users. As you eval-
uate overall cost, remember that the single metric of per-user licensing expense does not
provide an apples to apples comparison between SAAS and self-hosting a server. This com-
parison is especially impoverished if you are not including the time spent managing Tableau
Server, and the capital cost of refreshing or leasing hardware. The annual cost of running a
single server in the cloud can be more than $10,000 a year. And of course any analysis must
include your staffing cost of maintenance, periodic updates, and troubleshooting.
Dive deeper
l For a quick and relevant evaluation of moving to Tableau Cloud, see the blog post,
Should I Move My Analytics to Tableau Cloud?
l For more information about the advantages of moving from on-premises or self-hosted
to Tableau Cloud, see GigaOm's research article, CxO Decision Brief: SaaS Business
Intelligence Platforms.
l For a case-study detailing cost savings and performance improvement in the real world,
see Splunk migration to Tableau Cloud eliminates server admin overhead and drives
better dashboard performance.
Tableau Software v
Tableau Cloud Manual Migration Guide
l Regulation and data residency: Your business operates in a space that must comply
with a regulatory (such as FedRAMP, PCI, etc.) or data residency requirement that
Tableau Cloud does not yet meet. Please review our list of current compliances and
check back often to learn when new certifications become available.
l Data sources: Your organization relies on a data solution that does not work with
Tableau Cloud, is not supported by Tableau Bridge, or is otherwise beyond the scope
of your ownership to extract in a compatible way. Examples of such data sources
include cube data sources, custom connectors, packaged Tableau connector (.taco)
files, among others. The next topic, Plan Your Migration, walks through the different
supported data sources and options available in Tableau Cloud. You can also down-
load the free Tableau Cloud Migration Technical Readiness Assessment to see which
data sources you’re currently using and if they are supported on Tableau Cloud.
l Site capacity: If you have more than 1 terabyte of data, take a look at Advanced Man-
agement for Tableau Cloud. Otherwise, review Tableau Cloud Site Capacity to optim-
ize any necessary consolidation. The Tableau Cloud Migration Technical Readiness
Assessment can help you identify assets that will require consolidation.
l Authentication: If you require LDAP for an external identity store, Kerberos authen-
tication, or Kerberos delegated authentication.
l Data management: Tableau Prep Flows are not supported by Tableau Bridge. If you
require automated data updates with Tableau Prep Flows for data behind a private net-
work, see How to Run Tableau Prep Conductor Flows with On-Premises Data in
Tableau Cloud. Tableau Prep Flows using Python are also not supported by Tableau
Bridge.
After you migrate and create the core administrative functionality (identity/user, site con-
figuration, authentication, data connection, etc) in Tableau Cloud, the bulk of content migra-
tion can be shared with the creators at your organization. A "creator" is a user who has a
Creator role-based license. Depending on your goals, either you (the admin) or your creators
vi Tableau Software
Tableau Cloud Manual Migration Guide
can migrate content. For this reason, we've created a chunk of migration-related content you
can point your creators to. Users who migrate content need to have a Creators license and
access to Tableau Desktop. If the creators will be migrating Tableau Prep flows, then they
must also have Tableau Prep Builder installed.
Post-migration
In this guide we will do our best to cover as much of the Tableau Cloud platform as possible,
but there are some features that administrators cannot set up on behalf of their end users.
Users will need to make some updates to their content after a migration is complete. There are
also some features that are better to recreate anew in Tableau Cloud with the benefit of using
cloud-native functionality.
l In Tableau Cloud, as the administrator, you do not have direct access to the Tableau
Server Repository (Windows | Linux). Instead, you can use Admin Insights to under-
stand what’s going on in your Tableau environment, including the current licensing state
and performance.
l Guest access is not available on Tableau Cloud. Instead use Connected Applications to
broaden access.
l Custom fonts are not available on content.
l Tableau Cloud uses a single site model to simplify administration. If you have multiple
Tableau Server sites, your content may need to be consolidated onto a single site.
Run the Tableau Cloud Migration Technical Readiness Assessment to understand if there are
any use cases which may need to be adapted before migrating to Tableau Cloud.
l Webhooks
l Embedding solutions updates
l Update REST API scripts
l Configuring Analytics Extensions
Version compatibility
As a general rule, our documentation is based on recent-to-current versions of Tableau
Server, but because the process covered in this guide is not a programmatic or automated
migration, we don't foresee issues with migrating from older versions of Tableau Server to
Tableau Cloud. Strictly speaking, the process in this guide is more "port" than
"migration" when it comes to administrative configurations.
Licensing
Tableau Cloud uses Role-Based Subscription licensing. Tableau Server supports Role-
Based Subscription licensing and legacy pricing models. If you are on a different
(earlier) licensing model, please contact your Tableau account team to convert your licensing
to Role-Based Subscription.
Additional Support
After reading through this material you may decide that you'd prefer not to take on a manual
migration yourself, and would rather leave it to an expert. If so, please reach out to one of our
experienced migration partners to learn how they can help you accelerate a migration to
Tableau Cloud.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
Tableau Software ix
Tableau Cloud Manual Migration Guide
This topic walks you through two important planning tasks you should complete before migrat-
ing: your data connectivity strategy and establishing your authentication mechanism. You can
find a summarized list of the feature differences in the Tableau Server help topic, Technical
Considerations for Migrating from Tableau Server to Tableau Cloud (Windows | Linux). Run
the Tableau Cloud Migration Technical Readiness Assessment to understand if there are any
use cases which may need to be adapted before migrating to Tableau Cloud.
If you are familiar with administering Tableau Server today, you’ll find that many of your tasks
are largely the same in Tableau Cloud. With the move to Tableau Cloud though, tasks related
to deploying and managing the software will be handled by Tableau as a managed service.
You can leave the upgrades to us. Head to the blog post, Should I Move My Analytics to
Tableau Cloud? for more details. With Tableau Cloud, you will be able to focus more of your
energy on ensuring smooth data connectivity, equipping users with best practices and devel-
oping an analytics community. For more details about what managing a Tableau Cloud site
involves, as well as a bunch of resources to get you started as an administrator, visit the
Tableau Cloud Site Admin page.
x Tableau Software
Tableau Cloud Manual Migration Guide
The goal at this point is to validate that you can support your current data requirements after
your migration to Tableau Cloud.
l You can use the Stale Content (Windows | Linux) admin view in Tableau Server to
identify content that is no longer in use. It doesn't usually make sense to move ancient,
archived content to Tableau Cloud. Let it go!
l Like most organizations who have been running Tableau Server for a while, your con-
tent hierarchy and permission structure has probably "evolved" organically and probably
a bit messily. As you plan the migration, develop a strategy that will optimize project,
group, and permissions structures in your new Tableau Cloud site.
l If you are a Tableau Data Management customer, use the tools to manage data clean-
ing, combining, and processing for the pending move.
Tableau Software xi
Tableau Cloud Manual Migration Guide
l Cross check it with the Tableau Cloud connector table in the following section. If it's
supported, you've got a direct path forward. If it's not in the table...
l Cross check it with Connectivity with Bridge, to determine if your data type is supported
by Tableau Bridge.
l If the data source is a static file, Tableau Cloud supports uploading Excel or text-based
data sources (.xlsx, .csv, .tsv) directly from the browser or Tableau Desktop. The max-
imum file size you can upload is 1 GB. More likely, your users are connecting to these
types of files in a shared, common directory. If this is the case, you can upload these
files to a public cloud space such as Google Drive, Dropbox, or OneDrive, for example.
Or you can use Bridge. You (or your users) can then configure Tableau Cloud to con-
nect to these spaces for a live data connection.
l Run the Tableau Cloud Migration Technical Readiness Assessment to understand if
there are any use cases which may need to be adapted before migrating to Tableau
Cloud.
*For more information about using OAuth 2.0 standard for Google BigQuery, OneDrive, and
Dropbox connections in Tableau Cloud, see OAuth Connections.
**Teradata web authoring currently doesn’t support query banding functionality. See Teradata
for details.
‡Supports virtual connections if you have Data Management. See About Virtual Connections
and Data Policies in the Tableau Cloud help for details.
The default user account on Tableau Cloud is called TableauID. TableauID requires multi-
factor authentication (MFA) to ensure secure access to Tableau Cloud. See About multi-factor
authentication and Tableau Cloud in the Tableau Cloud documentation.
If your organization uses an identity provider (IdP) to enable authentication, you can probably
use that for Tableau Cloud. We support Salesforce authentication and Google OpenID
natively. You can also configure SAML for Azure, Okta, OneLogin, AD FS, PingOne, or any
IdP that supports standard SAML 2.0 authentication.
Before you proceed, review the Tableau Cloud Authentication options to develop a plan.
If your organization manages identities with Azure AD, Okta, or OneLogin, then you can also
automatically provision users and groups in Tableau Cloud. See Automate User Provisioning
and Group Synchronization through an External Identity Provider.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
The migration process that is described in this guide starts by working with your account man-
ager to transition your Tableau licenses from Server to Cloud. If you would like to test out
Tableau Cloud prior to your migration, you're also welcome to trial Tableau Cloud at any time.
Tableau Software xv
Tableau Cloud Manual Migration Guide
If the connection is a database, you may need to enable Tableau Cloud to query it. To enable
connectivity, see Authorize Access to Cloud Data Published to Tableau Cloud.
For flat files like Excel and .csv files: we recommend saving these files in a cloud store like
Google Drive, Dropbox, or OneDrive. You can then enable direct connectivity to the data from
Tableau Cloud. If that is not an option, you will need to configure Tableau Bridge to maintain
connectivity to flat files saved locally.
If you have Private data requirements, you will need to install and configure Tableau Bridge.
Tableau Bridge provides secure communication between Tableau Cloud and data behind fire-
walls. Install Bridge behind your firewall on a separate computer that has access to your data.
See About the Bridge Client.
Optional: For local files (Excel, CSV, etc), you can save them in a cloud store like Google
Drive, Dropbox, Onebox instead of using Tableau Bridge.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
If your organization relies on virtual connections in Tableau Server, you must migrate those
before proceeding. If you do not have virtual connections configured for Tableau Server, skip
this procedure.
Migrating virtual connections from Tableau Server to Tableau Cloud is a manual process. You
must recreate the virtual connection (or the published data source and virtual connection) on
your Tableau Cloud site, replace the data source in each workbook with the new virtual con-
nection, and then copy/paste any calculation formulas from the original workbook data source
to the updated one.
Step 2: Recreate published data sources built with the virtual connection
You will need to recreate all published data sources that use the virtual connections:
Run the following procedure from Tableau Desktop for each workbook that you want to
migrate to Tableau Cloud:
1. Sign in to Tableau Server, navigate to the workbook that you are migrating, and then
download the workbook.
2. Within the workbook select File > Close. Do not close Tableau Desktop.
3. Sign out of Tableau Server: Server > Signed into http://example > Sign out. You will
get a warning about signing out while connected to Tableau Server. Click OK.
5. From the Desktop home screen, select the workbook file to open it again.
You will receive two Unable to complete action error messages. Close the error mes-
sages. When the worksheet opens, it will display the Worksheet Unavailable message.
Do not edit the connection from the main window.
6. If you’ve already created a new published data source skip to Step 8. Otherwise, update
the data source by navigating to Data > New Data Source.
l Navigate to the new virtual connection that you created for this workbook, and
then click Connect.
l Open the original Tableau Server workbook and copy the formulas. Paste the for-
mulas in the updated Cloud workbook.
7. Create a new data source that exactly matches the previous data source. Field names
must match exactly.
8. Replace data source: On the Data tab, right-click the data source that you just created,
and then click Replace Data Source. In Replace Data Source specify the correct
source in the Replacement selector, and then click OK.
Name.
l Embedded in the workbook, select Publish > Workbook.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
xx Tableau Software
Tableau Cloud Manual Migration Guide
For many organizations running a manual migration, it may make sense to have users (or a
subset of users) migrate content they are familiar with to the new Tableau Cloud site. The con-
tent migration steps described in this topic can be completed by users (with Creator roles) in
your organization.
Keep the Tableau Server lights on! During your migration process, ensure that all content
and business processes remain operational in your Tableau Server system. Do not decom-
mission your Tableau Server environment until you have verified and validated that your con-
tent and procedures have been properly migrated to Tableau Cloud.
Before you begin, we recommend reviewing Quick Start: Permissions for a refresher course
on how permissions interact and inherit in Tableau. If you are familiar with these concepts in
the context of Tableau Server, then you're good to go. Tableau Cloud permissions use the
same logic as Server.
1. Configure template permissions on the Default project before creating more projects.
2. Remove permissions for All Users group. Removing All Users ensures that projects are
configured with explicit permissions for users who need to access the content.
For more general project permission guidance, see Use Projects to Manage Content Access.
1. On Tableau Desktop, sign in to your Tableau Server environment, navigate to the work-
book(s) that you want to migrate, and click Download.
2. On the Data menu in Tableau Desktop, select the data source, select Create Local
Copy, and then save the local copy of the data source.
3. Working from a Sheet, select Data > Replace Data Source. Enter the following
options:
l Current: The current Local Copy Replacement: the local copy you saved
l In the Data pane, right-click the original published data source, and then select
Close.
5. Select the data source in the Data menu and select Publish to Server.
6. In Tableau Desktop, sign in to Tableau Cloud, then publish the data source.
7. If necessary, schedule a refresh of that data source in Tableau Cloud. For more inform-
ation, see Recreate Refresh Schedules for Tableau Cloud.
If the newly published data source is the only data source in the workbook, then follow the next
two steps to publish the workbook as well. If the workbook has multiple published data
sources, skip to the next step.
1. When Publishing the data source, verify that Update workbook to use the published
data source is selected.
2. Select Server > Publish Workbook to publish the workbook to Tableau Cloud.
1. On Tableau Desktop, sign in to your Tableau Server environment, navigate to the pub-
lished data source that you want to migrate, and click Download.
2. The file will open in Tableau Desktop. On the Data menu in Tableau Desktop, select
the data source, select Create Local Copy, and then save the local copy of the data
source.
3. In the Data pane, right-click the original published data source, and then select Close.
4. Repeat steps 2-3 for all Published Data Sources in the workbook.
6. Working from a Sheet, select Data > Replace Data Source. Enter the following
options:
7. After all Published Data Sources are replaced, select Select > Publish Workbook to
publish the workbook to Tableau Cloud.
If the workbook also has an Embedded Data Source requiring Tableau Bridge, those data
sources will need to be published separately as during the migration. See Publish a Data
Source.
3. Select Server and then click Sign In to sign into Tableau Cloud.
4. If the embedded data source requires Tableau Bridge for automated refresh and is file
data (such as .cvs and .xlsx), follow the instructions at Publish on-premises data
(Tableau Cloud only).
5. If the data source does not require Tableau Bridge or is not file data, select Server >
Publish Workbook.
Repeat the following procedure for all Tableau Prep flows that you would like to migrate to
Tableau Cloud. Run this procedure on a computer that is running Tableau Prep Builder.
1. Sign in to your Tableau Server environment, navigate to the flow that you want to
migrate, and click Download.
2. The flow will open in Tableau Prep Builder:
a. If the flow connects to at least one published data source you will be automatically
prompted to sign into your server. If you are not automatically prompted, from the
top menu select Server > Sign in and sign in to Tableau Server.
b. Navigate from the top menu and select Server. In the Signed into server URL,
click Sign Out.
c. If the flow connects to at least one published data source, you will see the fol-
lowing warning:
6. After all published data sources are replaced, select Server > Publish Flow or click
the Publish button in the top right hand corner to publish the flow to Tableau Cloud.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
4. You are here: Migrate Data Sources, Workbooks, and Flows to Tableau Cloud
5. Recreate Refresh Schedules for Tableau Cloud
6. Configure Permission and Content Access for Migrated Users
7. Add Remaining Users to Tableau Cloud
8. End-User Migration Checklist
For data sources requiring Tableau Bridge, ensure Bridge is configured for the con-
nection before establishing extract refreshes. See Use Bridge for Private Cloud Data.
l To establish new refresh schedules for Tableau Prep flow, navigate to the flow in
Tableau Cloud. Select Scheduled Tasks > New Task > Select and configure the
schedule. Do the same for any Linked Tasks. For more information, see Schedule Flow
Tasks.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
Now that you've added your data sources, workbooks, and Prep flows to Tableau Cloud,
you're ready to add your users. Before we do that, it's important to understand how Tableau
determines who has access to what data. Tableau Cloud allows you to designate who has
access to content and allows you to restrict the data access within a data source.
We will use content access tools to restrict who has access to a content item, and row level
security tools to restrict the data a user can see within a data source.
Content access
Projects, nested projects, and individual content items are all subject to permission rules. You
can see how those rules are used in your Tableau Server environment and then recreate
them in Tableau Cloud. See Permissions.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
Now that you've migrated over all the content and set up your projects, groups, and per-
missions, you can add the rest (or all) of your users.
Add users
As soon as you add users, they will be able to access content. Make sure to follow the pro-
cedures in Configure Permission and Content Access for Migrated Users before adding
users.
We also recommend learning about user site roles before migrating to Tableau Cloud. See
Set Users' Site Roles.
You can add users manually as shown below. If you have a lot of users and want to batch-
import them with a CSV file, see Import Users.
2. On the Users page, click Add Users, and then click Enter Email Addresses.
3. If Google or SAML authentication is not enabled on this site, skip to the next step.
If Google or SAML authentication is enabled on this site, you can select the authen-
tication type for the new users.
l Select Add users for [Google/SAML] authentication if you enabled your site
for Google or SAML authentication and want the imported users to sign in to the
site through an external identity provider.
l Select Add users for Tableau authentication if you want these users to have
the default email address and password authentication.
You can go to the Users page to change users’ authentication type any time after
you add them.
Note: To work with Tableau Server by way of tabcmd, the Tableau Data
Extract Utility, or the Tableau APIs, users must authenticate with a
TableauID account.
4. In the Enter email addresses box, enter the users’ email addresses. If you add more
than one user, separate each address with a semicolon.
5. Select a site role from the drop-down list, to assign that site role to all users you’re
adding.
If a new user’s email address is already associated with an account on tableau.com, the user
is prompted to sign in using the existing email address and password for that account.
If a new user’s email address is not already associated with an account on tableau.com, the
user is prompted to provide a first and last name and password.
Until the user provides these values, their entry in the Tableau Server user list shows the
email address preceded by a period. For example:
.snguyen@example.com
After the user signs in, the entry is updated to show the full name. For example:
Susan Nguyen
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud:
You're here because your Tableau administrator has recently migrated your Tableau Server
environment to Tableau Cloud, Tableau's fully managed analytics platform.
As a part of your migration, the following tasks need a few minutes of your time to make sure
that you have a smooth transition to Tableau Cloud. If you were using any of the below fea-
tures on Tableau Server, they will need to be re-created on Tableau Cloud. Review this list to
understand what features need to be re-created and follow the steps provided to do so!
Work with your Tableau administrator to access both Tableau Server and Tableau Cloud while
you migrate these items.
n URL actions: You’ll need to update URL actions that originated on Tableau Server so
that they point to Tableau Cloud URLs, or you can use updated field variables. See
URL Actions.
n Subscriptions: You’ll need to resubscribe to views, workbooks, and flows on the
Tableau Cloud site. See Create a Subscription to a View or Workbook.
n Custom views: A custom view is a copy of a view that has your selections and filters
applied. You’ll need to reapply custom views on your Tableau Cloud site. See Use Cus-
tom Views.
n Row-level security: User and group names can change in a migration. If you used
groups and user names in row-level security solutions within Tableau data policies, data
sources or workbooks, they will need to be updated following a migration.
n Ask Data lenses: You’ll need to reconfigure Ask Data Lenses on Tableau Cloud. See
Create Lenses that Focus Ask Data for Specific Audiences.
n Favorites: You must recreate your favorites. You can add any type of content to your
favorites, except for embedded data sources. See Mark Favorites.
n Collections: Collections will need to be re-created by users in Tableau Cloud.
Migration workflow
This guide is organized according to a step-wise process for migrating to Tableau Cloud: