GitHub user dosubot[bot] added a comment to the discussion: Exporting 
Dashboards & Saved Queries from Superset Version 1.1.0 is not working when 
importing it into version 4.1.2.

<!-- Greeting -->
Hi @YaqoobAlam! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the 
superset team.

<!-- Answer -->
The import fails because Superset 4.1.2 requires all dependencies—databases, 
datasets, charts, and queries—to be present in the import bundle. If any 
referenced database or dataset is missing, you'll see errors like "Database not 
found" and the import will not proceed. This is a strict architectural 
requirement in recent Superset versions and there is no built-in fallback or 
remapping for missing resources 
[[source]](https://github.com/apache/superset/issues/31443).

To migrate dashboards and saved queries from 1.1.0 to 4.1.2, you need to:

1. Export not just dashboards and queries, but also all related databases, 
datasets, and charts from 1.1.0. The export must include everything referenced 
by your dashboards and queries.
2. If your export is missing any of these, manually export them from the old 
instance and add them to your bundle.
3. Before importing, check that the UUIDs for databases and datasets in your 
export match what the dashboards and queries reference. If not, you may need to 
edit the export files to align them.
4. Import the full bundle into 4.1.2. If you still get "Database not found," 
double-check that every referenced database is included and that its UUID 
matches.
5. After import, you may need to open and save each chart in the UI to 
regenerate query contexts, as these are not always populated during import 
[[source]](https://github.com/apache/superset/issues/33615).

There is no official migration guide for this upgrade path, and the 
import/export format has changed significantly since 1.1.0. If you have saved 
queries, note that recent versions require a `catalog` field in the import 
schema [[source]](https://github.com/apache/superset/pull/32775).

If you use tags, be aware that tag handling is now controlled by the 
`TAGGING_SYSTEM` feature flag and may affect your migration 
[[source]](https://github.com/apache/superset/pull/30833).

If you encounter errors related to empty `template_params`, a recent fix in 4.x 
sets these to null, which may resolve some import failures 
[[source]](https://github.com/apache/superset/pull/33547).

In summary: always export/import the full set of dependencies, ensure UUIDs 
match, and be prepared for some manual post-import fixes. There is no built-in 
tool to automate this process across such a large version gap.


<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*

---
<sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/d78a787b-e6e9-4f41-b33d-a2da2b2ba5b7?feedback_type=other)</sup>&nbsp;&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Sh
 are on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34022)

GitHub link: 
https://github.com/apache/superset/discussions/34022#discussioncomment-13637475

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to