Database migration - V3.6.8 to V4.2.0
Kurtis Rogers
This seems pretty critical and I've seen a lot of noise regarding Database Migration but aside from being sent this link (https://github.com/strapi/migration-scripts/tree/main/v3-sql-v4-sql) for a project - which is beta (using mysql) - I'm unsure how to handle this? The devops chaps have mentioned we use Liquibase which should help us out. But it would be great if there was a "Strapi way" to do this too.
I've tried using the package above and tbf, it is very nearly working, complains about
core_store
even though it does seem to handle but strapi start
dies which isn't great. Environment:
Node v15.14.0
Strapi v4.2
MySQL v2.18.1
Its really irritating as I delayed an upgrade on this project earlier this year because the docs weren't quite there - and 3.6.8 was still regarded as stable/the way to go.
Is there something impending? I've spent a week upgrading a production V3.6.8 instance and we've deployed it (test env) - works great! Content is persisting but the admin users are not - they've been wiped.
Any help on this would be greatly appreciated!
Thanks,
Kurtis
Shaun Brown
Hi Kurtis, I am sorry no one replied to you earlier. Have you seen the documentation on database migration? https://docs.strapi.io/developer-docs/latest/update-migration-guides/migration-guides/v4/data/sql.html ?