# Bulk migrate your dashboards to AI/BI with Genie Code

> Source: <https://www.databricks.com/blog/bulk-migrate-your-dashboards-aibi-genie-code>
> Published: 2026-11-19 16:00:00+00:00

**Key takeaway:** Pointing /importBI at a Unity Catalog volume directory instead of a single file converts every Tableau or Power BI report in that folder (.twb, .twbx, .tds, .tdsx, .pbit, .tmdl) into AI/BI Dashboards in one run, mapped to a chosen catalog and schema.

How to move many Tableau and Power BI reports to AI/BI Dashboards in a single /importBI run, then review and refine each one with Genie Code.

by  [Dipankar Kushari](https://www.databricks.com/blog/author/dipankar-kushari)  and  [Archana Shetty](https://www.databricks.com/blog/author/archana-shetty) 

In our previous post, [Migrate Your Dashboards to AI/BI with Genie Code](https://community.databricks.com/t5/technical-blog/migrate-your-dashboards-to-ai-bi-with-genie-code/ba-p/164326), we walked through moving a single Tableau or Power BI report onto Databricks AI/BI with the [/importBI](https://docs.databricks.com/dashboards/manage/import-bi) skill in Genie Code. That one-report-at-a-time flow is perfect for a pilot — but most organizations have hundreds of reports built up over years, and migrating them individually turns a strategic modernization effort into a months-long manual grind.

Bulk migration of dashboards changes that. You can now point the migration agent at an entire folder of reports and have them converted to [AI/BI Dashboards](https://www.databricks.com/product/business-intelligence/ai-bi-dashboards) in a single run — no more kicking off migrations report by report.

This guide is for you if:

`/importBI` on a report or two and are ready to scale up.
Bulk migration extends the Databricks AI/BI migration experience so that instead of importing one report at a time, you can process many reports together from a single command. The migration agent reads your source BI files, generates the corresponding AI/BI Dashboards on Databricks, and maps them to the target catalog and schema you specify.

This feature is now generally available, and so it's ready to use in your workspace today. Before you begin, check that [partner-powered AI features](https://docs.databricks.com/databricks-ai/partner-powered) are enabled at both the account and workspace levels.

For teams standardizing on Databricks AI/BI, bulk migration removes the single biggest bottleneck in a large-scale dashboard migration: the sheer repetition of moving reports one at a time. By migrating an entire folder of Tableau or Power BI reports into a single run — and landing them directly in your chosen catalog and schema — you can shift a migration project from a manual backlog to a repeatable, folder-at-a-time workflow.

The playbook below walks through a bulk migration end to end. It is grouped into three phases:

| Phase | Steps | 
|---|---|
| Prepare | (1) Export your BI reports (2) Stage them in a Unity Catalog volume | 
| Run | (3) Start the bulk import (4) Choose the target catalog and schema (5) Track the batch | 
| Review & refine | (6) Review each report (7) Follow the migration plan (8) Refine and polish | 

Export each Tableau or Power BI report you want to migrate to a supported file type. This includes: .twb, .twbx, .tds, .tdsx, .pbit, or .tmdl. The [Tableau export documentation](https://help.tableau.com/current/pro/desktop/en-us/export.htm) and [Power BI report templates](https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-templates) guides walk you through the export.

*Tip: Working with a Tableau workbook that connects to a published data source? Export that data source as well (.tds or .tdsx) and keep it next to the workbook.*

Place the BI report files you want to migrate into a [directory within a Unity Catalog volume](https://docs.databricks.com/aws/en/volumes/). Keeping them together in one folder lets you migrate them in a batch. A bulk run always picks up its files from the volume; dragging files straight into the chat only works for one-off, single-report imports.

From a draft dashboard, open Genie Code and submit:

`/importBI <path/to/volume/directory>`

*Above: Running /importBI against a volume directory from a draft dashboard.*

Pointing the command at the directory (rather than a single file) triggers the bulk flow across all reports in that folder.

If you prefer natural language, a request such as “Migrate every Power BI report in /Volumes/finance/bi/reports to AI/BI Dashboards” works just as well.

You can also name specific files instead of a whole folder: “Migrate Tableau reports Dashboard1.twb, Dashboard2.twb in /Volumes/finance/bi/reports to AI/BI Dashboards”.

Finally, you should add guidance that applies to the entire batch — for example, asking Genie Code to "build only the metric views".

The agent recognizes the batch and lists the reports it found in the volume, matching each Tableau workbook to its companion data source file on its own and checking with you if a pairing is unclear. It then prompts you for the destination catalog and schema so the migrated dashboards' metric views and SQL views land in the right place.

*Above: Genie Code lists the reports it found and asks for the target catalog and schema.*

After you've checked the file list and given the go-ahead, the bulk migration kicks off, and a status panel shows each report as it starts. Reports are queued and processed a few at a time, and each report reuses existing Unity Catalog tables and views where it can before creating new ones.

Note: For the current limits on the number and size of files supported in a single bulk import, always refer to the public documentation on [`/importBI`](https://docs.databricks.com/dashboards/manage/import-bi#import-multiple-files-in-bulk).

A status card in the chat keeps a running tally of the batch, with each report marked as Queued (not started), Running, or Completed (session ended). You can stop an individual report, or halt everything still in flight, from the same card.

*Above: The status card tracks every report in the batch.*

Because each report runs in its own background job, there's no need to keep the tab open — come back to the original chat in your Genie Code history at any time to see how the batch is progressing.

Each file name on the status card links to that report's own Genie Code conversation, which opens in a separate tab. If a run stops to ask a question, answer it there, and the migration picks up where it left off.

*Above: A run that paused to ask for input. In this example, the published data source behind the workbook.*

As with a single-file `/importBI` migration, each report runs through the Genie Code planning phase — for example, parsing and assessing the workbook, enumerating the semantic layer, creating metric views, building the dashboard pages, and validating the migration.

*Above: The migration plan for a single report, tracked step by step.*

Once the plan execution completes, you can view the finished AI/BI dashboard produced by the migration. You can further enhance or customize it with follow-up Genie Code prompts. Every Genie Code response can be undone as a single step, so it's safe to experiment, and you can even ask Genie Code to beautify the dashboard's look and feel.

*Above: A finished AI/BI dashboard produced by the bulk migration.*

Before you retire a source report, check that the migrated dashboard gives the same answers as the original.

**Tip:** If you've connected Tableau or Power BI via a read-only MCP connection (see the cheat sheet below), Genie Code can check the numbers against the live report directly rather than reading values from a screenshot.

Set things up well before you run `/importBI` to get the most faithful migration on the first pass:

| Best practice | Details | 
|---|---|
| Connect your source BI tool via MCP (optional/recommended) | • Set up a read-only MCP connection to Tableau or Power BI so Genie Code can use the live report as the source of truth, validating results against the original rather than relying solely on the exported file, which meaningfully improves accuracy.  | 
| Upload the shared or published data-source definitions | • In Tableau, export any published data source to its own .tds file; in Power BI, export the shared data model as a .pbit. Upload these alongside the report so the agent sees the full semantic layer. | 
| Make sure the underlying data is reachable in Databricks | • Migrated dashboards map to Unity Catalog tables (via Lakeflow Connect, Lakehouse Federation, or existing UC tables).  Example: *“The source tables for this report as available in dev.finance schema”* *“Use prod.finance.table1, prod.finance.table2 and prod.finance.mv_revenue as the source for this report”* | 
| Add screenshots of the original dashboard | • Uploading “before” screenshots into the Genie Code chat significantly improves visual and layout fidelity. **Tip:** Save screenshots of your original dashboards to a Unity Catalog volume before you migrate, so you can reference them by path in Genie Code prompt. | 
| Expect to refine with a follow-up prompt | • Treat Genie Code like any AI agent — a second prompt to adjust a chart, filter, or calculation after the first pass is normal. | 
| Promote finished metric views to Unity Catalog | • Tableau imports produce dashboard-scoped (local) metric views by default, while Power BI imports produce Unity Catalog metric views.  | 
| Check the documented file limits | • File count and size limits can change, so always refer to the [public /importBI documentation](https://docs.databricks.com/aws/en/dashboards/manage/import-bi#import-multiple-files-in-bulk) for the current limits.  | 
| Review each result before you trust it | • “Completed” means the run finished, not that every visual is final. Validate each report before you close its session. | 

Moving hundreds of Tableau or Power BI reports to Databricks AI/BI no longer has to mean hundreds of individual migrations. With bulk migration, you prepare a folder of reports once, run a single `/importBI` command, and let Genie Code work through the batch in the background while you review and refine each result.

If you're planning a BI modernization effort, upload a folder of reports to a Unity Catalog volume and try `/importBI` from a draft dashboard to see bulk migration in action.

If you’re ready to get started, just put your report files in a Unity Catalog volume, open a draft dashboard, and run `/importBI` in Genie Code.

For step-by-step details, see the documentation on [importing BI files with Genie Code](https://docs.databricks.com/dashboards/manage/import-bi). If you're new to AI/BI, start with our earlier post: [Migrate your Dashboards to AI/BI with Genie Code](https://community.databricks.com/t5/technical-blog/migrate-your-dashboards-to-ai-bi-with-genie-code/ba-p/164326). You should also read the [bulk migration product documentation](https://docs.databricks.com/dashboards/manage/import-bi#import-multiple-files-in-bulk).

**Q: What is bulk migration for Databricks AI/BI?**

A: Bulk migration allows you to process many Tableau or Power BI reports together in a single run, instead of importing one report at a time. The migration agent reads your source BI files, generates the corresponding AI/BI dashboards on Databricks, and maps them to your target catalog and schema.

**Q: What file formats does bulk migration support?**

A: Bulk migration supports .twb, .twbx, .tds, .tdsx, .pbit, and .tmdl file formats from Tableau and Power BI reports.

**Q: Where do I need to store my BI report files for bulk migration?**

A: Store all the BI report files you want to migrate in a directory within a Unity Catalog volume. You can then point the /importBI command at that directory to trigger the bulk migration workflow.

**Q: How do I start a bulk migration in Genie Code?**

A: From a draft dashboard, open Genie Code and submit the command /importBI <path/to/volume/directory>. You can also use natural language, such as "Migrate every Power BI report in /Volumes/finance/bi/reports to AI/BI dashboards."

**Q: What do I do after the bulk migration completes?**

A: After completion, you can review each migrated dashboard, compare it with the original report, and use Genie Code prompts to refine or customize the dashboard. You can also promote local metric views to Unity Catalog so they can be reused by other dashboards and applications.

Subscribe to our blog and get the latest posts delivered to your inbox.
