• 17 Sep 2026

Tableau to Amazon QuickSight: LOD, SPICE, and Security

Tableau has long led visual analytics, but per-seat licensing at scale, the overhead of self-hosted deployments, and the shift toward a serverless, AWS-aligned stack are leading many organizations to reconsider. A Tableau-to-Amazon QuickSight migration moves Tableau workbooks, data sources, and dashboards to Amazon QuickSight, AWS's fully managed BI service. This guide explains why enterprises migrate, how Tableau concepts map to QuickSight, the migration process, common challenges, and best practices, including the parts that genuinely need rethinking rather than copying.

Quick Summary

Tableau to Amazon QuickSight migration is a re-implementation, not a one-to-one copy: QuickSight doesn't mirror Tableau's visual range or LOD behavior directly, so LOD-heavy and highly custom dashboards need redesign rather than copy-paste. Tableau Hyper extracts map to SPICE (in-memory), live connections to Direct Query, and LOD expressions to Level-Aware Calculations. The main draws are pay-per-session pricing, serverless scale, and native AWS integration; the main effort is calculation and visual parity, validated through a phased, parallel-run migration.

Key Terms

• LOD (Level of Detail) — A Tableau-specific calculation feature that controls which dimensions a calculation considers, independent of what's on the current view (e.g., {FIXED [Customer]: SUM([Sales])}). QuickSight has no direct equivalent; the closest counterpart is Level-Aware Calculations, below.
• LAC-A / LAC-W (Level-Aware Calculations) — QuickSight's own mechanism for LOD-style logic, computing at a chosen point in the query's evaluation order (Aggregation or Window). LOD expressions are re-expressed as LAC-A/LAC-W, not translated line by line.
• SPICE (Super-fast, Parallel, In-memory Calculation Engine) — QuickSight's in-memory storage and query engine. Data loaded into SPICE is cached for fast dashboard performance, similar in purpose to a Tableau Hyper extract. SPICE caps the combined size of secondary tables in a join, which is why heavy joins are usually resolved upstream instead.
• Direct Query — QuickSight's live-query mode, querying the source database directly rather than caching data in SPICE. Maps to Tableau's live connections.

Key Takeaways

• Tableau to Amazon QuickSight migration moves Tableau reporting onto QuickSight, AWS's serverless, cloud-native BI service.
• It is a re-implementation, not a one-to-one copy: QuickSight does not mirror Tableau's visual range or LOD behavior directly, so LOD-heavy and highly custom dashboards need redesign rather than copy-paste.
• Tableau Hyper extracts map to SPICE (in-memory), live connections to Direct Query, and LOD expressions to Level-Aware Calculations.
• QuickSight has been renamed twice, to Amazon Quick Suite, then to Amazon Quick, but the underlying BI engine hasn't changed.
• Governance is best handled upstream in Redshift or Athena so QuickSight datasets stay clean; security uses Row-Level and Column-Level Security with IAM Identity Center.
• The main draws are pay-per-session pricing, serverless scale, and native AWS integration; the main effort is calculation and visual parity.
• A phased approach with a parallel run and side-by-side validation before cutover reduces risk, and accelerators can assess complexity and flag unsupported chart types up front.

What Is Tableau to Amazon QuickSight Migration?

Tableau to Amazon QuickSight migration is the process of moving reports, dashboards, and the reporting data layer from Tableau, Tableau Desktop for authoring and Tableau Server or Cloud for sharing, onto Amazon QuickSight. QuickSight is AWS's fully managed, serverless BI service: it connects to AWS and third-party sources, stores data in SPICE (its in-memory engine) or queries it live with Direct Query, and lets users build datasets, analyses, and dashboards, plus paginated reports for pixel-perfect output.

A re-implementation, not a copy. Tableau and QuickSight approach analytics differently, so migration recreates each workbook using its QuickSight equivalent rather than converting files one-to-one. The most important thing to accept early is that QuickSight is not a drop-in replacement for Tableau's visual sophistication: its chart range and calculation model are narrower, and it does not reproduce Level of Detail (LOD) behavior directly. Attempting a pixel-for-pixel recreation of an LOD-heavy Tableau dashboard often disappoints and can hurt performance. Treating the project as a redesign, keeping the business question, and rethinking the delivery is what makes it succeed, the same redesign-not-replicate principle covered in our Cognos to AWS QuickSight migration guide for a different source platform on the same target.

A Note on Naming: QuickSight, Quick Suite, and Amazon Quick

If you've seen references to "Amazon Quick Suite" or simply "Amazon Quick" alongside QuickSight, that's not a different product; it's the same one, renamed twice. AWS rebranded QuickSight to Amazon Quick Suite on October 9, 2025, bundling it with new AI-driven capabilities, then shortened the name again to Amazon Quick sometime in 2026. The underlying BI engine and SPICE are unchanged; QuickSight now exists as a component (styled "Quick Sight") inside the broader Amazon Quick product. This guide uses "Amazon QuickSight," since that remains the name most commonly searched and referenced, but don't be thrown if you see "Quick Suite" or "Quick" in AWS's own current documentation; they're the same target platform.

