Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

Migrate visuals to the Import model

Assisted migration, one visual at a time — check whether the visual translates, compare the numbers before and after, migrate and undo. Nothing changes on its own.

On this page (7)

Text in bold is the name as it appears on screen.

In an older dashboard, each visual may have its own query to the datalake, run again on every refresh. In the Import model, the dashboard uses an extract of each table, and each visual is sliced from that extract. Fewer queries, lower cost, same number.

The Import model is available to all workspaces. A visual built from the Fields list already reads the extract; an older visual, with its own query, moves to it through this migration, dashboard by dashboard. The migration is assisted: the product shows what can be moved over, compares the numbers and waits for you to decide. Nothing changes on its own, and everything can be undone.

To understand the data modes, see Data modes: Import, DirectQuery and cache.

Before you start#

  • You need permission to edit the dashboard. For read-only users, the button doesn't appear.
  • The table's extract must exist. If it doesn't, the preview warns you: "No extract of … — run "Refresh now"."

Open the migration#

In edit mode, go to the Data ribbon, Import model group, and click Migrate visuals.

The Import model — assisted migration screen opens. At the top is the dashboard's tally: how many visuals are already served by the extract, how many translate and how many have already been migrated. Below are the visuals with queries, grouped by page.

Import model — assisted migration screen, with the list of visuals by page and the Translatable, Not translatable, Migrated and Already by fields badges

What each badge means#

BadgeMeaning
TranslatableThis visual's query can be redone as a slice of the extract
Not translatable: …It can't be moved over; the reason is written next to it. The visual stays as it is
MigratedIt's already sliced from the extract. You can Undo it
Already by fieldsIt was built from the Fields list — it already uses the extract, there's nothing to migrate

Migrate a visual#

  1. 1. Click See before and after

    The product slices the extract the way the visual asks and compares it with what the card shows today, group by group and column by column.

  2. 2. Read the result

    Equal: the extract's numbers match today's. — you can migrate. The numbers DON'T match. — a table appears with Group, Column, Before and After for each difference.

  3. 3. Click Migrate

    The button is only enabled after you've seen the before and after. If the numbers don't match, first check I checked the differences — migrate anyway.

  4. 4. Confirm

    The confirmation explains what will happen and the action is Migrate (or Migrate anyway). At the end you'll see "… migrated."

Before and after of a visual: the Equal message or the Group, Column, Before and After table, with the Migrate and Undo buttons

When the numbers don't match

If you migrate anyway, the visual starts showing the extract's numbers. Check the differences first: sometimes it's a filter or a calculation that the old query did differently. If the differences table says "No columns in common to compare", check the names before migrating.

Undo#

On a Migrated visual, click Undo and confirm. The visual goes back to using the query that was kept and leaves the extract. What it shows now stays until the next refresh.

Limits#

  • One visual at a time. There's no "migrate all".
  • Some calculations can't be redone from the extract. Those visuals appear as Not translatable, with the reason, and stay as they are.
  • The canvas doesn't change: the visual's position, size and format stay the same.

Next task#

Related links