GitHub user Hassan6945 added a comment to the discussion: apache super set db migration issue
@dose I also have database backups from versions *6.0.0* and *5.0.0*. However, when I try to import these backups into a fresh *6.0.0* or even *5.0.0* installation, I run into an *Alembic version mismatch* issue. If I share the exact *migration ID* with you, would you be able to help me run the exact *5.0.0 release*? That would allow me to import the database from *5.0.0* into a fresh *5.0.0* setup, which would be the simplest solution for me. Otherwise, the only workaround I see is to create a separate connection, export all datasource database files, manually modify them, and then import them into a fresh *5.0.0* instance. This process is quite hectic and time-consuming. In short, all my data has been migrated to *0.0.0-dev*, and I want it to be on *5.0.0*, which should be migratable without Alembic issues. However, even an older *5.0.0* database backup results in the same problem when imported into a fresh *5.0.0*, though with a different Alembic ID. On Mon, Jan 19, 2026 at 12:16 PM dosubot[bot] ***@***.***> wrote: > The "Unknown field: datetime_format" errors happen because your exported > metadata includes a field that the target Superset version's import schema > doesn't recognize—likely due to version differences. Superset's importers > strictly validate fields and will block the import if any unknown fields > are present; there is no built-in way to ignore or map them automatically > (source) > <https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/datasets/schemas.py#L44-L174> > . > > To fix this, you need to manually clean your export bundle: > > 1. Unzip the exported dashboards/datasources ZIP file. > 2. Search all YAML files for datetime_format and remove those lines > (or, if needed, rename to python_date_format if that's what your > target version expects). > 3. Save the files and re-zip the bundle. > 4. Retry the import. > > For the password errors: Superset never exports database passwords for > security reasons. After import, you must manually edit each database > connection in the new environment and re-enter the password (source) > <https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/importers/v1/utils.py#L151-L197> > . > > If you hit similar "Unknown field" errors for other fields (like theme_id), > the same manual cleanup applies. For large migrations, always check that > all referenced databases, datasets, and charts are included in your export, > and that their UUIDs match what dashboards and queries expect (source) > <https://github.com/apache/superset/discussions/34022>. > > If possible, try to match your Superset source and target versions as > closely as you can to minimize schema mismatches. If you have a lot of > these errors, consider upgrading your target Superset to a newer version > that may have better compatibility with your export (source) > <https://github.com/apache/superset/issues/35177>. > > Let me know if you need a step-by-step for the manual cleanup or run into > other import errors! > > *To reply, just mention @dosu <https://go.dosu.dev/dosubot>.* > ------------------------------ > > How did I do? Good > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=great_response> > | Irrelevant > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=irrelevant_answer> > | Incorrect > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=incorrect_sources> > | Verbose > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=too_verbose> > | Hallucination > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=hallucination> > | Report 🐛 > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=bug_report> > | Other > <https://app.dosu.dev/response-feedback/cc6cbe8a-ae53-4808-954c-ff9bae51fba6?feedback_type=other> > > [image: Chat with Dosu] > <https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github> > [image: Open in Cursor] > <https://cursor.com/link/prompt?text=The%20%22Unknown%20field%3A%20datetime_format%22%20errors%20happen%20because%20your%20exported%20metadata%20includes%20a%20field%20that%20the%20target%20Superset%20version%27s%20import%20schema%20doesn%27t%20recognize%E2%80%94likely%20due%20to%20version%20differences.%20Superset%27s%20importers%20strictly%20validate%20fields%20and%20will%20block%20the%20import%20if%20any%20unknown%20fields%20are%20present%3B%20there%20is%20no%20built-in%20way%20to%20ignore%20or%20map%20them%20automatically%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/datasets/schemas.py%23L44-L174%29.%0A%0ATo%20fix%20this%2C%20you%20need%20to%20manually%20clean%20your%20export%20bundle%3A%0A%0A1.%20Unzip%20the%20exported%20dashboards/datasources%20ZIP%20file.%0A2.%20Search%20all%20YAML%20files%20for%20%60datetime_format%60%20and%20remove%20those%20lines%20%28or%2C%20if%20needed%2C%20rename%20to%20%60python_dat e_format%60%20if%20that%27s%20what%20your%20target%20version%20expects%29.%0A3.%20Save%20the%20files%20and%20re-zip%20the%20bundle.%0A4.%20Retry%20the%20import.%0A%0AFor%20the%20password%20errors%3A%20Superset%20never%20exports%20database%20passwords%20for%20security%20reasons.%20After%20import%2C%20you%20must%20manually%20edit%20each%20database%20connection%20in%20the%20new%20environment%20and%20re-enter%20the%20password%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/commands/importers/v1/utils.py%23L151-L197%29.%0A%0AIf%20you%20hit%20similar%20%22Unknown%20field%22%20errors%20for%20other%20fields%20%28like%20%60theme_id%60%29%2C%20the%20same%20manual%20cleanup%20applies.%20For%20large%20migrations%2C%20always%20check%20that%20all%20referenced%20databases%2C%20datasets%2C%20and%20charts%20are%20included%20in%20your%20export%2C%20and%20that%20their%20UUIDs%20match%20what%20dashboards%20and%20queries%20expect%20%5B%2 8source%29%5D%28https%3A//github.com/apache/superset/discussions/34022%29.%0A%0AIf%20possible%2C%20try%20to%20match%20your%20Superset%20source%20and%20target%20versions%20as%20closely%20as%20you%20can%20to%20minimize%20schema%20mismatches.%20If%20you%20have%20a%20lot%20of%20these%20errors%2C%20consider%20upgrading%20your%20target%20Superset%20to%20a%20newer%20version%20that%20may%20have%20better%20compatibility%20with%20your%20export%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/35177%29.%0A%0ALet%20me%20know%20if%20you%20need%20a%20step-by-step%20for%20the%20manual%20cleanup%20or%20run%20into%20other%20import%20errors%21> > [image: Join Discord] <https://go.dosu.dev/discord-bot> [image: Share on > X] > <https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/37232> > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/superset/discussions/37232#discussioncomment-15535716>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUUYY67BHLLTMQX7F6YJKMD4HSADXAVCNFSM6AAAAACSC7CE6SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNJTGU3TCNQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > GitHub link: https://github.com/apache/superset/discussions/37232#discussioncomment-15537452 ---- 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]