Why Enterprises Migrate from Tableau to Amazon QuickSight

Several factors drive the move, especially for AWS-centric organizations:

• Cost and pricing model. QuickSight's pay-per-session reader pricing can save significantly compared with Tableau's per-user licensing, especially when many users are occasional viewers; our QuickSight vs Tableau pricing comparison covers the same cost trade-off. Some vendors cite total cost of ownership reductions in the 60-70% range over three years; treat these vendor-reported figures as a starting point to model against your own workload, not a guaranteed outcome.
• Serverless, no infrastructure. QuickSight scales automatically and removes the servers and capacity management a self-hosted Tableau deployment requires.
• AWS ecosystem integration. Native, low-friction connectivity to Redshift, Athena, S3, RDS/Aurora, IAM, and Lake Formation, often with fewer network hops and no data egress fees within AWS.
• SPICE performance. The in-memory engine serves fast, concurrent dashboards over very large datasets.
• Generative BI. Amazon Q in QuickSight adds natural-language Q&A, executive summaries, and data stories, letting stakeholders ask plain-English questions and auto-generate charts and calculations.
• Embedded analytics economics. Dashboards can be embedded and served to large audiences without infrastructure work.

Tableau retains real strengths, best-in-class visual analytics, flexible LOD calculations, Tableau Prep, and a large community, so the trade is deliberate: QuickSight exchanges some visual and calculation depth for serverless simplicity, AWS-native integration, and cost efficiency. The fit is strongest for AWS-centric organizations with many occasional users, the same fit-first framing covered in our broader Amazon QuickSight vs Tableau comparison.

Mapping Tableau to Amazon QuickSight

A successful migration rests on mapping each Tableau construct to its QuickSight equivalent. The table below summarizes the most common mappings:

The mappings that need the most care are the calculations and the visuals.

Calculations

Standard Tableau calculated fields translate to QuickSight calculated fields, though the function sets differ, so validate each result. The harder case is Level of Detail (LOD) expressions: QuickSight uses Level-Aware Calculations (LAC-A and LAC-W), which compute at a chosen point in the query evaluation order. They can reproduce most LOD outcomes, but you usually have to re-express the logic rather than paste it across, and doing so thoughtfully protects SPICE performance. Table calculations map to QuickSight table calculations and window functions.

Visuals

Common visuals- bar, line, pie, KPI, tables, pivot tables, maps- map directly. However, Tableau's more advanced or highly customized chart types don't all have a one-to-one equivalent: Symbol Maps become Point Maps, Circle Views and Side-by-Side Circles become Stacked Bar charts, and Packed Bubbles are typically rebuilt as Custom Scatter Plots. Tableau Stories have no direct counterpart either; they are approximated with tabs, multiple sheets, or Amazon Q data stories. By assessing unsupported visuals early, accelerators can flag them and keep surprises out of the build phase.

Data and performance

Tableau Hyper extracts map to SPICE for fast, concurrent access, while live connections map to Direct Query. One practical limit to plan for: SPICE caps the combined size of secondary tables in a join, so heavy joins are best resolved upstream. Curating the data as governed views or star schemas in Redshift or Athena keeps QuickSight datasets clean and performant, the same upstream-governance discipline covered in our Cognos to AWS QuickSight migration guide.

The Migration Process

A typical enterprise migration follows a clear sequence:

• Inventory and assess. Catalog workbooks and data sources, and use assessment accelerators to flag complexity, LOD expressions, custom chart types, and complex joins. Auditing actual dashboard utilization often reveals that a large share of legacy content is stale and can be dropped from scope before conversion begins.
• Rationalize. Retire duplicate and unused dashboards so you migrate only what the business still needs.
• Design the AWS target. Plan the QuickSight account and edition, the upstream data layer, SPICE capacity, and identity.
• Build data and datasets. Curate governed views or star schemas upstream and define QuickSight datasets, choosing SPICE or Direct Query per dataset.
• Convert calculations. Translate calculated fields, re-express LOD logic as Level-Aware Calculations, and validate every result, the same conversion-and-validate discipline covered in our guide to automating ETL testing with Python.
• Rebuild visuals and dashboards. Recreate content as analyses and dashboards, redesigning rather than copying, with parameters, controls, and actions.
• Rebuild pixel-perfect output. Route dense or print-ready reports to QuickSight paginated reports.
• Configure security and delivery. Apply Row-Level and Column-Level Security, map identities through IAM Identity Center, and set up scheduled delivery and Snapshot Export.
• Parallel run and validate. Run Tableau and QuickSight side by side, reconcile the results, then cut over and decommission Tableau, the same side-by-side reconciliation covered in our key checklist for BI modernization.

