Skip to main content
Back to timeline
Databricks BlogSource publication:

Databricks turns dashboard migration into folder-level batches: one Genie Code command converts a whole set of Tableau or Power BI reports

Synopsis

Genie Code in Databricks now supports bulk migration: place a whole folder of Tableau or Power BI report files in a Unity Catalog volume, and a single /importBI command has the migration agent generate AI/BI dashboards report by report and map them to a chosen catalog and schema. Previously /importBI handled one report at a time, fine for a pilot but turning dozens or hundreds of accumulated reports into repeated manual work. The bulk flow queues reports, processes a few at a time in separate background jobs, and reuses existing Unity Catalog tables and views where it can.

Source-provided article image: Bulk migrate your dashboards to AI/BI with Genie Code
Databricks Blog

Interpretation

The migration entry point expands from a single report to an entire folder: put a batch of Tableau or Power BI report files in one directory of a Unity Catalog volume, and an /importBI command pointed at that directory triggers the bulk flow across every report in it rather than importing one. The earlier /importBI flow migrated one report at a time and suited a pilot; moving the dozens or hundreds of reports an organization accumulates over years one by one turns modernization into months of manual repetition. The feature is generally available and usable in a workspace today, provided partner-powered AI features are enabled at both the account and workspace levels; the file count and size limits for a single bulk import follow the public /importBI documentation.

The agent reads the source BI files, generates the corresponding AI/BI dashboards, and lands the migrated metric views and SQL views in the target catalog and schema the user specifies. Single-file migration also runs through Genie Code's planning phase, parsing and assessing the workbook, enumerating the semantic layer, creating metric views, building dashboard pages and validating the migration; bulk mode runs that plan for each report. Supported source formats are .twb, .twbx, .tds, .tdsx, .pbit and .tmdl; the agent matches each Tableau workbook to its companion data source file on its own and checks with the user when a pairing is unclear.

A bulk run proceeds as a queue, and a status card marks each report as queued, running or completed, so a user can stop an individual report or halt everything still in flight. Each report runs in its own background job, so there is no need to keep the tab open; the original chat can be reopened from Genie Code history to check progress. Each file name on the status card links to that report's own Genie Code conversation, where a run that pauses to ask a question can be answered and the migration resumes from where it stopped; each report reuses existing Unity Catalog tables and views where it can before creating new ones.

Perspective

The flow is for teams that have already tried /importBI on a report or two and are ready to scale up, and its inputs must be supported-format files staged in a directory of a Unity Catalog volume; dragging files straight into the chat works only for one-off, single-report imports.

Completed means the run finished, not that every visual is final; differences between a migrated dashboard and the original often stem from data freshness, differing default filters, or calculation semantics such as distinct counts, level-of-detail expressions and time intelligence, and do not always mean a migration error.