Product knowledge
Docs
Power BI to Qlik migration
Assess Power BI and Fabric source evidence, save a durable handoff pack and rebuild the approved scope in Qlik.
On this page
Confirm the source evidence and access
The PBI Migration module gathers Power BI and Fabric metadata and produces a reviewable migration plan. The Qlik build is a separate step using the appropriate Raptor Qlik tools. Expect to review measures, data modelling, security and user workflows during the rebuild; visual and expression parity requires validation.
Migration capabilities are included with Builders under the current Portal catalogue, subject to the Gateway's enabled capabilities and access rules. Microsoft identity, tenant settings, workspace membership, item permissions and sensitivity controls determine which source evidence it can read. For unattended use, administrators configure a dedicated Entra service principal and grant it access to each approved workspace. Tenant-admin visibility alone does not provide that workspace access.
- Prefer Fabric item definitions or exported PBIP, PBIR and TMDL project content where available.
- Supported evidence includes report pages, visuals, bookmarks and themes, plus model tables, measures, relationships, partitions and security roles where Microsoft permits access.
- PBIX-only extraction is best effort. Prepare project-format or API evidence when the file alone is insufficient.
- Source totals can be checked with DAX queries where the Microsoft tenant and identity allow query execution.
Save the handoff before building
Generate the migration handoff pack and store it in the customer's approved project repository. It should be sufficient for the team to continue the rebuild and investigate later differences without depending on the original assessment session.
- powerbi-migration-manifest.json: structured source inventory, target plan and validation backlog.
- powerbi-source-inventory.md: source workspaces, reports, models, fields, measures and connections.
- qlik-build-handoff.md: instructions and agreed scope for the Qlik build.
- validation-pack.md: row-count, measure and visual comparison checks.
- open-decisions.md: unsupported items, security questions and design decisions requiring review.
Rebuild and verify business meaning
Use approved Qlik connections to the original governed data sources where practical. Rebuild the model, expressions and sheets against the reviewed handoff. Custom visuals, DAX behavior, Power Query transformations, RLS and source-specific features may need redesign. Keep unresolved items visible rather than treating generated recommendations as completed work.
Accept the target on checked business totals, representative filters, reload results, security behavior and business-owner review. Record expected layout and interaction differences. Keep source credentials, Gateway secrets and database passwords out of the manifest and workpapers.
Related SQL reporting migrations
For SSRS or other T-SQL reporting logic, licensed Raptor guidance can help plan a direct parity conversion or a Qlik model redesign. This is an assisted script-development workflow, with review of source queries, parameters, transformations and target reload evidence. It does not imply an SSRS server inventory or automatic migration of report layouts and subscriptions.
Previous
QlikView migration
Next