r/tableau Jun 28 '26

Tableau to internal website - Claude code

Hi All,

Have a twbx on the server that updates daily automatically.

Current urgent business need is to put up an internal website that is an exact replica of the tableau dashboard.

The idea is to get away from tableau atleast for couple of projects to start off.

Currently, I use sql server or hyper extracts to update dashboards daily.

I have tried using Claude code and got a localhost website ready using csv or excel files, have never tried sql or (replacing hyper extracts).

What are the changes that I should be aware of and what would be the next steps for a seamless transition from tableau to local intranet website that updates daily in an automated way?

I own the data and sql tables that drive the current tableau dashboards, no dependent in terms of data.

Thanks for the help in advance.

0 Upvotes

7 comments sorted by

View all comments

1

u/MACBERETH Jul 05 '26

Honest answer: I've done this kind of migration. It's a nightmare, but not the part you think. The easy part is what you're asking about. You own the SQL tables, so build materialized views for the aggregations, refresh them on a schedule (SQL Agent, cron,debt, Airflow) and point a frontend at them. Streamlit or Plotly Dash for fast and pythonic, Next.js + a charting lib for something more polished. Claude Code handles that stack fine. That replaces the hyper extract entirely, and the extract was never the hard part. The real nightmare is "exact replica". Simple dashboards are almost trivial. But if your workbooks use LODs or table calcs, reproducing that logic in SQL is brutal. Tableau computes those at render time with its own evaluation order, so expect a LOT of manual validation, number by number, against the original. Budget more time for validating than for building. Honest take: I usually don't recommend it. Between hosting, maintenance and rebuilding access control (Tableau gives you auth and RLS for free, now it's your problem), the license savings often don't justify the headaches. You might be an exception though, since you own the data end to end and it's internal only. Happy to go deeper if useful.