What is Migrated Data in Tableau?

You've just opened a Tableau workbook someone sent you, and in the corner, you see a notice: your data source is "migrated data." It sounds a bit technical, and maybe even like something is wrong. Is your data lost somewhere in translation? Is it out of date? This article will walk you through exactly what migrated data means in Tableau, why it happens, and how to manage it so you can stay in control of your dashboards.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What Does "Migrated Data" Actually Mean in Tableau?

At its core, "migrated data" is simply Tableau's way of telling you that it has created a static, local copy of your data and saved it inside the workbook file itself. Think of it like a photograph. Instead of having a live video feed from your data source (like an Excel file or a database), the workbook has taken a snapshot of that data at a specific moment in time and is now referencing that snapshot.

This process is tied to the concept of a Tableau Extract. When your data is migrated, it's converted into a highly compressed, performance-optimized Tableau Data Extract file (with a .hyper extension). This .hyper file is then bundled together with your worksheets and dashboards into a single Tableau Packaged Workbook file (.twbx).

This is the key difference between a .twb (Tableau Workbook) file and a .twbx (Tableau Packaged Workbook) file:

• A <strong>.twb</strong> only contains the instructions — the sheets, dashboards, and formatting you've built. It relies on a live connection to an external data file to populate your charts. If you send someone a .twb file without the data file, they can't see anything.
• A <strong>.twbx</strong> is a self-contained package. It bundles the workbook (the .twb) with all its necessary assets, including the data extract ("migrated data"), custom images, and geocoding information. Anyone can open a .twbx and see the dashboard exactly as you intended, because all the data is baked right in.

So, when you see "migrated data," it's not an error. It's a feature designed to make your dashboards portable and self-sufficient.

Why Does Tableau Migrate Data? The Pros and Cons

Tableau often migrates data automatically, especially when you save a file from Tableau Public or choose to create a packaged workbook for sharing. Understanding why this happens can help you decide whether a static extract or a live connection is better for your particular project.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The Upside of Migrated Data (Extracts)

1. Unbeatable Portability

Imagine you’ve built a dashboard connected to an Excel file sitting on your C: drive folder. If you email the .twb file to your manager, they'll see a bunch of blank charts because their computer can't access your drive. By migrating the data and saving it as a .twbx, you bundle everything together. Your manager can open it instantly without needing access to the original file path. This makes sharing dashboards via email, Slack, or other platforms incredibly easy.

2. Better Dashboard Performance

Live connections can be sluggish, especially if you're pulling from a slow database, a large text file, or a data source over a VPN. An extract, however, leverages Tableau’s optimized .hyper technology. Queries against a .hyper extract are often lightning-fast. For users, this means filters respond instantly, charts load quicker, and the overall experience is much smoother.

3. Offline Access

Once the data is migrated into your workbook, you no longer need an internet connection or network access to work with it. You can build charts, tweak dashboards, and analyze your data on a plane, in a coffee shop, or anywhere you can open your laptop. The workbook is entirely self-contained.

The Downside of Migrated Data

1. The Data is Static and Can Become Stale

This is, by far, the biggest drawback and the leading cause of confusion. A migrated data extract is just a snapshot. If you're connected to a sales forecast spreadsheet that gets updated daily, your .twbx file won't know about those new numbers. It will continue to show the data from the moment the extract was created. This leads to dashboards displaying old, outdated information, which can be misleading or downright wrong if you’re not careful.

2. Increased Workbook File Size

Because you are embedding the entire dataset inside the workbook file, your .twbx files will be much larger than their .twb counterparts. This can become an issue for emailing, uploading, or simply storing on your hard drive, especially if you're working with millions of rows of data.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

How to Identify and Manage Migrated Data in Your Workbook

Being comfortable with Tableau means knowing what your data is doing. A few simple checks will tell you if you're working with a live connection or a migrated extract, and more importantly, how to change it.

Checking Your Data Source Status

The easiest way to check your connection status is on the "Data Source" tab (at the bottom-left of your screen). Once there, look at the top right of the canvas:

