Transformations / bi consolidation

Stop Renting Your Dashboards

You didn’t set out to run twelve BI tools. TextQL rebuilds the dashboards that matter as code in your own repository — governed, refreshed and yours — reconciles every number, and retires the rest.

[ the difference ]

Your BI Estate, Before and After

today
  • A dozen BI tools nobody chose on purpose
  • A new seat every time someone needs to look
  • Business logic trapped in each vendor’s format
  • Migration quoted as a multi-year program
with textql
  • One governed layer, every dashboard as code
  • Dashboards shared without buying another seat
  • Metrics defined once, in your own repository
  • A fixed-scope move, measured in dashboards and weeks
[ 01 consolidate ]

Every BI Tool Into One Layer You Own

Workbooks, calculated fields, LookML and Cognos universes are parsed into governed metrics and dashboards-as-code. The meaning survives; the vendor’s syntax doesn’t have to.

  1. Calculated fields become reviewed metric definitions
  2. Scheduled emails become playbooks — usually better ones
  3. Row-level access carried over from the warehouse
one workbook, taken apart 1 file → 4 files
Tableau rev_exec.twb calculated field [rev_adj] metricontology/net_revenue.tqlworksheet · 6 views dashboarddashboards/exec_revenue.tsxuser filter · region accessontology/access.tqlemail subscription playbookplaybooks/monday_exec.yml / your-org/analytics
[ 02 reconcile ]

Every Number Proven Before Anything Is Switched Off

Each rebuilt dashboard is tested against golden values finance already trusts. When the numbers disagree, the difference is traced to its cause — and sometimes the migration finds a number that was always wrong.

  1. Parity tests run on every rebuilt panel
  2. Differences traced: time window, then definition, then data
  3. Sign-off recorded before the old workbook retires
net revenue · q3 off by $0.7M
tableau $48.9M your repo $48.2M
+$0.7M returns counted twice calculated field [rev_adj]
The rebuilt number is $0.7M lower. A migration bug?
[ customer story ]
client
withheld at client request
profile
global · fortune 50 · healthcare
file
tableau → textql
status
closed · tableau switched off
4,200 310 workbooks → dashboards kept, as code
  • 11,000 0 tableau seats renewed
  • 14 1 versions of net revenue
A global Fortune 50 healthcare company

Tableau, switched off. The dashboards that matter, kept as code.

We stopped renting our dashboards. Everything finance looks at on a Monday now lives in our repo, reviewed like code — and for the first time the numbers agree across the business.

VP, Data & Analytics, a global Fortune 50 healthcare company
16 weeks
from inventory to switching Tableau off
100%
of rebuilt numbers reconciled before cutover
1 repo
owned by the company, not a vendor
[ the migration ]

Three Steps, One Dashboard Family at a Time

The same path every time, sized by what your people actually open — so you migrate dozens of dashboards, not thousands.

  1. 01 / find Find What’s Alive Every workbook, owner and open count, inventoried. Most of the estate turns out to be unused. the zombie list
  2. 02 / rebuild Rebuild and Prove It The dashboards people open, rebuilt as code in your repo and reconciled to the numbers finance trusts. Old and new run side by side until usage moves over. parity signed off
  3. 03 / switch off Retire the Rest Unused workbooks and the seats behind them go. The logic you kept lives in your repository. seats returned

Assess a BI Migration

Bring one dashboard family. We inventory it, rebuild the one that matters as code, and reconcile every number with your team — then you decide what to retire.

  1. 01A 30-minute call to pick the dashboard family and the tools behind it
  2. 02We inventory usage and rebuild the flagship inside your cloud
  3. 03Your team signs off parity before anything is switched off
[ use cases ]

Where Consolidation Starts

  • 01 Tableau migration

    Parse workbooks and calculated fields into governed metrics, rebuild the dashboards people open, and retire the server on your timeline.

  • 02 Power BI and Looker consolidation

    DAX measures and LookML explores translated into one set of definitions, so the same metric means the same thing everywhere.

  • 03 Cognos and BusinessObjects retirement

    Capture the business logic trapped in decades-old universes before the people who wrote it retire, and move it into code you own.

  • 04 Scheduled reports into playbooks

    Email subscriptions become scheduled playbooks that explain the numbers they send, not just attach them.

  • 05 Embedded and customer-facing dashboards

    Rebuilt dashboards embedded in your own portal, white-labeled and governed by the same permissions.

  • 06 Conversational analytics, governed

    Replace the AI-made HTML dashboards that never refresh with ones that refresh, share safely and respect row-level access.

[ faq ]

What Teams Ask Before They Start

No. The inventory finds what people actually open. Unused workbooks are retired, and every remaining asset is sorted into rebuild, keep, consolidate or retire — so the real scope is usually a fraction of the estate.

[ try textql ]

Bring Us Your Hardest Problem