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:

1. 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.
2. Existing plugins may stop working
   Many custom plugins rely on internal APIs, database structures or fieldnames that have changed in LimeSurvey 7.
3. Custom themes can break after the update
   Older Twig templates, CSS customizations and Bootstrap-related changes may cause broken layouts or rendering issues.
4. Existing survey links may no longer work as expected
   Changes to URL handling can affect already distributed participant links and integrations.
5. 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.

Your webpage about that topic is currently broken.


 

Thanks a lot for the hint, @jelo. We were working on the page draft and now the page was published.
 

LimeSurvey 7 Migration Series - Part 2: What’s new in LimeSurvey 7LimeSurvey 7 has now been released as a first official version. We take this as an opportunity to summarize some of the most important changes and new features introduced with LimeSurvey 7.While our first post focused on migration risks and reasons to be careful with production updates, this second part highlights what is actually new in LimeSurvey 7.Important changes and new features:

1. New React-based survey editor
   LimeSurvey 7 introduces a new React-based survey editor. This modernizes the survey editing experience and is one of the most visible changes in the new version.
2. Better response saving for larger surveys
   The handling of response saving has been improved, especially for larger and more complex surveys. This should help with more demanding survey setups.
3. Randomization improvements
   LimeSurvey 7 improves randomization handling, including better support for fixed subquestion and answer positions in randomized question structures.
4. Response table and fieldname refactor
   Internal changes to response tables and fieldnames have been introduced. These changes are especially relevant for custom exports, external reporting tools, integrations and direct SQL-based workflows.
5. Design unification
   The administration interface and participant-facing survey views have been further aligned. This creates a more consistent visual experience across the system.
6. PHP 8.1.29 minimum requirement
   LimeSurvey 7 requires PHP 8.1.29 or newer. Before planning an update, server environments should therefore be checked carefully. The current LimeSurvey download page also lists PHP 8.1.29 or newer as a requirement for version 7.0.0.

These changes are important steps forward, but they also mean that existing installations should be reviewed before upgrading. This is especially important for systems using custom plugins, custom themes, complex survey logic, external integrations or direct database queries.The latest recommendations, release information and migration considerations will be continuously updated on our website.We plan to continue this series with the following sections:

• 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 seeing with LimeSurvey 7.

Mazi wrote:

LimeSurvey 7 Migration Series - Part 2: What’s new in LimeSurvey 7
LimeSurvey 7 has now been released as a first official version. We take this as an opportunity to summarize some of the most important changes and new features introduced with LimeSurvey 7.While our first post focused on migration risks and reasons to be careful with production updates, this second part highlights what is actually new in LimeSurvey 7.Important changes and new features:

Hi there, a little confused by this post. Is this in reference only to your services as a partner?

The official LimeSurvey blog, news section of this forum,  limesurvey.net (by the GmbH)  and CE releases on GitHub are still featuring LimeSurvey 6.
The linked page on your website still gives a  warning not to update  and you posted it on 29th May, same time as this post?

Anyway, I would be interested in learning more about this:

Randomization improvements
LimeSurvey 7 improves randomization handling, including better support for fixed subquestion and answer positions. This is especially relevant for surveys with complex question structures.

Hi there,

please note that our posts are no official statements by the LimeSurvey GmbH, that is a different company.
Our comments are based on our daily work with LimeSurvey. We are dealing with ~250-300 LimeSurvey projects every year. Based on that we try helping users with our experience.

Regarding your question: The new LimeSurvey 7 version (and I think also the latest 6.17.x version) comes with a new feature to keep certain subquestions/answer options at original positions on randomization. This is often useful when having certain items like "None of these" or "I do not want to answer this".

Actually you are right, it has released on the community site back on 26 May ...
but the communication about it has been odd.

But not tagged on GitHub , announced in this forum's news section (the RC was), or the official blog .

The closest to confirmation I could find was a git commit . So I wonder if, despite the "7.0.0" marker, this is not actually intended for production use yet by the developers?

So I wonder if, despite the "7.0.0" marker, this is not actually intended for production use yet by the developers?

As it doesn't have any "alpha", "beta" or "RC" added to the version, I assume that the Limesurvey GmbH deems LS 7.0.0 ready for production.

However, based on previous releases, I would install LS 7.0.0 for tests, but not yet move my production environment to LS 7. Experience shows that there are often still some "hickups" during the first weeks/months.

