Why a SurveyMonkey alternative for academic research starts with the data rules
Self-hosted LimeSurvey is the option that fits a university-run server, and Formbricks is the weaker fit for research instruments. Once survey results with personal data are exported from SurveyMonkey, the institution loses control over where copies sit, who downloads them and how long they persist. An ethics board, data steward or funder will eventually ask where the responses live, who can reach them and how that is recorded. LimeSurvey runs on the institution's own server with a database the research office can name, which gives a direct answer. Formbricks is built around product and customer feedback, with link, website and in-app surveys, so its question handling and research workflows are a less natural match for a formal instrument.
Before choosing a platform, confirm the rules that apply to your data. If your institution takes federal student aid, FERPA's rules on education records and access logging may apply, and the GLBA Safeguards Rule may reach student financial data collected through surveys. If participants include children under 13, the COPPA Rule adds a written security program and a data retention policy with a deletion timeframe. Ask your data protection officer or IRB which of these apply, then write the answers into the survey design before the first invitation goes out, since changing a retention or access model later is harder than setting it at the start.
DeployOpen can plan the server, access controls, backup and retention settings, and assemble the evidence that a university compliance office or external auditor will ask for. DeployOpen does not issue audit reports, attestations or certifications. Those come from independent auditors and certification bodies, so the scope of any engagement should say which controls are configured and documented, and which ones the institution must test and attest to itself.
What the data rules require from a research survey server
Research surveys often collect personal data from students, staff, children or EU residents, and the rules that apply depend on who the institution is and who responds. The cards below set out the duties most likely to shape how a LimeSurvey server is hosted, accessed, logged and emptied. Which of them apply depends on the institution, the funding it receives and the study design, so confirm each with your data protection office or legal counsel.
Outside contractors as school officials
Under FERPA, an outside party such as a hosting provider or survey consultant may receive education records only if it performs a service the institution would otherwise use employees for, stays under the institution's direct control for the use and maintenance of those records, and follows the redisclosure limits. For a self-hosted server, this means the written agreement with any managed hosting provider should spell out control, use and redisclosure. Ask who holds administrator credentials and database backups.
Access limited to legitimate interests
FERPA expects institutions to use reasonable access controls so that school officials see only the education records in which they have a legitimate educational interest. In LimeSurvey, this means restricting survey ownership, admin roles and response-viewing permissions to named study staff, rather than giving every project member full administrator rights. Test the permission model with a non-admin account before fieldwork opens and record who approved each role.
Disclosure record for each access
FERPA requires a record of each request for access to, and each disclosure of, personally identifiable information from education records, including the parties and their legitimate interests, kept for as long as the records are kept. A survey server does not create this log automatically in every configuration, so confirm what LimeSurvey and the web server log, where those logs are stored and how long they are retained. Plan the log retention period alongside the data retention period.
Written security program for child respondents
The amended COPPA Rule requires operators that collect personal information from children under 13 to maintain a written information security program, name a coordinator and complete at least annual risk assessments. Operators must also keep children's data only as long as reasonably necessary and maintain a written retention policy with a deletion timeframe. For school-age surveys, document the deletion schedule for raw responses, invitation lists and exports, and check whether the data is kept on backups beyond that date.
Multi-factor authentication for institutions
Every institution in the Title IV federal student aid programs has agreed to follow the GLBA Safeguards Rule, which requires multi-factor authentication for anyone accessing any information system and notification to the FTC within 30 days of a qualifying event affecting at least 500 consumers. A self-hosted survey server holding applicant, financial aid or alumni data falls within that scope. Confirm which accounts can reach the server directly, enforce MFA on admin and database access, and include the server in the incident response plan.
GDPR and NIS2 for European teams
For researchers in the EU or processing data about EU residents, GDPR governs the lawful basis, purpose limits and transfers of personal data, while NIS2 sets cybersecurity risk-management and incident reporting duties for covered entities. Hosting LimeSurvey in an EU data center keeps responses in one jurisdiction, but it does not decide whether a study is lawful. Ask your data protection officer whether your institution falls under NIS2 and document the processing record for each survey.
Where SurveyMonkey helps research teams and where the server question starts
SurveyMonkey's Team Advantage plan lists exporting results to CSV, XLS, PPT and PDF, along with exporting results for SPSS, so a research team on that plan can move its data into statistical software without writing custom extraction code. Its Enterprise option adds SSO and a choice of US, Canada or EU data center. For many studies, that export path is enough. The question that matters for research is what happens once the data leaves the survey platform: a copy of the results, and often the invitation lists and identifiers that came with them, now sits in files on a laptop, a shared drive or a project folder, each with its own access rules and retention period.
Exports from any hosted service move the risk rather than remove it. Once a file is downloaded, the questions become who controls the server that held the original responses, who can read its access logs, how long the vendor keeps deleted responses and what the export terms say about your rights to the data. Before you rely on a hosted export, confirm with SurveyMonkey which data center applies to your contract, whether the plan you hold includes the Enterprise data center option, and what the agreement says about retention after cancellation. Write those answers into your data management plan, because an institutional review board or data protection office will ask for them.
Self-hosting changes the answers to those questions because the institution decides them. A LimeSurvey server running in a university data center or a contracted facility in your jurisdiction keeps responses, uploaded files and respondent contact data under your own access controls and logs. You still need to confirm the hosting location, backup copies, admin account lists and the deletion schedule with your IT security team. Start that conversation with a written list of your current export formats and the SPSS or R files your analysts depend on, so the replacement can be checked against them before the old plan ends.
Which self-hosted options fit a research data constraint
This table compares self-hosted LimeSurvey Community Edition, LimeSurvey Cloud in a Germany or Finland region, and Formbricks Community Edition against the constraints typical of academic research. Read each row as a question to put to the platform and its hosting provider before you commit survey data to it.
| Requirement | LimeSurvey Community (self-hosted) | LimeSurvey Cloud (Germany or Finland) | Formbricks Community (self-hosted) |
|---|---|---|---|
| Data location | Your university server or chosen provider, so you set the jurisdiction | Hosted by LimeSurvey in a chosen EU region, with Germany or Finland recommended for EU customers | Your own server, so you set the jurisdiction |
| Question types | More than 30 question types | Same question types as the software, subject to plan | Built for link, website, app and email surveys, with fewer research-style question types |
| Multilingual surveys | More than 80 languages | Same language support as the software | Multi-language surveys included |
| SPSS, R and Stata export | ExportR and ExportSTATAxml plugins; SPSS export to confirm in your version | Confirm which export plugins your plan allows before relying on them | Exports focus on feedback data; confirm fit for statistical packages |
| Response limits | No response cap from the software; set by your server | Monthly or yearly response caps by plan | Unlimited surveys, responses and users in Community Edition |
| Workspaces | Multiple surveys and administrators on one installation | Admin users limited by plan | Only one workspace in Community Edition |
| Version to deploy | Deploy 7.6.0, the latest stable release; the 6.17.19 line reached end of support on August 31, 2026 | Vendor manages the version | Check the current release before installing |
| Hosting and maintenance | You run PHP, the database, backups, patches and TLS; needs staff time | Vendor handles hosting and upgrades; less control over the environment | You run the containers, database and updates; enterprise code requires a license key for some features |
| Best fit | Academic surveys with quotas, panels and statistical exports | Teams that want an EU-hosted service without running servers | Product and customer feedback rather than research instruments |
How to deploy LimeSurvey on a university server under research data rules
This sequence takes a LimeSurvey instance from an agreed governance model to a tested server that collects research responses, keeps exports in the institution's control and has a documented retention and recovery position before any participant data arrives.
Agree the data steward and access model
The principal investigator, the institution's research data office and IT agree in writing who is the data steward, who may administer the server, who may create and export surveys, and how each role is granted access. Confirm whether the university treats survey responses as education records, research data under an ethics approval, or both, because that decides which rules apply. The step is done when a signed access matrix and a named steward exist, and the IT team can point to them when asked who can read responses.
Confirm the server stack against supported versions
The IT team checks that the server runs PHP 8.1.29 or later with the mbstring and PDO drivers, and a supported database: MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Confirm each version against the institution's own patch policy and its database team's standards before installation. The step closes with a written record of the PHP build, database version and host location, which becomes part of the system description for the ethics and data protection files.
Install the 7.6.0 release
The administrator installs LimeSurvey Community Edition 7.6.0, the latest stable release listed on the community downloads page, rather than the 6.17.19 line, which reached end of support on August 31, 2026. Record the exact version and checksum from the download source in the change log. The step is complete when the administration panel reports version 7.6.0 and the install log is stored with the server documentation.
Enable and test the export plugins
The administrator enables the ExportR and ExportSTATAxml plugins and runs a test survey with representative question types, including multiple choice, matrix and free text. The tester exports the results and opens the R and Stata files, then compares variable names, value labels and missing-value codes with the codebook. Confirm that the plugin versions match the LimeSurvey release in use. The step is done when the test exports load correctly in the analysis software the research team uses, and the outcome is recorded.
Configure access controls and administrator MFA
The administrator creates named accounts for each role from the access matrix, removes default or shared logins, and restricts administrator rights to the people listed. Multi-factor authentication is set for every administrator account, through the institution's identity provider or an approved method, and the team confirms that the login path is protected by the same controls as other university systems. The step closes with a screenshot or export of the user list and a test login showing MFA is required.
Build multilingual surveys and quotas
The research team builds the survey in each language required by the study, using LimeSurvey's multilingual support, and checks that translated text, skip logic and quota rules match the source version. Quotas are set and tested with dummy responses so that cell limits behave as the protocol describes. The step is complete when a reviewer compares each language version against the approved instrument and signs off on the quota test log.
Set the retention and deletion schedule
The data steward writes a retention and deletion schedule that states how long responses, invitation lists and exports are kept, who approves deletion, and how deletion is logged. The schedule follows the approved ethics protocol and the institution's records policy, and it names any rule that applies to children's data, such as the COPPA Rule where a study collects personal information from children under 13. The step closes when the schedule is signed and linked from the survey system documentation.
Test backups and restores before live collection
The IT team configures scheduled backups of the database and the upload directory, then performs a full restore to a separate environment and checks that surveys, responses and uploaded files open correctly. Confirm backup location, encryption and access rights against the institution's standards. The step is done when a restore test report exists, showing the survey count and response count matched the source before the survey goes live to participants.
What the principal investigator, data steward and IT team each decide
The principal investigator owns what the survey measures and how respondents are asked. In LimeSurvey, that means choosing question types from the more than 30 available, setting quotas so sample composition matches the protocol, and building multilingual versions that carry the same meaning in every language. The consent wording is also the PI's responsibility, and it has to match what the platform actually stores, including any IP addresses, timestamps or contact details.
- Instrument design: Confirm each item, skip logic and scale against the approved protocol, and freeze the version that goes to the ethics board.
- Quotas: Write quota rules as they will be applied, and test how they behave when a quota fills mid-field.
- Multilingual versions: Decide which translation is authoritative and who verified each language.
- Consent wording: Align the consent text with the data the platform collects and the retention period the data steward approves.
- Statistical exports: Test the SPSS, R or Stata export on a dummy dataset before launch, so variable labels and value codes match the analysis plan.
Keep the approved protocol version, the tested survey export, the translation sign-off and the consent text as dated records. Confirm the export plugin versions with your IT team, since they must work with the installed LimeSurvey release.
The data steward or privacy office decides how long identifiable data is kept, who may access it, and what legal role any outside party plays. If the research involves students, the FERPA regulations in 34 CFR Part 99 may apply to the institution, and a contractor may receive education records as a school official only under the conditions in 34 CFR 99.31(a)(1)(i)(B). Children under 13 bring in the COPPA Rule, which requires a written retention policy with a deletion timeframe.
- Retention: Set a deletion date for identifiers and raw responses, separate from anonymized analysis files.
- Access: Define which named roles can view identifiable responses, and enforce this with platform access controls, as 34 CFR 99.31(a)(1)(ii) expects for school officials.
- Contractor status: Document whether any vendor or hosting partner qualifies as a school official and remains under the institution's direct control.
- Disclosure log: Record each request for access and each disclosure of personally identifiable information, as 34 CFR 99.32 requires.
- Incident path: Agree who is told about a suspected breach and how quickly, including any GLBA Safeguards Rule notification duties that apply to the institution.
Keep the signed retention schedule, the access list, the contractor agreement or determination, and the disclosure log. Ask legal counsel whether the institution is subject to FERPA, COPPA or GLBA for this particular study, since the answer depends on funding and population.
IT decides where LimeSurvey runs, which database it uses, how backups are taken and what gets logged. LimeSurvey requires PHP 8.1.29 or later with mbstring and PDO drivers, and supports MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Its Community Edition is free to self-host, so the main costs are infrastructure, administration time and support. Confirm the current stable release, which is 7.6.0 on the community downloads page, and avoid building on the 6.17.19 line, which reached end of support on August 31, 2026.
- Hosting location: Place the server in a university data center or an approved region, and confirm that responses, uploads and invitation lists stay in that location.
- Database: Choose one of the supported engines and confirm its version is still under vendor support.
- Backups: Test restores, not just backup jobs, and encrypt backups that contain personal data.
- Logging: Turn on web server and application logs that show administrative access and export activity, and keep them for the period the data steward sets.
- Patching: Assign owners for PHP, the database and LimeSurvey updates, and track end-of-support dates.
Keep the architecture diagram, the supported version record, restore test results, access logs and the patch calendar. Confirm with the vendor or your own security team how the chosen export plugins are installed and maintained.
What auditors and ethics reviewers ask to see
Ethics boards, data protection officers and auditors rarely accept a claim that data is safe. They ask for records they can inspect. The cards below list the artifacts that a self-hosted LimeSurvey deployment can produce for a research program, and they note which ones your own institution must own.
Access and disclosure record
Where identifiable participant data is involved, FERPA requires institutions to log each request for access to and each disclosure of personally identifiable information, with the parties and their legitimate interests, for as long as the records are kept. For a LimeSurvey instance, build this from web server and application logs, export events and account changes, and check that the log retention matches the study's retention period. Confirm with your IRB or privacy office which events they want recorded.
Role-based access and admin lists
Reviewers want to see who can open raw responses, who can export them and who can change survey settings. LimeSurvey separates super administrators from survey-level roles, so keep a dated list of every admin account, its role and its owner. Remove accounts for departed staff and students, and review the list at each survey close. Access reviews are a common finding in institutional audits, so schedule them and keep the signed results.
Multi-factor authentication settings
The GLBA Safeguards Rule requires multi-factor authentication for anyone accessing an information system, and institutions that take federal student aid have agreed to comply with it. Document how administrators sign in to the LimeSurvey server, the database and the hosting console. Export a screenshot or configuration record of the identity provider or reverse proxy that enforces the second factor. Note that LimeSurvey's own login may not enforce MFA by itself, so confirm this in your deployment.
Written security program and risk assessments
Where a study collects personal information from children under 13, the amended COPPA Rule expects a written information security program with a named coordinator and at least annual risk assessments. Prepare the program document, the coordinator designation and dated risk assessment reports covering the LimeSurvey server, its database and its backups. DeployOpen can prepare these artifacts for your environment, but the program and its adequacy are decisions your institution must own.
Retention and deletion policy
COPPA operators may keep children's personal information only as long as reasonably necessary, and they must maintain a written retention policy with a deletion timeframe. Research ethics approvals usually set a similar limit for identifiable data. Write one policy that states how long responses, invitation lists and exported files are kept, who approves deletion and how deletion is recorded, and then test that the database and backups follow it. Ask your ethics board whether anonymized datasets may be kept longer.
Backup, restore and hosting terms
Reviewers ask for backup and restore test results, not just a backup schedule. Keep dated records of at least one full restore of a LimeSurvey database and its upload directory to a separate host. For any external hosting, including a university data center or a managed provider, collect the signed data processing terms, the sub-processor list and the data location. LimeSurvey Cloud lists hosting regions and recommends Germany or Finland for EU customers, which is a useful reference when comparing options. Confirm each term with the provider directly.
Questions research teams ask before moving off SurveyMonkey
What drives the cost of self-hosting LimeSurvey compared with a SurveyMonkey team plan?
The software itself is free: LimeSurvey Community Edition is free to download and self-host, so the cost is in the components around it. These are the server or cloud instance, the database, backups, the time to rebuild surveys, email delivery for invitations, and support or maintenance. SurveyMonkey's Team Advantage plan lists a 50,000 response per year limit and bills per user from 3 users, so a hosted plan recurs per seat and per response cap. Self-hosting costs recur for infrastructure and staff time, and they rise with server size, backup retention and the number of projects. Ask any quote for a line-item breakdown of hosting, database administration, rebuilding surveys, support hours and any upgrade work, and confirm which items are one-time and which recur each year.
How long does a SurveyMonkey to LimeSurvey migration take?
No duration is fixed in the supplied facts, so treat any timeline as something to agree in writing. The time depends mainly on the number of surveys, the complexity of skip logic, quotas and piping, how many languages each instrument needs, whether panels and invitation lists move, and whether the server and database are already in place. Pilot a single representative survey first, because it reveals how much rebuilding and translation work the rest will need. Your team should also plan time to run test responses and verify that exported data matches the original before the SurveyMonkey plan ends.
What does the university IT team need to provide for a self-hosted survey server?
The IT team typically provides the hosting environment, the database, identity and access arrangements, network and backup policy, and a named owner for patching. LimeSurvey requires PHP 8.1.29 or later with mbstring and PDO drivers, and one of MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Confirm with your IT team which of these engines is already supported and backed up. They should also agree on TLS certificates, a domain name, outbound email for invitations and reminders, log retention, and where encrypted backups are stored. Ask them to confirm that the server sits in the region the institution's data rules require.
Can a research team run a self-hosted LimeSurvey instance without outside help?
A research team can build and field surveys in LimeSurvey without outside help once an administrator has installed and secured the instance. Ongoing operation is different: patching, backups, database maintenance, plugin compatibility and restore testing need someone with server administration skills. Current stable release information is on the LimeSurvey community downloads page, and the 6.17.19 line reached end of support on August 31, 2026, so the upgrade path is a recurring task. Many institutions split the work, with researchers owning instruments and data quality while central IT or an implementation partner owns the platform. DeployOpen plans, implements, hardens, backs up, upgrades and supports self-hosted platforms in your own infrastructure under a written, fixed scope, and it offers ongoing support as a retainer.
Does LimeSurvey export directly to SPSS, and what should I confirm?
The supplied facts do not confirm a native SPSS export in LimeSurvey, so do not assume one. What is confirmed is that LimeSurvey is GPL licensed, supports more than 30 question types, and offers plugins including ExportR and ExportSTATAxml for R and Stata. Test a full export from a sample survey with your own variable types, value labels, missing-value codes, multi-select items and multilingual text, then open the file in SPSS and compare it with the original. Confirm with the LimeSurvey project which export formats its current release provides. SurveyMonkey lists SPSS export on its Team Advantage plan, so keep an archived copy of your SurveyMonkey data before cancelling.
Does hosting LimeSurvey on our own servers make us FERPA or GDPR compliant?
No. Hosting alone does not make an institution compliant with FERPA or GDPR. Self-hosting gives you control over where responses are stored and who can access them, which supports those obligations, but compliance depends on policies, access controls, contracts with any outside party, retention rules, and records of disclosures. FERPA under 34 CFR Part 99 requires access controls for school officials and a record of disclosures, while GDPR under Regulation (EU) 2016/679 sets lawful basis, data minimization and processor obligations. Your legal or privacy office should map each survey to its obligations. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications, which independent auditors and certification bodies provide.
What should I ask for in a quote before choosing a self-hosted survey platform?
Ask for a written scope that names each deliverable, the surveys and languages in scope, the target hosting environment, the database, and what data will be migrated from SurveyMonkey. Request an itemized view of implementation, hardening, backup and restore testing, documentation, training for researchers, and ongoing support as separate lines. Confirm which items are one-time and which recur, how change requests are priced, and who is responsible for upgrades and end-of-support releases. DeployOpen works from fixed, written scopes with agreed deliverables and timelines, and it does not publish a price list, so the quote follows from that scope.
How DeployOpen implements a research survey server under these rules
DeployOpen plans, implements and hands over self-hosted LimeSurvey servers inside the institution's own infrastructure, so research teams can move from SurveyMonkey without sending respondent data to a third party. Each engagement starts with a written scope that covers the research workflows, data-handling obligations and hosting choices the institution has to meet.
How we scope
- We agree a written scope covering survey types, question formats, quotas and multilingual versions before any build starts.
- We map which data-protection rules apply to your study, such as FERPA, COPPA or GLBA, and record the controls each one needs.
- We confirm the hosting location, database engine and export plugins your analysts need, including R and Stata, in the scope document.
How we build
- We install LimeSurvey on your own servers or your chosen provider, with the PHP and database versions the release requires.
- We configure access controls so only staff with a legitimate research interest can view identifiable responses and exports.
- We set up the ExportR and ExportSTATAxml plugins and test SPSS, R and Stata imports against sample data from your study.
How we hand over
- We deliver documentation for administrators, survey builders and analysts, covering backups, access rules and export procedures.
- We provide a record-keeping procedure for disclosures and access requests, so your compliance office can evidence how the system is run.
- We walk your team through the handover and confirm acceptance against the written scope, with no certification or audit report issued by us.
How we support
- Engagements are fixed-scope, and changes to questionnaires or data handling are scoped in writing before they are made.
- Ongoing support, upgrades and continuous security testing are available as a retainer after handover.
- Ask us to confirm current release support dates with the vendor and your own environment before planning any upgrade.
Sources and further reading
- 34 CFR Part 99, Family Educational Rights and Privacy, eCFR ↗
- 16 CFR Part 312, Children's Online Privacy Protection Rule, eCFR ↗
- 16 CFR Part 314, Standards for Safeguarding Customer Information, eCFR ↗
- Regulation (EU) 2016/679 (GDPR), EUR-Lex ↗
- LimeSurvey GitHub repository ↗
- LimeSurvey community downloads ↗
