Qlik Sense → Power BI Migration

The Qlik Sense source platform is either a proprietary binary or lives on a server. The extract step connects to the Qlik Sense Engine (local Desktop or Qlik Server), exports each app's structure as a portable .navis-qlik file, and saves the underlying data to your working folder. The analyze and convert steps then run entirely offline — no engine, no server, no network required.

Configure the Qlik Engine WebSocket URL in [extract]:

[extract]
engine_url = "ws://localhost:4848/app/engineData"
app        = "C:/Apps/YourApp.qvf"

navis-extract spec.toml

It reads your source folder, saves the exported definitions and data to your working folder, and produces a working.sig integrity manifest that the analyze and convert steps verify to detect tampering.

Scan .navis-qlik artifacts (produced by the extract step) to assess what can be automatically migrated before committing to a conversion.

navis analyze spec.toml                  # Analyze all workbooks
navis analyze spec.toml --summary-only     # High-level numbers only
navis analyze spec.toml --no-recursion     # Top-level folder only

Submit the License Request PDF to navis@cepheusonline.com. The PDF embeds cryptographic fingerprints of your workbooks. Cepheus replies with a license file.

1. Run navis analyze and save the License Request PDF
2. Email the PDF to navis@cepheusonline.com
3. Receive a license file back

[convert]
license = "cepheus-license.pdf"

navis verify-license spec.toml

navis convert spec.toml

What Navis produces

For each workbook: a .pbip folder (Power BI Project), plus a _CEC.zip Evidence Capsule.

How calculations are converted

Navis translates Qlik Sense expressions to their Power BI equivalents using a formal atom-by-atom mapping that has been tested against actual Qlik Sense output. If an expression cannot be converted with verified accuracy, Navis flags it in the Evidence Capsule rather than guessing.

Windows only. The converter produces a .pbip project with the correct semantic model and DAX measures, but the M queries point to placeholder data sources. The deploy step writes the source data as CSV files alongside the project and repoints the M queries at those CSVs — so you can open the project in Power BI Desktop and see live data immediately.

Connects to the Qlik Engine (using [extract].engine_url and [extract].app) and exports each data-model table to CSV.

[deploy]
# No extra [deploy] keys required — reads [extract].engine_url / [extract].app automatically

navis-deploy spec.toml

After the deploy step, open the .pbip file in Power BI Desktop — all visuals will populate with data. Review the conversion, check the Evidence Capsule PDF for any fidelity gaps, and hand off to your data team.

Navigate to the _wired folder for any converted workbook and open the .pbip file in Power BI Desktop (File → Open report). Your report pages load with data immediately.

Connecting to production data

In Power BI Desktop: Home → Transform data → Data source settings. Select the CSV source and click Change Source. The semantic model and all measures are already correct — no other changes needed.

Review the PDF report inside the Evidence Capsule for anything flagged:

• Data connections — connect to your production data source after import.
• Unmapped expressions — set expressions or aggr() patterns without a proven equivalent; clearly marked.
• Qlik extensions and custom objects — not converted.
• Bookmarks and alternate states — not transferred.
• Variables used as dynamic expression bodies — flagged for manual review.
• Nothing is ever silently skipped. If Navis can’t convert something, it tells you.

Power BI Project folder

SalesDashboard/
  SalesDashboard.pbip              <-- open this in Power BI Desktop
  SalesDashboard.Report/
    definition.pbir
    report.json
  SalesDashboard.SemanticModel/
    definition.pbism
    definition/
      model.tmdl
      database.tmdl
      tables/
  _CEC.zip                         <-- Evidence Capsule

Open SalesDashboard.pbip in Power BI Desktop. The semantic model and all DAX measures are fully defined — you only need to point the data source at your production data.

The _CEC.zip Evidence Capsule contains the PDF audit report with formula-level conversion evidence, SHA-256 checksums, and any fidelity gaps.

Every conversion produces a _CEC.zip alongside the converted output. It contains:

• A signed PDF with formula-level translation evidence
• SHA-256 checksums of all input files
• A machine-readable JSON manifest of all conversions and fidelity gaps
• A timestamp and license reference

The capsule is tamper-evident: any modification to the converted output invalidates the checksums in the PDF. Keep _CEC.zip alongside your converted project as your audit record.

The Evidence Capsule PDF is cryptographically signed by Cepheus. The signature certifies:

• The workbooks that were analyzed match the license issued
• The conversion was performed by an authentic, unmodified Navis binary
• The formula translations are the ones Cepheus has validated

Signature verification does not require internet access. The public key is embedded in the license file.

Every command writes a structured log alongside the output. Log entries include:

• Per-workbook conversion decisions and fidelity gaps
• SHA-256 of each input file at conversion time
• Formula translation records (source expression → target expression)
• Any warnings or skipped elements

Logs are in JSON Lines format for easy ingestion into SIEM or audit tooling.

License errors

Common issues

For other issues: navis@cepheusonline.com

To analyze or convert a specific subset of workbooks, name the batch in your spec file and list the files you want:

[pipeline]
input = "my_batch"
working  = "C:/Working"
output   = "C:/Output"

[pathlists.my_batch]
base  = "C:/Workbooks"
files = [
    "Sales.twbx",
    "Finance.twbx",
    "subfolder/HR.twbx",
]

Each path in files is resolved relative to base. Use a named batch when you want to hand-pick specific files rather than converting an entire folder.