LimeSurvey 7 Features & Migration

This page contains the latest information, migration risks, compatibility notes and technical updates related to LimeSurvey 7. We continuously update and expand this guide as new releases, issues and migration experiences become available.

Why you should NOT (yet) update to LimeSurvey 7

LimeSurvey 7 introduces major architectural and technical changes. In this section we summarize the current status, known risks and important migration considerations.

  1. LimeSurvey 7 was just released
    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.
  6. NEW: SQL problem when updating large Postgres datbases
    A user reported a failed update with a very large Postgres LimeSurvey database, see bug report.

While the new version brings many improvements, we currently do not recommend updating production systems yet.

Need help with your LimeSurvey 7 migration or already experiencing upgrade problems? Contact us for professional support.

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 the most important changes, new features and technical updates introduced with LimeSurvey 7.

LimeSurvey 7 is more than just a regular update. It introduces several architectural, technical and usability-related changes that can affect existing installations, plugins, themes and workflows.

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.

Better response saving for larger surveys
The handling of response saving has been improved, especially for larger and more complex surveys. This can help make data collection more reliable in demanding survey setups.

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.

Response table and fieldname refactor
Internal changes to response tables and fieldnames have been introduced. These changes can affect custom exports, external integrations, reporting systems and direct SQL-based workflows.

Design unification
The design of the administration interface and the participant-facing survey view has been further aligned. This creates a more consistent visual experience across the system.

PHP 8.1.29 minimum requirement
LimeSurvey 7 requires at least PHP 8.1.29. Server environments may therefore need to be checked and updated before planning a migration.

While LimeSurvey 7 introduces many important improvements, existing installations should still be reviewed carefully before upgrading. This is especially important if you use custom plugins, custom themes, complex survey logic, external integrations or direct database queries.

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.

LimeSurvey 7 migration checklist

This checklist is intended for all users upgrading from LimeSurvey 6 to the new LimeSurvey 7 release.
For larger installations, we strongly recommend creating a staging environment based on a copy of the current production database and files. This allows you to validate the migration process before updating your live system.

System Requirements and Backup
Before starting the upgrade, verify that your server meets the new system requirements. LimeSurvey 7 requires PHP 8.1 or newer, while PHP 8.3 and PHP 8.4 are currently recommended for new installations.
Before performing any update, create a complete backup of your database as well as all application files. This ensures that the existing installation can be restored if necessary.

Custom LimeSurvey Themes
If your installation uses custom themes, review all modifications before the migration. Particular attention should be paid to custom JavaScript code and CSS adjustments. These components should be thoroughly tested after the upgrade to ensure that the survey appearance and functionality remain unchanged.

LimeSurvey Plugins
Review all custom-developed plugins currently used in your installation. Ideally, these plugins should be tested on a LimeSurvey 7 test system before updating the production environment.
Plugins that directly access response tables may require adjustments, as the underlying data structures have changed in LimeSurvey 7.

Update to LimeSurvey v7.x
For larger environments, perform the migration on a staging system first. A successful test migration helps identify potential compatibility issues before updating the production environment.
After validating the test installation, the production system can be upgraded using the standard update procedure.

Post-Migration Check
After the upgrade, verify that surveys, themes, plugins and custom integrations continue to work as expected. Particular attention should be given to customized components and any external systems connected to LimeSurvey.

Updating from Older LimeSurvey Versions
When upgrading from older LimeSurvey versions, custom plugins should be reviewed with particular care, as compatibility issues are more likely to occur.
In addition, LimeSurvey 6 and 7 use a modern template technology that differs from older releases. Custom survey themes created for previous versions may need to be rebuilt once using the new theme framework before they can be used with LimeSurvey 7.

Free LimeSurvey 7 Migration Check
Not sure whether your installation is ready for LimeSurvey 7? We offer a free migration check to review your current environment, custom themes, and plugins.
Contact our team for professional LimeSurvey support.

How to safely upgrade your LimeSurvey production system to version 7

Updating a production LimeSurvey system requires more than simply installing the latest release. If your installation includes custom themes, plugins, active surveys or external integrations, careful preparation helps minimize downtime and unexpected issues.
The following six steps provide a practical approach for upgrading to LimeSurvey 7 while reducing the risk for your production environment. If you have not already done so, we also recommend reviewing our LimeSurvey 7 Migration Checklist before starting your update.

1. Create a database backup and define a rollback strategy
Before making any changes, create a complete backup of your LimeSurvey database and application files. Verify that the backup can actually be restored if necessary.
For production environments, it is equally important to define a rollback strategy before starting the update. If unexpected problems occur, you should know exactly how to return to the previous version without unnecessary downtime.

2. (Optional) Set up a staging environment
For larger or more complex installations, we strongly recommend testing the upgrade in a staging environment first. A staging system should be based on a copy of your production database and application files to simulate the real environment as closely as possible.
Smaller installations may choose to update directly, but a staging environment significantly reduces the risk of unexpected compatibility or configuration issues.

3. Validate your complete installation
If you are using a staging or test environment, validate the complete installation before updating your production system.
Besides verifying that LimeSurvey itself works correctly, test all components that are important for your installation. This includes custom plugins, survey themes, external authentication, reporting tools, API integrations, scheduled tasks and any custom developments. A successful software update alone does not guarantee that the complete system will continue to operate as expected.
For a more detailed overview of components that should be reviewed before upgrading, see our LimeSurvey 7 Plugin & Theme Compatibility guide.

4. Review URL compatibility for active surveys
Before updating to LimeSurvey 7, review how your survey URLs are generated. Older installations often use the legacy get URL format, while the new React-based survey editor requires the path URL format.
For example:

  • Old URL format: https://example.com/limesurvey/index.php?r=survey/index&sid=123456
  • New URL format: https://example.com/limesurvey/123456

If you switch from the old URL format to the new one, existing participant links, embedded surveys or external integrations may no longer work as expected. If active surveys are already running, verify that previously distributed links remain accessible or configure appropriate redirects before performing the upgrade.
For further details about the new URL handling, see the official LimeSurvey documentation.

5. Review the allowed_hosts.php configuration
Newer LimeSurvey versions automatically create the application/config/allowed_hosts.php configuration file during the update process. This file protects the administration interface by defining which hostnames are allowed to access the backend.
After the upgrade, verify that all hostnames used to access your LimeSurvey installation are listed in this file. This is particularly important if your system is reachable through multiple domains, aliases or internal hostnames. Missing entries can prevent administrators from accessing the backend, even though the upgrade itself completed successfully.

6. Perform the production update and verify the installation
Once all preparations have been completed successfully, perform the production update during a planned maintenance window.
After the upgrade, verify the most important functions of your installation. Check administrator access, active surveys, email delivery, plugins, themes and external integrations. Reviewing the application logs after the update can also help identify issues before users report them.
If you skipped the optional staging environment, this verification becomes even more important, as it is your first opportunity to identify issues in the production system.

Planning your upgrade to LimeSurvey 7?
We help organizations safely upgrade to LimeSurvey 7—from the initial assessment to a successful production rollout. Contact us to discuss your migration project.

LimeSurvey 7 Resources & Further Information

The following resources provide additional information about LimeSurvey 7 releases, compatibility, migration considerations and technical changes.