A standard, zero-disruption rollout is commonly cited in the three-to-six-month range depending on dashboard count, though your own inventory and complexity assessment is a more reliable estimate than any general figure.

Migration Accelerators and AWS Transform

Several named tools and services specifically target this migration path. AWS Transform offers chat-based BI Migration Agents built into its workflow: they connect via API to your Tableau Cloud or Server environment for automated assessment, rebuild datasets, filters, calculated fields, and visualizations through AI-powered conversion, and keep computation, extraction, and code translation inside your own AWS account perimeter. Commercial accelerators available through AWS Marketplace include LeapLogic, MigratorIQ4Tableau, and EZConvertBI, alongside migration services from partners like Wavicle Data Solutions.

Vendor-reported automation coverage varies by source; one accelerator claims automated conversion of up to 80% of workflows, with roughly 15-25% of highly complex, nested calculations needing human structural redesign. Treat these as directional estimates specific to that vendor's tooling and your own workbook complexity, not universal figures, and pilot any accelerator against a representative batch of your own dashboards before trusting it with production content, the same pilot-first discipline covered in our key checklist for BI modernization.

Common Challenges

• Visual parity. Some Tableau chart types and formatting have no direct equivalent; flag them early and redesign rather than force a match.
• LOD expressions. QuickSight does not mirror LOD directly; re-express the logic as Level-Aware Calculations and validate, since copy-paste can degrade SPICE performance.
• Table calculations. Map to QuickSight table calculations and window functions, checking edge cases.
• Tableau Prep flows. Light shaping moves into dataset prep; heavier transformation belongs in AWS Glue or the upstream data layer.
• SPICE limits and capacity. Plan around the secondary-join size cap and in-memory capacity, and set refresh schedules for predictable cost and speed.
• Stories. There is no direct Story equivalent; rebuild the narrative with tabs, sheets, or Amazon Q data stories.
• Security model. Tableau user filters and entitlement tables map to QuickSight Row-Level and Column-Level Security rules.
• Timeline realism. Governance, security, and testing take time; a large estate takes months, not weeks.

Best Practices for a Successful Migration

• Assess complexity first. Use accelerators to score workbooks, flag unsupported visuals and LOD logic, and rationalize duplicates before building.
• Redesign, don't replicate. Keep the business question and rebuild for QuickSight's strengths, rather than chasing a pixel-perfect copy.
• Re-express LOD deliberately. Convert LOD expressions to Level-Aware Calculations and validate them against the originals.
• Govern the data upstream. Curate views or star schemas in Redshift or Athena so datasets stay clean and joins stay light, the same upstream-governance principle covered in our ETL Solutions overview.
• Choose SPICE or Direct Query deliberately. SPICE for fast, concurrent dashboards; Direct Query for freshness or very large live data.
• Run in parallel. Keep Tableau available during a transition and validate parity before cutover to build user confidence.
• Plan security and identity early. Design Row-Level and Column-Level Security and IAM Identity Center up front.
• Model cost and enable users. Estimate reader sessions and author roles, and train users on QuickSight's authoring model, the same enablement discipline covered in our key checklist for BI modernization.

Case Study: Consolidating Tableau on Amazon QuickSight

The following is an illustrative example, not an account of a specific customer engagement. No customer names, figures, or performance results are implied.

Consider an AWS-centric enterprise running Tableau Server with hundreds of workbooks, a large population of occasional viewers, and rising per-seat licensing and infrastructure costs. The organization wants to consolidate analytics on AWS and reduce viewer licensing overhead.

A migration could address this by first inventorying and scoring the workbooks with an assessment accelerator, retiring duplicates, and flagging LOD-heavy and custom-visual dashboards for redesign. The reporting data would be curated as governed views in Amazon Redshift, with QuickSight datasets defined on top, using SPICE for high-traffic dashboards and Direct Query where freshness matters. Calculated fields and LOD logic would be re-expressed as QuickSight calculated fields and Level-Aware Calculations, dashboards rebuilt for QuickSight rather than copied, and dense reports moved to paginated reports. Security would be reproduced with Row-Level and Column-Level Security through IAM Identity Center, and the two platforms run in parallel until parity was confirmed.

Qualitatively, the likely outcomes are a serverless, AWS-native analytics platform, materially lower viewer licensing costs, fast SPICE-backed dashboards, and access to generative BI, with dashboards redesigned to work well in QuickSight rather than being forced to imitate Tableau.

Frequently Asked Questions

Related Reading

• Amazon QuickSight vs Tableau
• QuickSight vs Tableau: 2025 Pricing and Features
• Cognos to AWS QuickSight Migration
• Oracle BI Publisher to Amazon QuickSight Migration
• Unique Features of Amazon QuickSight
• Tableau to Microsoft Fabric Migration
• Tableau to Power BI Migration
• Automating ETL Testing with Python: Data Validation
• ETL Solutions
• Key Checklist for Successful BI Modernization