How to migrate from Qualtrics to LimeSurvey without losing longitudinal data
Survey definitions and collected responses can move from Qualtrics to LimeSurvey, but the branching logic, quotas, panels and integrations have to be rebuilt by hand and then validated against the original. That split matters most for organizations leaving over a renewal, a data residency requirement or a licensing change, because the export is the easy part and the rebuild is where longitudinal studies go wrong. Research operations teams usually own the work, with IT handling the server and database and a partner taking on the rebuild when internal capacity is thin. Treat the rebuild and its validation as the main effort, not the file transfer. LimeSurvey Community Edition is free to download and self-host under GPL v2.0, and survey data is stored on the organization's own server or on a provider's server that the organization chooses. Before committing, confirm the required stack against the LimeSurvey GitHub repository, which lists PHP 8.1.29 or later with mbstring and PDO drivers and a supported database such as MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Check the current stable line on the LimeSurvey community downloads page and plan on a supported release rather than a line that has reached end of support. Your recurring costs are then hosting, backups, patching, and staff time, while the software license itself carries no fee. For longitudinal data, the critical check is whether each wave can be reproduced. Keep the original Qualtrics export of every wave in a read-only archive with its question IDs, recode values and export format noted. Then load the same questions into LimeSurvey, run a test wave with known answers, and compare the exported values field by field before the first live wave. Ask whether the team will confirm that any scoring, recoding or skip logic produces identical results in both platforms, and document each difference that remains.
Which Qualtrics capabilities map to LimeSurvey and which need rework
This table compares the Qualtrics capabilities a migration usually touches with their LimeSurvey equivalents, marked as clean, needs rework or gap. Read each row as a planning question: a clean mapping still needs a test survey, while rework and gap rows decide how much of the project must be rebuilt or handled outside LimeSurvey. Confirm every row against the Qualtrics license you hold and the LimeSurvey version you deploy.
| Capability | LimeSurvey equivalent | Status | What to confirm |
|---|---|---|---|
| Question types | More than 30 question types supported | Clean | Map each Qualtrics type used in your projects to a LimeSurvey type and test it in a copy |
| Branching and display logic | Conditions and relevance equations per question or group | Needs rework | Rebuild complex embedded data and piped logic by hand and retest every path |
| Quotas | Quota feature available in LimeSurvey | Needs rework | Recreate quota members and full-quota actions, then verify counts against a sample of responses |
| Multilingual surveys | Multilingual surveys in more than 80 languages | Clean | Export translations from Qualtrics and confirm right-to-left and special character rendering |
| Response exports (CSV, TSV, SPSS) | Standard exports, with the ExportR and ExportSTATAxml plugins for R and Stata | Needs rework | Compare variable names, value labels and coding against an old export before you retire the source |
| File uploads | File upload question type that stores files on the server | Needs rework | Confirm the file-to-response link in the export and plan how to package files alongside the data |
| Invitations and panels | Participant management and invitation tools in LimeSurvey | Gap | Confirm whether Qualtrics panels are used, since LimeSurvey does not provide a managed panel |
| Advanced analytics and dashboards | Built-in statistics and export-based analysis | Gap | Identify which Qualtrics dashboards, text analytics or XM modules your team relies on |
| Reporting and scheduled distribution | Reporting depends on exports and configured email tools | Needs rework | Document every automated report and reminder schedule so each can be rebuilt |
What data moves, what stays behind and which integrations to rebuild
Moving a Qualtrics project to LimeSurvey is less about copying a survey and more about deciding which records, files and connections leave Qualtrics and how each one is read afterward. The cards below separate response data, respondent uploads, survey structure, API pulls and long-term readability so each can be checked before the contract ends.
Response exports and format choice
Qualtrics exports responses in formats that depend on your license, which may include CSV, TSV or SPSS. Pull a test export from a finished project and confirm which formats your account offers, how multi-select and rank questions are split into columns, and whether choice labels or numeric codes come out. Compare that output against the LimeSurvey response export before you rely on it for analysis.
Uploaded respondent files as ZIP
File upload questions are exported separately from the response table, and the export is typically a ZIP archive that must be matched back to response IDs. Confirm with Qualtrics how file names are built and whether respondent identifiers appear in them. Plan where these files will live in LimeSurvey and who may read them, because uploads often contain personal data.
Survey structure and logic
Question text, answer options, piped text, display logic, skip logic and quotas do not travel as a data file. Export the survey as a document or print it from Qualtrics, then rebuild each item in LimeSurvey and test every branch with sample responses. Keep a written map from each old question ID to its new one so later analysis can follow the change.
API-driven pulls and scheduled exports
If scripts or dashboards pull responses from Qualtrics through its API, those integrations stop working at cutover and must be rewritten against LimeSurvey's own interfaces. List every connected tool, its schedule and the fields it reads. Confirm with your Qualtrics administrator which API features your license includes before you retire the credentials.
Codebooks and variable naming
A longitudinal study needs a codebook that maps each variable name, wave and answer code to its meaning, and this document is what keeps old exports readable. Record Qualtrics variable names, value labels and recode rules in the codebook before migration, then assign LimeSurvey codes that match them or document each change. Store the codebook alongside the raw exports, not inside the platform.
Keeping old exports readable
Archived Qualtrics files remain useful only if someone can open them after the license lapses. Keep the original CSV or SPSS files in a read-only location with checksums, and keep a dated record of the export settings used for each wave. Test that each archived file opens in the statistics software your team uses today, and assign an owner for the archive.
The migration sequence from inventory to decommission
This sequence moves each Qualtrics project into LimeSurvey in a controlled order, so every survey has a tested rebuild, a reconciled set of responses and a verified archive before the Qualtrics contract ends. Each step ends with a written output that the next step depends on.
Build a project register from inventory
List every active and archived Qualtrics project, along with its owner, live distribution links, panel or invitation lists, response counts, uploaded file volumes and any longitudinal waves that share a question set. Confirm with each project owner which projects still collect data and which must be kept only for reference. The output is a project register, a single table with one row per project and a decision for each: migrate, archive or retire. Ask Qualtrics which export formats and API access your license includes before you rely on any of them.
Rebuild and test a pilot survey
Choose one representative project, ideally one with branching logic, quotas, multiple languages and file upload questions, and rebuild it in a LimeSurvey instance that runs in your own infrastructure. Recreate question types, piping, logic and quotas, then test every path with internal respondents. Export a test set in CSV or SPSS format and check that variable names, value codes and question wording match the original. The output is a validated pilot export and a short list of any constructs that LimeSurvey handles differently and needs a documented workaround.
Export and archive Qualtrics data
Before any live collection moves, export every migrated project from Qualtrics in the formats you need, including response data, the codebook or data map, survey definition, and respondent file uploads as ZIP. Store the files with checksums in your own repository, and record which export date each file reflects. This step also covers projects you plan to retire, since their data must remain readable after the license ends. The output is an archive manifest listing each file, its checksum and its source project.
Run both platforms in parallel
Rebuild the remaining projects in LimeSurvey and, for each active survey, keep Qualtrics and LimeSurvey collecting responses at the same time for an agreed period. Use separate test and live instances so that duplicate invitations are not sent. Compare response counts and field values daily, and investigate any mismatch in skip logic, quotas or encoding. The output is a reconciliation report per project that shows matching counts, identified differences and the resolution for each.
Cut over links and invitations
Once the reconciliation report is clean for a project, move distribution to LimeSurvey. Replace public links in emails, websites and embedded pages, transfer invitation and panel lists under your data protection terms, and set Qualtrics surveys to closed with a clear message pointing to the new location if respondents still reach the old link. Confirm that LimeSurvey's data hosting location matches your residency requirement, whether you self-host or use a provider. The output is a cutover log listing each project, the date it moved and the owner who signed off.
Verify archives and decommission
Before you cancel Qualtrics, open each archived export and confirm that it loads in the tools your analysts use, that row counts match the source, and that file uploads open correctly from the ZIP. Keep a sample of the original export format in case a longitudinal study needs to be re-analyzed later. Then remove the Qualtrics projects and confirm with your contract owner which data retention terms apply after cancellation. The output is a signed archive record and a decommission checklist that the project owner and the data protection lead both approve.
How the migration changes for research teams, IT-led programs and mid-flight studies
A research group with many active longitudinal studies carries the highest risk of breaking comparability. Each wave of a study has to match the instrument that came before it, so question wording, response scales, skip logic and value codes must survive the move unchanged. The main work is less about building new surveys and more about proving that old and new waves line up, and about keeping the historical exports readable for analysis.
- Freeze instruments before rebuilding: Export the question text, answer codes and routing for each study version, and rebuild only from those records.
- Test value coding in parallel: Run one pilot wave in both platforms and compare exported codes, missing-value handling and multilingual labels.
- Plan for archived exports: Keep the original Qualtrics CSV, TSV or SPSS files alongside the LimeSurvey exports so future analysts can check the source.
- Sequence by study cycle: Move studies between waves rather than mid-wave, so no single wave is split across two platforms.
- Confirm panel handling: Panels and invitation lists are not replaced by LimeSurvey, so decide where contact data will be managed.
Before any cutover, ask the principal investigators to sign off on a mapping document for each longitudinal study.
An IT-led program moving a shared survey service starts from infrastructure rather than instruments. The team must decide who runs the servers, how accounts and roles are provisioned for many departments, and how the service is backed up and upgraded. The risks sit in operations and ownership: a survey service that works for one project can fail quietly when dozens of owners depend on it.
- Size the platform before migrating users: Confirm the PHP, database and web server versions required by LimeSurvey, and build a supported stack with a clear upgrade path.
- Define tenancy and roles: Decide which departments get admin rights, how survey ownership transfers when staff leave, and how data is separated between projects.
- Set the version policy: Check the current stable release and the support status of older lines before committing, since an unsupported line will need a forced upgrade.
- Assign backup and restore ownership: Survey data, uploaded files and the database must be restored together and tested on a schedule.
- Choose hosting deliberately: LimeSurvey Cloud offers hosted regions, while Community Edition runs on your own or a provider's server, so the choice shapes who carries patching and availability.
Ask the service owner to document who responds when a survey breaks during fieldwork, and at what hours.
A team with surveys already in field has the least room for error. Respondents are actively answering, reminder emails may be scheduled, and some responses are still arriving. Moving a live survey mid-collection risks duplicate invitations, lost partial responses and respondents landing on a broken link. The safest approach keeps the active survey where it is until fieldwork closes, and moves only the design work that is not yet live.
- Keep live collection where it is: Do not switch links or invitation codes while a survey is open, since partial responses may not transfer cleanly.
- Export a complete snapshot first: Take a full response export, including uploaded files as ZIP, and verify row counts against the live platform.
- Build the next wave in parallel: Rebuild the next survey in LimeSurvey and test logic and quotas before fieldwork opens there.
- Stop and reconcile at close: When fieldwork ends, export final data, compare totals, and record which respondents were invited on which platform.
- Watch for subscription changes: If a commercial subscription is ending, confirm how long access to collected responses remains before the contract lapses.
Confirm with the survey owner the exact closing date of each live project before any move is scheduled.
What drives migration cost and duration
This table lists the factors that change how much effort a Qualtrics to LimeSurvey move takes, why each one matters, and how to keep it manageable. Costs fall into two groups: one-time rebuild and validation work, and recurring hosting, patching and support. Use it to scope a quote, since the largest drivers are usually the number of live projects and how much logic and quota structure each one carries.
| Driver | Why it changes effort or cost | How to keep it down |
|---|---|---|
| Number of active projects | Each live survey needs its own rebuild, test pass and sign-off, so effort grows with the project count. | Migrate closed projects to archive only and rebuild just the surveys still collecting data. |
| Question logic complexity | Branching, piped text and embedded data must be re-expressed in LimeSurvey's condition and relevance model, and each path needs testing. | Simplify logic where the research design allows, and document every path before rebuilding. |
| Quota schemes | Quotas tied to sample groups often do not transfer directly and must be recreated and tested against live response counts. | List quota definitions in a spreadsheet first and confirm which ones the research team still needs. |
| Multilingual content | Each language version requires translation checks, and right-to-left or special characters need separate display testing. | Export translated text from Qualtrics and reuse it, then have native speakers review only the rendered surveys. |
| Panel and invitation volume | Contact lists, invitation templates and reminder schedules must be moved and checked against consent and opt-out records. | Confirm which panel sources are licensed for reuse before importing any contact data. |
| File upload volume | Respondent uploads are exported as a ZIP archive and must be matched back to responses and stored under the organization's retention rules. | Measure total file size per project early and plan storage capacity before the migration window. |
| Hosting choice | Self-hosting adds server setup, PHP and database administration, backups and security patching. LimeSurvey Cloud moves some of this to the provider, with tiers listed by LimeSurvey and Corporate by quote. | Compare the quoted self-hosted running cost with the tier listed on the LimeSurvey pricing page before choosing the model. |
| Internal skills and support | Teams without PHP, database or survey-methodology experience need outside help, which adds to one-time effort and to recurring support. | Ask for a written scope that includes knowledge transfer and runbooks for the operating team. |
| Historical data continuity | Longitudinal studies need old exports and codebooks kept readable, which adds mapping and validation work for each wave. | Archive final exports and codebooks per wave and check that variable names match before retiring Qualtrics. |
Choosing where LimeSurvey runs and what self-hosting adds
The first decision in this migration is whether LimeSurvey runs on your own servers or on LimeSurvey Cloud, and that choice determines who holds the respondent data, the database and the upgrade work. Community Edition is free to download and self-host, with survey data stored on your server or on your provider's server. LimeSurvey Cloud is sold by subscription and hosted in Germany, Finland, the UK, the USA, Canada or Australia, with Germany or Finland recommended for EU customers. If your residency rules or your Qualtrics data processing terms require data to stay inside your own boundary, self-hosting is the direct route. If you choose Cloud, confirm the hosting region, the subscription's response limits and what happens to collected responses if the subscription lapses, since LimeSurvey's pricing FAQ says the account falls back to a Free package and keeps access to collected responses. Put the region and the data location in writing before you import anything.
If you self-host, the platform requirements set the server work. LimeSurvey requires PHP 8.1.29 or later with the mbstring and PDO drivers, and a database of MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Your platform team should confirm which database your standards already support, because the database carries the response tables, backups and restore testing. On versions, Community Edition 7.6.0 is the latest stable release, and the 6.17.19 line reached end of support on August 31, 2026. Do not plan a new installation or an upgrade path on 6.17.19. Check the LimeSurvey community downloads page on the day you install, because the current stable version changes over time, and budget for recurring work to apply upgrades, PHP and database patches, TLS certificates and backups on a schedule your operations team owns.
What usually goes wrong and how to prevent it
Most failed survey migrations do not fail at the import step. They fail in small mismatches between the old platform and the new one: labels, logic, counts, links and the software version itself. The cards below cover the risks we see most often and a concrete check for each before the Qualtrics contract ends.
Exports that lose labels
Qualtrics exports can be set to show choice text, recode values or both, and variable labels do not always carry over to a flat CSV. If the codebook is not kept, analysts later cannot tell which code means which answer. Export each project in more than one format, store the codebook beside the data, and check that every coded variable in the LimeSurvey export maps to a documented value before deleting anything.
Logic that changes during rebuild
Display logic, skip logic, randomization and piped text are rebuilt by hand, and a single reversed condition can route respondents to the wrong section without any error. Test each branch with scripted responses in LimeSurvey and compare the path counts against the Qualtrics preview. Record every rule in a table with its source question and target so a reviewer can sign off on it.
Quota miscounts
Quotas that count completes in one platform may count partial or screened-out responses in another, which skews the sample for the whole study. Confirm in writing how LimeSurvey counts quota members, whether it includes incomplete responses, and what happens when a quota is full mid-field. Run a pilot with a known number of test responses and reconcile the quota totals before launch.
Invitations sent from the wrong link
Panel and email invitations often carry a platform-specific link or embedded token, and sending a reminder with an old Qualtrics URL can create responses in a survey that is closed or outdated. Generate new participant tokens in LimeSurvey, map each contact to its token, and send a small test batch to internal addresses. Confirm that the old links redirect or fail cleanly during the overlap period.
Respondents resuming partial responses
Respondents who started a survey before the move may return through a saved link and find a blank or duplicated response, or none at all. Decide whether open partial responses will be completed in Qualtrics, migrated as incomplete records, or closed with a notice. Document that decision for each project, since it determines what the longitudinal dataset contains.
Unreadable archives and unsupported versions
An archive of exports and uploaded files is only useful if the file formats and the software that produced them can still be read years later. Store the raw ZIP of uploads, the export files and the survey structure file together with a written note of the LimeSurvey version used. Plan upgrades on the vendor's published support timeline, since the 6.17.19 line reached end of support on August 31, 2026, and an unpatched install exposes respondent data.
Questions buyers ask before moving off Qualtrics
How much does a migration from Qualtrics to LimeSurvey cost?
The cost is driven by scope, not by a list price. LimeSurvey Community Edition is free to download and self-host, so the recurring spend moves to infrastructure, hosting, backups, patching and staff time. Migration work is usually a one-time item: exporting responses and uploaded files, rebuilding questions, logic and quotas, moving panels and invitations, and validating results against the originals. The main drivers are the number of active projects, how complex the branching and quota logic is, how many languages are involved, and how much historical data must stay readable. Ask any implementation partner for a written, fixed-scope quote that lists each deliverable. Confirm with LimeSurvey which hosted plan or support option you would need if you choose Cloud instead of self-hosting, since those prices are published on its pricing page.
Is LimeSurvey free to use?
The Community Edition is free to download and self-host under the GPL v2.0 license, with the option to use any later GPL version. Free does not mean zero cost. You still pay for servers or cloud accounts, a PHP and database stack, storage for responses and uploaded files, backups, security updates and the people who operate the service. LimeSurvey also offers paid hosted plans, which are listed by responses per month or per year, admin users and checkout in euros. Those plans are a separate choice from self-hosting. Before deciding, compare the total cost of running the Community Edition in your own environment with what you pay Qualtrics today, including the staff hours your team would spend on operations.
How long does a Qualtrics to LimeSurvey migration take?
Duration depends on the number of surveys, how many questions each one has, how complex the logic and quotas are, and whether you need historical data to stay comparable across waves. A small set of simple surveys can move quickly, while a longitudinal study with many waves, custom piping and multilingual versions takes longer because each version must be rebuilt and tested. Time is also spent on export validation, stakeholder sign-off and cutover planning. No duration is fixed in advance. Ask for a timeline in the written scope, and ask your implementation partner which milestones they tie to acceptance. Plan for an overlap period in which both platforms are available, so active projects can finish without interruption.
What does our team need to provide for the migration?
Your team needs to supply access to Qualtrics exports, a list of active and archived surveys, the codebook or variable definitions, and a named owner for each research project who can confirm that rebuilt surveys match the originals. Your infrastructure or IT team needs to decide where LimeSurvey will run, provide hosting accounts or on-premises servers, and approve the database, backup and access controls. Security and compliance staff should review where respondent data and uploaded files will be stored. Plan time for these people, because the migration stalls when approvals or decisions wait on them.
Can a research team migrate surveys without outside help?
A research team with someone who has administered LimeSurvey can rebuild simple surveys without outside help. Harder work includes complex skip logic, quotas, multilingual versions, randomization, panel integration and preserving variable names so exports line up across waves. Installing, hardening, backing up and upgrading the platform is an operational task that needs an owner beyond the research group. Many teams split the work: researchers verify question content and logic, while IT or an implementation partner handles hosting, data transfer and validation. Decide early which of these tasks belong to your team, and document that split in the project plan.
Will old Qualtrics exports still be readable after migration?
Old exports stay readable when you keep the original files in a documented, open format and record how each variable was defined. Qualtrics can export responses as CSV, TSV or SPSS, and uploaded respondent files can be downloaded as a ZIP, so archive those alongside a codebook, question wording and the coding scheme for each wave. For LimeSurvey, use its supported export formats and check that variable codes, value labels and response options match the originals before retiring old data. Test a sample of past waves by reopening them in your analysis software. Keep a checksum or record count for each archive so you can prove nothing was lost. Confirm the exact export options available on your Qualtrics license with the vendor.
What happens to our data if a LimeSurvey Cloud subscription expires?
When a LimeSurvey Cloud subscription expires, the account falls back to the Free package and keeps access to the responses already collected. Access to the data is not removed by the downgrade, but the Free package has different limits than the paid plan you were on, so confirm those limits on LimeSurvey's pricing page before you rely on them. Ask the vendor how long data is kept after a lapse, how you export it, and which hosting region stores it. For EU customers, LimeSurvey recommends Germany or Finland. If you self-host, data stays on your own servers, so subscription status does not affect access, but you then carry the responsibility for backups and retention.
Does LimeSurvey cover everything Qualtrics does for us?
LimeSurvey covers survey design, many question types, multilingual surveys, quotas, logic and exports, but it does not replace every Qualtrics module. Qualtrics also offers analytics dashboards, panel services and experience management features that LimeSurvey does not provide. Before migrating, list the modules your organization actually uses, and check each one against LimeSurvey's documented features on its GitHub repository and in its community downloads. Plan separate tools or manual steps for anything missing, and confirm each gap with the vendor or your partner before the contract ends.
How DeployOpen scopes, runs and supports a Qualtrics to LimeSurvey migration
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For a Qualtrics to LimeSurvey move, that means agreeing the survey inventory, data handling and hosting in writing before any work starts, then building and documenting the target instance.
How we scope
- Inventory every Qualtrics project, its question types, logic, quotas and languages before agreeing deliverables.
- Confirm which exports your license allows, including CSV, TSV, SPSS and uploaded file ZIP archives.
- Record where LimeSurvey will run, whether your own servers or a chosen provider, and which data region applies.
How we build
- Set up LimeSurvey on infrastructure you control, with a supported PHP and database combination confirmed against the project's requirements.
- Rebuild priority surveys, logic and quotas, then test them against the original Qualtrics versions.
- Configure invitations, panel imports and any export plugins your analysts depend on, such as ExportR or ExportSTATAxml.
How we hand over
- Deliver a written record of each rebuilt survey, its mapping to the source project and known differences.
- Document the export format and codebook used so older datasets remain readable for longitudinal studies.
- Provide runbooks for backups, upgrades and access control, with the responsibilities for each role named.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Agree the upgrade path in writing, since LimeSurvey release lines reach end of support on a published schedule.
- Keep the scope written and fixed, so changes to survey count or integrations go through a documented change request.
