- Create APIsDesign REST and GraphQL Content Delivery APIs to connect to any frontend.
- Content ManagementCraft experiences and easily manage editing, publishing, and translation.
- CustomizationPersonalize your CMS to meet your project's unique requirements.
- CollaborationWork together easily on code and content.
- HostingHost your projects on robust, secure servers in minutes.
- SecurityImplement robust security measures to protect your information.
- EcommerceLevel up your eCommerce experiences
- Mobile applicationsOne CMS, any devices.
- Corporate siteManage your brand narrative.
Looking for our logo ?
- Last updated: December 8, 2022 (Strapi v4 era)
- 3 min read
End of The Road for Strapi v3
It is the end of the road for Strapi v3, and we explain what it means to Strapi users and what you can do to migrate.
November 30, 2022
When we officially announced the release of Strapi v4 at the end of 2021, our initial plan was to keep supporting v3 and fixing critical bugs for at least six months. We later extended Strapi v3 support until December 31st, 2022 and did a handful of v3 releases (v3.6.10, and v3.6.11) since then to update dependencies and avoid security vulnerabilities.
In this post, we will provide some clarity on when Strapi v3 will reach the end of life (EOL) and give a summary of all the resources available to users who still have projects running on v3.
When will Strapi v3 reach end of life support, and what does that mean?
As mentioned above, we will continue to support v3 until December 31st, 2022. After that date, your Strapi project running on v3 will continue to work as expected; the only difference is that we will no longer be providing any kind of support to v3 users or issuing any new releases or security patches ourselves.
The Strapi v3 documentation will remain available as a resource to those who might need it.
How can the Strapi team help with the migration?
If you are a Strapi Enterprise Edition customer currently running on Strapi v3, please refer to this support article as a starting point. Customers with a valid Silver or Gold license can also use the support portal to contact our support team, who can answer specific migration questions you might have. If you are a Community Edition user, please refer to the migration resources available below and join the #v3-to-v4-migration channel on discord.
Does the Strapi team provide professional services related to migration?
We do not provide professional services to handle migration on behalf of our customers. Feel free to contact our official Solution partners listed in this directory to inquire about services related to Strapi migration.
What are the migration resources available?
If you’re a Strapi user still running on Strapi v3 and looking to migrate to v4, we invite you to take a look at this migration walkthrough as well as the links to our official guides covering the following migration topics:
- code migration for your back-end and front-end code
- data migration for your database content
- plugin migration for your plugins
Knowing that the migration from v3 to v4 is not trivial for users who have a lot of data or customization, our team started delivering scripts and tooling to help ease and automate the migration process, including:
- Codemods - a CLI to help you migrate your Strapi application
- Data Migration Scripts (used to help automate migrating your data)
Based on the feedback from awesome members of the Strapi community, we also created a dedicated Youtube playlist covering migration examples and FAQ.
Will Strapi v3 application be able to be deployed on Strapi Cloud?
No, only Strapi version 4.4.x or higher will be able to be deployed on Strapi Cloud.
Victor Coisne is VP Marketing at Strapi, the leading Open Source Headless CMS. As an open-source and developer community enthusiast, Victor has been working for Open Core B2B companies for more than a decade including 5+ years as Head of Community at Docker. In his free time, Victor enjoys spending time with friends, wine tasting, playing chess, tennis or soccer.