Tableau to QuickSight Migration: License Cost, Savings Math and What Breaks in the Move

A Tableau to QuickSight migration usually cuts the license bill by roughly 50 to 80 percent for a typical mid-market team, and the savings are real, but they are not free. On list prices, 40 people cost $14,040 a year on Tableau Cloud Standard and $2,700 to $6,660 a year on Amazon Quick Sight, depending on how many of them need to build and whether anyone turns on the AI features. What eats into that gap is the rebuild: QuickSight itself does not open Tableau workbooks, the official conversion agents are a separate paid purchase, Tableau Prep flows have no QuickSight equivalent, and calculated fields still need checking by an analyst. AWS prices below were read from its pricing page on 26 September 2026.

One housekeeping note before the numbers. AWS has folded QuickSight into a product called Amazon Quick, and the pricing page title now reads "Amazon Quick Sight Pricing", with a space. The old aws.amazon.com/quicksight/pricing address redirects to aws.amazon.com/quick/quicksight/pricing. Same service, same seat types, new name. Most migration guides you will find still use the old one.

How much does it cost to move from Tableau to QuickSight?

There are two separate bills: the licenses you will pay every year afterward, and the one-time cost of rebuilding content. The license side can be calculated exactly from published prices. The rebuild side cannot, because it depends on how many workbooks you have and how complicated their calculations are, and no migration vendor we checked publishes a price.

The license side, on published list prices

Take a normal 40-person analytics footprint: 5 people who build dashboards, 10 who filter, edit and do light analysis, and 25 who only read. On Tableau that maps to Creator, Explorer and Viewer. On QuickSight the role model is simpler. An Author builds and edits; a Reader views, filters, drills and downloads. There is no Explorer tier, so your 10 middle users become either Authors or Readers, and that choice moves the bill more than anything else.

The Tableau rows use Tableau's role prices as last read from tableau.com on 10 September 2026 (tableau.com has refused automated access since then); the full breakdown is on our Tableau pricing page. The QuickSight rows use AWS's page as read on 26 September 2026: Reader $3, Reader Pro $20, Author $24 and Author Pro $40 per user per month, and a $250 per month per account infrastructure fee that applies once the account has at least one Pro user, Q&A enabled through topics, or Dashboard Q&A enabled. Every QuickSight line item, including SPICE storage and the session capacity plans, is on QuickSight pricing.

Two lines in that table are where migration business cases go wrong. The first is the $250 fee. A migration pitched on "$3 Readers" quietly becomes a different number the day someone enables natural-language Q&A so that managers can ask questions, and that fee is charged for the whole account whether one person uses the feature or forty. The second is SPICE, the in-memory store that replaces Tableau extracts. Each Author comes with 10 GB, Readers bring none, and extra capacity is $0.38 per GB per month. Five Authors give you 50 GB. If your Tableau extracts total 200 GB, you are buying 150 GB more, which is $57 a month, small but worth writing into the plan so nobody is surprised.

The rebuild side, which nobody prices publicly

There is no "open Tableau workbook" button in QuickSight. Content moves one of three ways. Your analysts rebuild each dashboard by hand. Or you use the BI migration agents AWS announced for AWS Transform in May 2026, which convert Tableau dashboards into QuickSight datasets, calculated fields, visuals and filters inside your own AWS account; they are built by the AWS partner Wavicle Data Solutions (branded EZConvertBI) and sold as separate AWS Marketplace listings, an Analyzer and a Converter, so assessment and conversion are two purchases. Or you hire a services firm such as Quantiphi, DEFTeam or LeapLogic. We checked the migration pages of all four on 26 September 2026 and none carried a dollar amount; each routes you to a sales conversation. Marketplace purchases do have one real advantage if you hold committed AWS spend: they can draw that commitment down.

