Migration guides

Migrations are necessary when upgrades to Strapi include breaking changes. The migration guides are sequential, meaning if there is more than 1 migration guide between your current version and the latest release, follow each guide in order. If there is no specific migration guide between your current version and the latest release follow the Update Strapi guide.

✋ CAUTION

Plugins extension that create custom code or modify existing code will need to be updated and compared to the changes in the repository. Not updating the plugin extensions could break the application.

v4 migration guides

• Migration guide from 4.0.0+ to 4.0.6
• Migration guide from 4.0.6+ to 4.1.8
• Migration guide from 4.1.8+ to 4.1.10

v3 to v4 migration guides

🚧 Migration guides

This section is still a work in progress and will continue to be updated and improved. In the meantime, feel free to ask for help on the forum (opens new window) or on the community Discord (opens new window).

Migrating from v3.6.x to v4.0.x revolves around 3 topics:

• The code migration guide helps migrating the built-in back-end and front-end code of the Strapi application to v4.
• The data migration guide helps migrating the database content to v4.
• The plugin migration guide helps migrating a plugin to v4.

v3 migration guides

v3 migration guides are available in the v3 documentation (opens new window).