Support for LimeSurvey 6 on Cloud ends on 1 November 2026. Every LimeSurvey Cloud site moves to LimeSurvey 7, either when you start the upgrade yourself or automatically in the first week of November. This page answers the questions we get most often.
Log in as an administrator and click Upgrade to version 7 in the header of your survey site. You first see a dialogue that explains what happens next; confirm it to start the upgrade. The upgrade begins at the next full hour and takes 1 to 10 minutes. You receive an e-mail when it has finished; the version in the admin footer then reads 7.0.x.
No. LimeSurvey 7 is included in every plan. Your subscription, price and renewal date do not change.
Everything is carried over: surveys, responses, participants and access codes, quotas, conditions, e-mail templates and survey links. Active surveys stay active. You do not need to export or re-import anything.
Briefly. While the database is migrated (1 to 10 minutes) the site is in maintenance mode: respondents cannot open the survey, and someone in the middle of a page loses that page's answers. Pages already submitted are safe. You decide when the upgrade starts, so pick a moment when few people are filling in your surveys.
Yes. Create a free LimeSurvey account (it runs on version 7), export your survey (.lss) and your theme (.zip) from your current site, import both there and run through the survey once. Free-plan limits apply, so use a representative survey. If an import fails, send us the .lss file.
Your site is upgraded automatically during the first week of November. We recommend choosing your own moment before then.
You can pick your own moment until 1 November, but not beyond it, so every Cloud site moves to version 7. Corporate and Enterprise customers, and customers on a dedicated server: if you have concerns or cannot make 1 November, contact our support team and we schedule the upgrade with you at a time that suits you.
No. We take a snapshot of your site right before the upgrade, and if the upgrade fails our team restores it for you and will investigate the reason. Once the upgrade has completed, your site stays on version 7. Version 6 is no longer supported after 1 November, and restoring the snapshot would take your site back to the moment before the upgrade, so every response collected on LimeSurvey 7 since then would be lost. If you want to be sure everything works, test in a free account first (see above).
It is shown only to administrators of a site that is still on version 6. If you don't see it, you are logged in as a regular user, the site is already on version 7 (check the admin footer), or the e-mail referred to another site of yours. Send us the site address and we check.
Yes. A theme that runs on 6 runs on 7, whether it extends fruity, vanilla, bootswatch or another custom theme; all three are still core themes in 7.
What breaks: CSS or JavaScript that targets answer fields by the old id (answer123456X7X89), now Q123 or Q123_S456. Selectors on the theme's classes keep working.
Before you upgrade: import the theme (.zip) and a survey (.lss) into a free account (see above) and run through it. Extended theme? Import the parent first.
Only if the theme is based on fruity_twentythree. Surveys on any other theme open in the classic editor. Respondents notice nothing.
Want the new editor for such a survey? Build a theme on fruity_twentythree, port your CSS, assign it to the survey. After the upgrade, one survey at a time.
The upgrade does not rewrite scripts. Scripts using question codes keep working. Scripts that address fields by the old identifiers (answer123456X7X89) need the new names: Q<questionId> for a question and Q<questionId>_S<subquestionId> for a subquestion. Usually the id is the only change; test in a free account. Read more about the new field names in the manual: LimeSurvey 7 Fieldname Refactor.
Core plugins compatible with LimeSurvey 7 stay active. LimeSAML (SSO) also stays active, so your login is not affected. Custom plugins that are not marked compatible with version 7 are deactivated during the upgrade. Contact the developer of the plugin to update it for LimeSurvey 7, then re-activate it under Configuration → Plugins. The new field names in version 7 also affect plugins: a plugin that depends on the old names needs to be updated. See LimeSurvey 7 Fieldname Refactor in the manual.
Check them before you upgrade. LimeSurvey 7 renames the response tables (survey_<sid> becomes responses_<sid>, the timings table likewise), uses the new field names inside them (see the JavaScript question above) and stores the answers of a ranking question in one JSON column. Anything that reads the database directly, such as a BI connection, a reporting script or a custom export, needs the new names: prepare the updated queries before the upgrade and switch them over right after it. Scripts that use the RemoteControl API keep working; error responses now include an error code next to the error text. This cannot be tested in a free account, so if you are unsure which tables or fields your integration uses, contact support before you upgrade.
Yes. LimeSurvey 7 opens the new editor by default. The classic editor remains available for HTML formatting in subquestions, answers and the end screen, for conditions on individual subquestions, and for themes not based on fruity_twentythree. Everything you build in one editor is available in the other. If you are on a Corporate plan, your site keeps the classic editor after the upgrade to version 7; the new editor is not switched on for Corporate accounts yet.
Run one full test response through each active survey. If a condition, a ranking question or an e-mail behaves differently, or you see an error message, contact support with your site address and the survey ID. Do not start the upgrade again.
The 1 November date and the automatic upgrade apply to LimeSurvey Cloud only. Self-hosted installations upgrade with ComfortUpdate or manually. See Upgrade from version 6 to 7 in the manual.