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.
<!-- Answer --> Superset does not automatically map or reconcile user IDs during import, even with Google OAuth. The user who performs the import (via CLI or UI) is added as an owner to dashboards, charts, and datasets if not already present. If you need historical or accurate ownership, you’ll have to manually reassign owners after import—there’s no built-in way to map users by email or OAuth identity during migration. For saved queries, owner fields are not tracked on import, so no user mapping occurs at all [[source]](https://github.com/apache/superset/blob/308007f909b5a3c1cdd6fc5632ef27ca7eb97ce0/superset/commands/dashboard/importers/v1/utils.py). For large imports, the web UI and API enforce a 100 MB ZIP file size limit and a 200:1 compression ratio. If you hit "Payload too large" errors, use the CLI tools (`superset import_dashboards`, `superset import_datasources`, etc.), which bypass these limits and can handle much larger files as long as your system resources allow. There’s no chunked upload support, so CLI is the best option for big migrations [[source]](https://github.com/apache/superset/blob/308007f909b5a3c1cdd6fc5632ef27ca7eb97ce0/superset/config.py). Superset 4.1.2 requires ZIP files for import. The CLI provides commands to export/import dashboards and datasources as ZIPs. Legacy CLI commands exist for importing/exporting YAML and JSON from older versions, but there’s no built-in tool to convert YAML exports from 1.1.0 to the ZIP format required by 4.1.2. The recommended approach is to use the legacy CLI importer for YAML, or re-export your assets using the CLI in a newer Superset version that supports ZIP export, then import those ZIPs into 4.1.2 [[source]](https://github.com/apache/superset/blob/308007f909b5a3c1cdd6fc5632ef27ca7eb97ce0/superset/cli/importexport.py) [[source]](https://github.com/apache/superset/blob/308007f909b5a3c1cdd6fc5632ef27ca7eb97ce0/docs/docs/configuration/importing-exporting-datasources.mdx). There isn’t a single official migration guide for this upgrade path, but CLI command help and error messages are the main documentation for required formats and migration steps. For smoother migration, pre-create users in the new instance (with matching usernames/emails), use an admin account for imports, and plan for manual ownership adjustments after import. <!-- 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/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0923080a-a747-45ef-8d03-76632cc6bdfb?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](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-13637949 ---- 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]
