Skip to content

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

Updated on 2026-09-08

Migrate from Power BI to ingestia.bi

A Power BI → ingestia.bi concept map: what's equivalent, what changes and what doesn't exist yet.

On this page (6)

If you're coming from Power BI, almost everything has an equivalent here — with names in Portuguese and modeling resolved in datalake SQL. This page is an honest concept map: what's equivalent, what changes shape and what doesn't exist yet. We don't promise full parity.

Example workspace: Comércio Aurora Ltda (aurora).

Concept map#

Power BIingestia.biNote
Model (tables + relationships)Semantic modelRelationships become joins in SQL; no in-memory engine.
Star schemaStar schemaSame idea; grain-aware anti-fan-out.
Date table / Mark as date tableCalendar tableFiscal year, 4-4-5, time zone, pt-BR locale.
DAX measuresFormulas (DAX-like, in pt-BR)100+ functions; real filter context.
Calculated columnsCalculated columnsRow by row, with cycle protection.
Calculation groupsCalculation groupsDeterministic precedence; refuses ties.
Parameters / What-ifParameters (field/measure/what-if)The selection travels in the URL/bookmark.
RLS (functions/roles)RLS by attribute (ABAC)One grant serves hundreds of people; fail-closed.
Import / DirectQueryImport / DirectQueryImport = snapshot; DirectQuery with cache.
BookmarksBookmarksPer dashboard (not per user).
Drill-through / tooltip pagesDrill-through / tooltip pagesEquivalent.
Publish + SharePublish and shareDraft × published, public link.
Embed / Publish to webEmbedHMAC token + origin allowlist.
Export PDF/PPTX/ExcelExport datapt-BR XLSX/CSV; PDF/PPTX depends on infrastructure.
.pbix (binary)Open project format + GitDiff per widget/version instead of an opaque binary.

What changes (and why it's good)#

  • Formulas in Portuguese (SOMA, SE, ACUM_ANO) with Brazilian syntax: arguments separated by ;, comma as the decimal separator, VAR … RETORNAR.
  • Native Brazil maps by state/municipality.
  • FinOps per query: a bytes ceiling and the cost in reais on every query.
  • WhatsApp as a delivery/alert channel (official, Cloud API).
  • Automatic anti-fan-out: instead of you discovering an inflated number, the product refuses the wrong aggregation and warns you.
  • Open project + Git instead of the binary .pbix: you can review diffs.

DAX importer (assisted)#

There's an assisted DAX importer with a compliance matrix: it translates what has an equivalent and flags what doesn't, instead of pretending it converted everything. Treat the conversion as a draft to review, not a "magic button".

What does NOT exist yet (be honest in your planning)#

  • A VertiPaq-style scale engine (in-memory columnar): there isn't one. Performance comes from the datalake + snapshot/cache; very large live volumes depend on modeling and on DirectQuery.
  • Power BI's ecosystem/connectivity: the connector catalog is smaller and several connectors are in limited access (see Data).
  • Full DAX: it's a genuine DAX-like language (real filter context), but it doesn't cover 100% of DAX (no virtual tables in the engine).
  • TV mode exists: the dashboard has its own TV layout, which fills the whole screen and refreshes on its own — see TV link. Personal per-user filters are Roadmap.
  • Goals scorecard (Power BI's goals feature) has no equivalent: the Targets screen was removed on 09/26/2026. The target comes in as your own data (a targets table) and becomes a measure — see Measures and formulas.

Suggested migration plan#

  1. Recreate the model

    Build the star schema and the calendar table.

  2. Bring over the measures

    Use the DAX importer as a starting point and review each measure in formulas.

  3. Rebuild the visuals

    Recreate pages/visuals in the editor; apply a theme and conditional formatting.

  4. Set up security

    Recreate RLS by member attribute.

  5. Publish and distribute

Related#


Last reviewed: 2026-09-08.

Related links