Move from Lightdash

Keep your dbt-backed definitions as the starting point while bringing Lightdash charts and dashboards into Querio.

Already exported? Go straight to Move exported work to Querio.

1. Prepare access

Install unshackle and run the commands below from your analytics Git repository.

• LIGHTDASH_URL, LIGHTDASH_API_KEY and LIGHTDASH_PROJECT. The project UUID appears in /projects/PROJECT_ID/ in the browser address.
• Create a personal access token in Settings > Personal access tokens. It sees only the spaces and projects its user can access.
• Set LIGHTDASH_DBT_PROJECT_DIR to your dbt checkout if you also want its schema YAML in the export.

2. Export one report

unshackle check lightdash --prompt
unshackle inventory lightdash
unshackle migrate lightdash --only DASHBOARD_ID
unshackle todo

Replace DASHBOARD_ID with the selected item's ID from inventory. The credential prompt saves values to a local, git-ignored .env; keep those values out of agent prompts.

Read migration/report.md for missing dependencies, extraction errors and unfinished translations before continuing.

Using exported files instead

Without API access, import the dbt project that defines your Lightdash metrics. Include lightdash download output when you have exported charts and dashboards:

unshackle init
unshackle import lightdash path/to/dbt-project
unshackle build lightdash
unshackle todo

A dbt project alone does not contain saved chart/dashboard exports. File imports also lack Lightdash-compiled chart SQL and usage; inspect the report for chart SQL that still needs writing.

3. Review what needs adapting

• Distinct aggregates, custom SQL metrics and table calculations may need SQL models or window functions.
• Review dashboard filters and relative dates rather than assuming they are bound to every chart.
• Retain your dbt definitions and avoid creating conflicting metric meanings in Querio context. Access-attribute groups need explicit mapping.

Download a source chart's results as CSV, or compare its Lightdash-compiled SQL under pinned dates and filters. Include joins or distinct metrics that could change the aggregation grain.

4. Rebuild and check it in Querio

Open the repository in Claude Code, Codex or your preferred coding agent. Give it this brief:

Read https://docs.querio.ai/llms/guides/move-bi-workflow/already-unshackled.md.
Use this repository's Lightdash export to rebuild REPORT_NAME in Querio.
Reuse the dbt-backed definitions. Pay attention to Lightdash metric
filters, distinct aggregates, compiled chart SQL and table calculations.
Ask me for the target workspace, datasource and a trusted source result.

Replace REPORT_NAME with the report you chose. Follow Move exported work to Querio for CLI authentication, the full agent task, verification and sharing. Check the rebuilt Querio output against your source result before using it as a replacement.

For export settings and the full list of translation gaps, see unshackle's Lightdash guide.