For budgeting, count workbooks rather than dashboards, and sort them into three piles: those nobody has opened in 90 days (Tableau's admin views show this), those that are simple charts over one data source, and those with heavy calculations, parameters and actions. The first pile should not be migrated at all. In most Tableau estates it is the biggest one, and deleting it is the cheapest saving in the whole project.

What breaks when you migrate from Tableau to QuickSight?

Most dashboards survive the move in some form. The work concentrates in a few specific places, and knowing them up front is what keeps a migration on schedule.

• Level of detail expressions. Tableau's FIXED, INCLUDE and EXCLUDE have a QuickSight counterpart in level-aware calculations, but the syntax and some behavior differ, so every LOD gets rewritten and retested. This is usually the single largest line of work.
• Tableau Prep flows. QuickSight has no visual prep tool of the same kind. Flows become SQL views in the warehouse, custom SQL datasets, dbt models or an AWS data prep service. If your team leans on Prep, budget for this separately.
• Data blending and extracts. Blends become joined datasets, and .hyper extracts become SPICE datasets with their own refresh schedules. Refresh timing and incremental logic need rechecking.
• Offline authoring. QuickSight authoring is browser only. Analysts used to Tableau Desktop lose the local, offline workflow, and some of them will say so loudly.
• Private databases. If Tableau reaches an on-premises or private database through Tableau Bridge, QuickSight needs a VPC connection into that network instead. That is an infrastructure ticket, not an analyst task, so file it early.
• Visual polish. Highly customized Tableau dashboards with precise layouts, custom shapes and dense map layers rarely look identical in QuickSight. Agree with stakeholders in advance that "equivalent" means the same numbers, not the same pixels.

Row-level security, parameters, table calculations and scheduled email reports all exist in QuickSight, so those move with rework rather than redesign. Test each against the Tableau original with the same filters before you retire anything.

Is QuickSight cheaper than Tableau?

On licenses, yes, by a wide margin, and the gap widens as the reader audience grows. Every extra Tableau Viewer is $15 a month on Standard; every extra QuickSight Reader is $3. For 200 read-only users that difference alone is $28,800 a year. Where QuickSight is not cheaper is the first year, when the rebuild, the retraining and a period of running both tools overlap. A realistic plan keeps both licenses live for one to three months while dashboards are rebuilt and signed off. We compare the two products feature by feature on QuickSight vs Tableau, and if the team is also looking at Microsoft, Tableau to Power BI migration runs the same exercise for Power BI.

A migration plan that protects the savings

1. Inventory and cut. Export usage from Tableau's admin views and drop everything unopened in 90 days.
2. Decide the Explorer question. For each of your middle users, decide Author or Reader. It is the biggest lever on the annual bill.
3. Decide on Q&A before rollout. If managers will want to type questions, budget the $250 monthly fee from day one rather than discovering it on the first invoice.
4. Move data first. Recreate Prep flows as SQL views or dbt models so QuickSight datasets can be thin.
5. Rebuild the top 20 dashboards by usage, validate the numbers side by side, then retire the Tableau versions.
6. Retrain. Readers need an hour; Authors need a few sessions. Running it as a short self-paced course on a corporate training platform beats a single live call that half the team misses.
7. Cancel Tableau at renewal, not before, and not a year after.

The questions a migration will not fix

One thing migrations rarely change is the queue of one-off questions to the data team. Moving from Tableau to QuickSight changes where dashboards live; it does not create the dashboard for the question nobody anticipated, such as which enterprise accounts downgraded in the last 60 days. Those still land on an analyst's desk, now with a rebuild project competing for the same hours.

That is the gap AgentSQL covers. If your data sits in PostgreSQL or MySQL (including RDS and Aurora), Snowflake or BigQuery, it connects read-only, reads your schema, turns a plain-English question into SQL, runs it and returns the number, a chart and the query it wrote. It does not replace QuickSight dashboards and it does not connect to Redshift or Athena today. It is priced flat, from $39 a month billed yearly, with no per-question meter and no account fee, which makes it a predictable addition next to a QuickSight rollout that has deliberately left Q&A switched off. Try a question in the console at the top of this page, or see how it works on text to SQL.