I didn't have much time lately to look into LS 7.x so I can't really tell about who stable or production ready it really is.

LimeSurvey 7 Migration Series — Part 3: LimeSurvey 7 Plugin & Theme Compatibility

Planning to update a customized LimeSurvey installation to version 7? Then plugin and theme compatibility should be one of the first things to check – especially if you are migrating directly from an older LimeSurvey 3.x or 5.x installation.
LimeSurvey 7 introduces several internal changes that can affect custom setups in different ways.

Custom themes
Updates from LimeSurvey 6.x to 7.x should generally be relatively straightforward regarding themes. However, when upgrading from LimeSurvey 3.x or 5.x, existing custom themes are not compatible with the technologies used in LimeSurvey 7 and usually need to be rebuilt or migrated accordingly.
If you rely on a customized survey design, we strongly recommend reviewing the theme before performing the update. We are happy to  help with theme migration  and redevelopment where required.
Themes downloaded from our  online shop  will be available for LimeSurvey 7 starting in July 2026.

Custom plugins
Custom plugins should also be reviewed before upgrading. In particular, plugins that directly access the response table or participant table may require significant adjustments due to structural changes introduced in LimeSurvey 7.
Plugins that do not rely on these tables are generally less likely to be affected, but compatibility testing is still recommended.
The plugins available for download at our online shop will be updated for LimeSurvey 7 in July 2026 step by step (check the plugin’s change log for details).Survey links
LimeSurvey 7’s React-based question editor requires the path URL format. Systems still using the older get URL format should carefully evaluate the impact of switching, as existing survey links, invitations, embedded surveys, or external integrations may be affected.Custom exports and database integrations
Organizations using custom exports, reporting scripts, or direct database queries should verify their functionality after migration. Changes to response tables and field names can require adjustments to existing workflows.

PHP compatibility
LimeSurvey 7 requires a modern PHP 8.1 environment. Existing plugins, custom code or server setups may need adjustments before the update.

Large PostgreSQL installations
There is a reported issue affecting some large PostgreSQL-based LimeSurvey installations during updates from LimeSurvey 6 to 7. Systems with several thousand questionnaires should therefore be tested carefully in a staging environment before updating production systems.

Need help with your LimeSurvey 7 migration?
As this article shows, there are quite a few potential pitfalls when upgrading to LimeSurvey 7. Depending on your setup, custom themes, plugins, survey links, database integrations, or server configuration may require adjustments before the update can be completed successfully.
With many years of experience in LimeSurvey migrations, custom development, and enterprise installations, we know where upgrade projects typically run into problems. Before risking unexpected downtime or compatibility issues, contact us for a free pre-check of your LimeSurvey installation. We will review your setup and help you identify potential risks before the migration starts.

Could you share more details about "Response table and fieldname refactor"?
We actually query the database directly
Thanks

franz007 wrote:

Could you share more details about "Response table and fieldname refactor"?
 

Perhaps you can find a few interesting things in the manual.
www.limesurvey.org/manual/LimeSurvey_7_Fieldname_Refactor
 

franz007 wrote:

Could you share more details about "Response table and fieldname refactor"?
We actually query the database directly
Thanks

We also have also created a list with additional information and links at  survey-consulting.com/limesurvey-7-migra..._Further_Information

Hello,I am finding it quite difficult to determine if the latest update is ready for production.There seems to be a mismatch in information: the download page lists the release as "stable," yet multiple threads here on the forum advise against using it in a production environment.Could anyone clarify why there is such a gap between the official status and the community feedback? Any insights would be greatly appreciated.

Hallo Frosch,
our feedback is based on 15 years of experience with new LimeSurvey releases and 250-300 LimeSurvey projects we deal with every year.
Based on that experience I have to say that the first release are never fully bug free. Furthermore, there are quite a few open bug tickets at the LimeSurvey bugtracker which also indicates that some additional work needs to be done.
My recommendation it to wait another 2-4 months before using version 7.x for production.

Beste Grüße
Marcel

Same here: The definition of what is considered "stable" and "ready for production" can be different for different people.

Same as Mazi, based on experience over the last couple of major releases, I would hold back a couple of months to use LS 7.x in production environments that are really critical.

In theory all major bugs should be gone in LS 7.x, but ...