LimeSurvey 7 Migration Series — Part 1: Why you should NOT (yet) update to LimeSurvey 7
Over the last weeks, we have received an increasing number of support requests from users who accidentally updated their systems to the still unstable LimeSurvey 7 release. For this reason, we want to briefly summarize the current state of LimeSurvey 7 and explain why updating production systems is currently not recommended.
Current risks and migration considerations:
- LimeSurvey 7 is currently still in Beta/RC status and not yet considered production-ready
Production environments may experience unexpected issues, incomplete features or compatibility problems.
- Existing plugins may stop working
Many custom plugins rely on internal APIs, database structures or fieldnames that have changed in LimeSurvey 7.
- Custom themes can break after the update
Older Twig templates, CSS customizations and Bootstrap-related changes may cause broken layouts or rendering issues.
- Existing survey links may no longer work as expected
Changes to URL handling can affect already distributed participant links and integrations.
- Custom exports and database queries may fail
The response table and fieldname refactor can break external reporting systems, integrations and SQL-based workflows.
The latest recommendations, release information and migration considerations will be
continuously updated on our website
.
We plan to continuously expand this guide over the next weeks.Upcoming sections include:
- What’s new in LimeSurvey 7
- Plugin & Theme Compatibility in LimeSurvey 7
- LimeSurvey 7 Migration Checklist
- How to safely update business-critical LimeSurvey systems to Version 7
- FAQ and troubleshooting examples
We would also be interested in hearing about migration experiences, compatibility issues or upgrade problems other users are already seeing with LimeSurvey 7.