• Live: This indicates you have a direct connection to your data source. Any changes in the source file will be reflected in Tableau the next time you interact with the dashboard (or when refreshed manually).
• Extract: This tells you that an extract has been created. You are working with migrated data - a static snapshot living inside your workbook.

You can also check the icons in the "Data" pane on any worksheet. A data source with a single blue cylinder icon represents a live connection. Two cylinders overlapping with a small arrow indicate an extract connection.

Refreshing, Reverting, or Reconnecting Your Data

Once you’ve identified that you're using migrated data, you have several options depending on what you want to accomplish.

1. Update the Snapshot (Refresh the Extract)

If you like the performance boost of an extract but just need the latest data, you can simply refresh it. This tells Tableau to go back to the original source, grab all the latest information, and update its local snapshot.

How to do it:

• Right-click on your data source in the Data pane.
• Hover over "Extract."
• Click "Refresh."

This will reconnect to the original data source (assuming you still have access to the file path) and rebuild the extract with fresh data.

2. Switch Back to a Live Connection

If you need real-time data and can tolerate potentially slower performance, switching back to a live connection is simple.

How to do it:

• Navigate to the "Data Source" tab.
• In the top right corner, simply click the "Live" radio button.

Tableau will disable the extract and connect directly to the original file. Be aware: if the original data source is on a network drive or in a location your computer can't reach, this connection will fail.

3. Fix a Broken Connection

Sometimes you’ll open a workbook and see a red exclamation mark next to your data source. This commonly happens when an extract needs to be refreshed, but the original file has been moved or renamed. Tableau knows it created a snapshot from a file that was at C:\Users\You\Downloads\SalesData.xlsx, but now it can't find it.

How to do it:

• Right-click the broken data source in the Data pane.
• Select "Edit Connection."
• A file browser window will pop up, allowing you to navigate to the new location of your data file.
• Select the file, click "Open," and Tableau will re-establish the connection.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Best Practices: When to Use a Live Connection vs. an Extract

Choosing between a Live connection and an Extract is a fundamental decision in building Tableau dashboards. Neither one is inherently "better" — it's all about picking the right tool for the job.

Situations That Favor a Live Connection:

• For Truly Real-Time Data: When you need an up-to-the-minute view of what’s happening, like in an operations dashboard tracking live support tickets or website traffic, a live connection is necessary.
• When Using a High-Performance Database: If your company has invested in fast, optimized database systems like Snowflake, Google BigQuery, or Amazon Redshift, you should use their power directly with a live connection.
• When Keeping Data Secure: In some cases, organizations prefer not to have data extracts floating around in packaged workbooks. A live connection ensures all data access respects your database’s security rules.

Situations That Favor an Extract (Migrated Data):

• For Better Performance: If your live connection is slow and frustrating to use, creating an extract will almost always make your dashboard feel faster and more responsive.
• For Portability and Sharing: When you need to send a dashboard to someone who doesn't have access to the original underlying data, a packaged workbook with a data extract is the perfect solution.
• To Reduce Load on Source Systems: If many users are hitting a transactional database with live Tableau queries, it can slow the system down. Using extracts that refresh on a schedule (a feature of Tableau Server and Tableau Cloud) allows you to consolidate data requests and protect the performance of your production systems.

Final Thoughts

In the end, "migrated data" in Tableau isn’t a mystery or an error — it’s just another name for a Tableau Extract. It means you’re working with a fast, portable snapshot of your data that's saved directly inside your workbook. While this is great for performance and sharing, remember that it's disconnected from the live source and needs to be refreshed to get the latest updates. Understanding this trade-off is central to becoming a more proficient and confident Tableau developer.

Managing data sources, dealing with extracts vs. live connections, and ensuring everyone has up-to-date reports can sometimes feel like a full-time job. That’s one of the main reasons we designed Graphed. Instead of worrying about data migrations or manual refreshes, you just connect your sources like Shopify, Google Analytics, or Salesforce once. We handle all the data connections in the background, making sure your dashboards are always pulling live, real-time information — no stale data, ever. You can even build a brand new report in seconds just by describing what you want to see, letting you focus on the insights instead of the technical setup.