Microsoft Forms or LimeSurvey: which fits your survey work
You are probably reading this because a Microsoft 365 renewal is coming up, a survey has outgrown Microsoft Forms, or a data residency rule now requires survey responses and uploaded files to stay on servers you control. Microsoft Forms fits short forms, quizzes and polls that sit comfortably inside Microsoft 365. LimeSurvey fits surveys with more than roughly 200 questions, quota logic, many language versions and statistical exports, run on your own server. The decision is not about which tool is better in general. It turns on five things: how many questions each survey contains, whether you need quotas that close or route respondents by answers, how many languages you must publish in, who will operate the server and database, and who will support that stack when something breaks.
Question volume and logic are the first checks. Pull your largest existing survey and count its questions, pages and branches, then test whether the logic you rely on, such as quotas and conditional routing, can be reproduced in the tool you are evaluating. LimeSurvey supports more than 30 question types and multilingual surveys in more than 80 languages, and its plugin list includes ExportR and ExportSTATAxml for statistical export. Confirm each of these against your own survey, because a plugin you need may have its own installation and maintenance requirements. Language is the second check: list every language version you publish today and every version your respondents will need in the next two years.
The cost of LimeSurvey is different in kind from Microsoft Forms. Community Edition is free to download and self-host under GPL v2.0 or any later GPL version, so the license line disappears, but you pay for a server, a supported PHP and database stack (MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, as the GitHub repository lists), patching and backups, and staff time for administration. Those costs recur. If you prefer a managed option, LimeSurvey Cloud offers regions including Germany and Finland, which the vendor recommends for EU customers, but it is a paid subscription. Ask any provider for written support hours, the upgrade path from the 6.17.19 line, which reached end of support on August 31, 2026, and who is accountable for the database and data residency.
Which option fits which survey scenario
This table matches common survey scenarios to the better fit between Microsoft Forms and self-hosted LimeSurvey, with the reason for each choice. Read the last column to see where the answer depends on whether your team can run a PHP and database server.
| Scenario | Better fit | Reason and server skill dependency |
|---|---|---|
| Short internal forms, such as event sign-ups or IT requests | Microsoft Forms | Quick to build and already inside Microsoft 365. LimeSurvey is viable but adds a server to patch and back up, which is hard to justify for a few questions. |
| Quizzes and simple polls | Microsoft Forms | Built-in quiz scoring and Microsoft 365 sign-in cover this well. Recreating scoring rules in LimeSurvey is possible but needs admin time. |
| Surveys over 200 questions | LimeSurvey | Designed for long, branched instruments with many question types. Confirm the exact limit against your Microsoft Forms plan and version before deciding, and test your largest instrument in a staging instance. |
| Quota-controlled research | LimeSurvey | Quota management is a core research feature, so the survey logic fits the study design. Requires a team member who can configure quotas and validate them before fieldwork. |
| Multilingual panels | LimeSurvey | Supports multilingual surveys in more than 80 languages. Translation workflow and review still depend on your own process, not the tool. |
| Statistical exports for analysts | LimeSurvey | Plugins such as ExportR and ExportSTATAxml support analysis tools directly. Analysts without server access can still work from exported files. |
| Strict data residency rules | Depends on hosting | Self-hosting in your own data center or chosen region keeps responses under your control. Cloud-hosted LimeSurvey is an alternative, so confirm the region and provider terms in writing. |
| Teams without PHP or database administration | Microsoft Forms or a managed LimeSurvey provider | Running LimeSurvey well requires PHP, a supported database and regular updates. Confirm whether your team can own this or whether a managed provider or implementation partner should carry it. |
Where survey data lives and who controls it
Microsoft Forms keeps responses inside the Microsoft 365 tenant, while LimeSurvey places them wherever the organization or its hosting provider runs the server. The cards below separate where data sits, which region it lands in, who operates the platform, and what the organization must document itself.
Data location in Microsoft 365
Forms responses sit in the Microsoft 365 tenant, so the data residency terms of that tenant govern them. Your security team should confirm the tenant's data location settings, retention policy, and whether any response exports or linked Excel workbooks create copies outside the intended boundary. Moving to LimeSurvey changes the operator as well as the location, so the review has to cover both.
Self-hosted LimeSurvey server
A self-hosted LimeSurvey instance stores responses in the database you attach to it, such as MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, on PHP 8.1.29 or later. Your team owns the server, database backups, patching and uploaded files. Confirm which database engine your DBA team can back up, restore and monitor before you commit to a deployment.
LimeSurvey Cloud regions
LimeSurvey Cloud offers hosting in Germany, Finland, the UK, the USA, Canada and Australia, and the vendor recommends Germany or Finland for EU customers. Region choice is a contract and data residency question, not only a technical one. Ask the vendor for the data processing terms, sub-processors and where backups are kept, because the region name alone does not answer those questions.
Community Edition on your own servers
The Community Edition is free to download and self-host, and survey data stays on the server you or your provider operate. The licence is GPL v2.0 with the option of any later GPL version, which allows internal use without a per-response fee. The cost sits in infrastructure, administration and support, so budget for those roles and not for a licence.
Identity and access implications
Microsoft Forms relies on Microsoft 365 sign-in for people who build surveys, and respondents often sign in with their work account. A self-hosted LimeSurvey instance uses its own user accounts and administrator roles, so you must decide how staff authenticate, who can export responses, and how leavers lose access. Map each admin role to a named owner and review it on a fixed schedule.
Compliance evidence you must produce
Moving survey data changes the evidence your organization must produce. You will need a record of the hosting location, backup and restore tests, access reviews, patch records and the data processing terms of any hosting provider. An auditor will look for these artifacts in your environment, since DeployOpen prepares these controls and evidence but does not issue audit reports or certifications.
What LimeSurvey brings with it: server, database and support
Choosing LimeSurvey means taking on a small web application stack. Each survey runs on a web server with PHP 8.1.29 or later, with the mbstring and PDO drivers enabled, backed by one of MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, according to the LimeSurvey GitHub repository. Before you commit, confirm which database engine your platform team already operates, supports backups for, and patches on a schedule, because that engine will hold every response, uploaded file reference and respondent record. Also confirm the web server, TLS termination and the PHP version your operating system ships, since the minimum PHP version can differ from the default in some distributions.
Version lifecycle is the item most likely to surprise a team. The latest stable Community Edition is 7.6.0, and the 6.17.19 line reached end of support on August 31, 2026, according to the LimeSurvey community downloads page. A deployment installed from an older line will need a planned upgrade path, including a database backup, a test run against a copy of the survey data and a review of any plugins such as ExportR or ExportSTATAxml, which must be checked against the target version. Patching, backups and restore testing are recurring work, and they fall to whoever runs the server.
Support is the other half of the picture. Community Edition is free to download and self-host, but no vendor contract comes with it, so the organization or its implementation partner answers for uptime, security patches and upgrades. Ask in writing who owns each of these tasks, what the recovery point and recovery time targets are for survey data, and who is on call when a survey closes at a deadline. If you need an external party to carry that responsibility, LimeSurvey Cloud and its hosting regions are a different cost structure, as covered on the LimeSurvey pricing page.
What each option costs to own
Microsoft Forms is included in most Microsoft 365 plans, so the direct cost is usually bundled into a licence the organization already pays for. The recurring cost sits in that agreement, and the organization's own staff time goes into administration, Power Automate flows and any Excel or reporting work built on exported responses. Responses are stored in Microsoft's cloud, so there is no server, database or backup job for the team to run.
- Licences: Confirm which Microsoft 365 plan includes Forms for your users and whether any add-on is needed for features you rely on.
- Infrastructure: None to run. Storage and retention follow your tenant settings.
- Staff time: Tenant administration, sharing policies, and any flows that route responses to other systems.
- Limits: Response and form limits depend on the product and environment, so confirm the current caps for your tenant and for any government cloud.
- Exit cost: Export responses and plan the migration effort before the next renewal, because the bundled cost hides the work of moving data out.
Ask your Microsoft account team to confirm which licence covers Forms for your tenant and which limits apply to your environment.
LimeSurvey Community Edition is free to download and self-host, so the cost moves from a licence fee to the infrastructure and people who run it. Survey data stays on the server you choose, which is the main reason organizations take on this work. Costs recur for hosting, database, backups and patching, and the largest variable is staff time for upgrades and support.
- Infrastructure: A web server with PHP 8.1.29 or later and a supported database. Size it for your peak concurrent respondents and attachments.
- Database: MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, each with its own backup and maintenance routine.
- Backups and upgrades: Regular database and file backups, plus time to move from one release line to the next. The 6.17.19 line reached end of support on August 31, 2026, so plan upgrades on a schedule.
- Staff time: Installation, plugin configuration (such as ExportR for statistical exports), access control and incident response.
- Support: Community support is available, but a paid support arrangement is a separate cost to request in writing.
Before committing, ask for a written estimate of the hours to install, harden, back up and upgrade the instance each year.
LimeSurvey Cloud is a subscription in which LimeSurvey runs the hosting and the tier sets the limits. The tiers are priced in euros at checkout, and the limits are the main driver of which tier fits. Basic supports 1,000 responses per month with 1 admin user, Expert supports 10,000 responses per year with 3 admins, and Business supports 50,000 responses per year with 5 to 10 admins. Corporate is priced by quote.
- Basic: 1,000 responses per month and 1 admin user, suited to small, steady surveys.
- Expert: 10,000 responses per year and 3 admins, for teams running several surveys across departments.
- Business: 50,000 responses per year and 5 to 10 admins, for high-volume research or many administrators.
- Hosting region: Germany or Finland is recommended for EU customers, and the choice can affect data handling terms.
- Expiry: When a subscription expires, the account falls back to the Free package and keeps access to collected responses.
Compare your annual response volume and admin count against the tier limits, and check whether the Business tier's 50,000 annual responses covers peak months.
The Corporate tier is priced by quote, so the cost depends on the scope the vendor agrees with you. Drivers include response volume above Business limits, number of administrators, hosting region, support level and any contractual requirements for data location or service levels. The quote is the place to make these terms explicit before signing.
- Volume and admins: Ask how the Corporate limits compare with Business, including any overage rules.
- Hosting and data location: Confirm the region, the data processing terms and where backups are kept.
- Support and response times: Request the support tier in writing, including any response targets, rather than assuming them.
- Term and renewal: Confirm the billing period, the renewal terms and what happens to the account at expiry.
- Exit terms: Ask how response data is exported and in what format if you move again.
Request a written quote that lists each of these items, and compare it with the staff and hosting cost of running Community Edition yourself.
How a move from Microsoft Forms to LimeSurvey proceeds
The sequence turns a set of Microsoft Forms surveys into a self-hosted LimeSurvey instance that holds the questions, logic, quotas and responses inside the organization's own infrastructure, with each step closed by a written check. The order matters because hosting and database choices affect everything that follows.
Inventory forms and response volumes
The survey owner or Forms administrator lists every form in scope, with its question count, branching, quizzes, file upload questions, languages used, expected response volume and who needs access to results. Count responses per form from the Forms results pages and note any form that relies on Excel integration or Power Automate flows, because those connections will need a replacement. The step is done when the inventory is signed off by the business owner of each survey and the list of surveys to migrate, and the ones to retire, is agreed in writing.
Decide the hosting model
The security or platform lead chooses where LimeSurvey runs: on the organization's own servers, in its private cloud, or with a hosting provider under a contract that defines data location. Include residency requirements, backup ownership and who patches the application. LimeSurvey Community Edition is free to download and self-host, while LimeSurvey Cloud is a subscription with hosting regions listed on its pricing page, and the team should confirm the current regions and terms directly with the vendor. The step is done when a written decision records the hosting model, data location and operating owner.
Provision the server and database
The platform team builds the environment to the LimeSurvey requirements: PHP 8.1.29 or later with the mbstring and PDO drivers, and a supported database such as MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. They set up HTTPS, backups, monitoring and access controls, and they install the latest stable Community Edition release, which the vendor lists as 7.6.0 at the time of research, rather than an older line that has reached end of support. The step is done when the instance loads, a test survey can be created and submitted, and a restore from backup has been tested.
Rebuild surveys, logic and quotas
Survey designers recreate each in-scope form, mapping Forms question types to LimeSurvey types, rebuilding branching as conditions and setting quotas where the survey needs them. Forms quizzes and scoring need separate handling, since they do not map directly. Keep a matrix that links each Forms question to its LimeSurvey counterpart and records any question that was simplified or dropped. The step is done when a reviewer confirms the matrix and every survey is saved as a draft with its logic reviewed.
Test multilingual and quota behavior
Testers run each survey in every language it needs, check that translated text and routing behave as expected, and fill test responses to confirm that quotas stop or redirect respondents at the right thresholds. They also test edge cases such as a respondent who returns to a partial survey. Results from these tests are recorded with the expected and actual outcome for each case. The step is done when all test cases pass or each failure has a documented fix and a retest.
Export and validate historic results
Before any cutover, the team exports historic Forms responses using the formats the Forms results area provides in the organization's own tenant, and confirms those formats in that tenant rather than assuming them. Responses are then loaded or archived alongside the new surveys, and a sample of records is compared field by field against the original exports, with totals, timestamps and file attachments checked. Forms results cannot be assumed to map one-to-one to LimeSurvey response tables, so the reconciliation should be written down. The step is done when the record counts match and the validation sign-off covers every migrated survey.
Cut over survey links
The survey owner publishes the LimeSurvey links, updates email templates, intranet pages, QR codes and embedded forms, and notifies respondents of the new address where needed. Responses are collected in parallel for a short period agreed with the business owner, and the team checks that new submissions arrive in LimeSurvey and that notifications work. The step is done when every active link has been switched and the owner confirms that no live survey still points to Forms.
Retire Microsoft Forms links
Once cutover is confirmed, the Forms owner closes each form to new responses, keeps an archived export under the retention policy, and removes any Power Automate flows or connectors that still reference the old forms. The records of retirement, including the archive location and the person who approved it, are stored with the migration file. The step is done when the retirement log lists every form, its archive and its approval, and no active flow depends on a retired form.
Questions buyers ask before switching surveys to LimeSurvey
What does it cost to run a self-hosted LimeSurvey?
The software is free under GPL v2.0 or later, so the recurring cost is the infrastructure and the people who run it. The main components are the application server running PHP 8.1.29 or later, a supported database such as MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later, backups, monitoring, TLS certificates, and staff time for upgrades and patching. Costs rise with response volume, the number of concurrent respondents, the need for high availability and the size of your uploaded file store. One-time work includes installation, theme and branding, and integration. Ask any implementation partner for a quote built from a written scope that lists each component separately, and ask your own hosting team to price the servers and storage in your environment.
How long does a migration from Microsoft Forms to LimeSurvey take?
The duration depends on the scope, not on a fixed rule. The main drivers are the number of surveys to rebuild, how many questions use logic, quotas or piped text, how many languages each survey needs, whether historical responses must be imported, and how many integrations such as Power Automate flows or Excel reports must be replaced. Environment work also counts, including server build, database setup, identity and access rules and approval of the hosting location. A fixed-scope engagement sets out these items and their order in writing before work starts, so ask for a timeline tied to that list rather than a generic estimate.
Can our in-house team run LimeSurvey without outside help?
A capable team can, provided it has the skills to operate the stack. You will need someone comfortable with Linux server administration, a web server and PHP configuration, relational database administration and backups, and TLS and access control. Survey design work requires a survey owner who understands question types, validation, quotas and multilingual setup. Someone also has to own upgrades, since the community releases move on and older lines reach end of support, so check the current support dates on the community downloads page before committing to a version. Many organizations split the work: internal staff own content and day-to-day administration, while an outside team handles the initial build, hardening and periodic upgrades under a retainer.
What happens to our responses 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. The plan limits then change, so surveys may no longer accept responses at the earlier volume, and features tied to paid plans may stop working. Before any renewal decision, export your responses, questionnaire structures and any uploaded files, and confirm with the vendor which features are removed under the Free package. If the data must stay under your control permanently, self-hosting the Community Edition removes the dependency on a subscription entirely.
Do quotas and multilingual surveys need extra work in LimeSurvey?
Yes, both need deliberate setup, but neither requires custom code in most cases. LimeSurvey supports multilingual surveys in more than 80 languages, so each language version must be translated and reviewed, and translation effort grows with the number of languages and questions. Quotas limit how many responses are accepted for given answer groups, so they must be designed against your sampling plan and tested with sample responses before launch. Confirm both features against the version you plan to run, and test a full survey in every language and with quota edge cases before release.
How do we compare Microsoft Forms and LimeSurvey fairly on the same survey?
Build one representative survey in both tools and score them against the same written criteria. Include the same questions, branching, required fields, file uploads, language versions and quota rules, then run identical test responses through each. Measure what matters to you: how long a respondent takes, how each tool handles a partial response, what the export looks like, whether statistical exports and plugins such as ExportR or ExportSTATAxml meet your analysis needs, and where the data is stored. Record the administration effort for each option too, including upgrades, backups and access reviews, so the comparison covers running costs as well as features.
How DeployOpen helps evaluate, implement and migrate LimeSurvey
DeployOpen plans, implements, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For Microsoft Forms vs LimeSurvey, that means starting from the surveys you actually run, then building a LimeSurvey environment that keeps responses and uploaded files on servers you control.
How we scope
- Inventory current Microsoft Forms surveys, question counts, response volumes and export needs before any design work begins.
- Agree in writing which quotas, multilingual versions, statistical exports and plugins are in scope for the LimeSurvey build.
- Confirm the hosting location, database engine and PHP version your environment supports, against the LimeSurvey requirements.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
How we build
- Deploy LimeSurvey Community Edition in your own cloud account, data center or air-gapped network, with the database you select.
- Configure authentication, administrator roles, survey templates and the question types your surveys depend on.
- Test quotas, skip logic, translated surveys and exports against sample surveys before any live data moves.
- Harden the server, restrict administrative access and set up backups and upgrade procedures for the chosen LimeSurvey release line.
How we hand over
- Document the architecture, configuration, survey build standards and the steps to create, publish and export a survey.
- Deliver runbooks for backups, restores, PHP and database updates, and plugin changes so your team can operate the platform.
- Provide a migration plan that maps each Microsoft Forms survey to its LimeSurvey equivalent, with gaps listed for your review.
- Prepare evidence of configuration and controls for your compliance assessors, who issue any audit reports or certifications.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- Plan upgrades ahead of vendor support dates, such as the end of support for older LimeSurvey release lines, and test them first.
- Confirm with the LimeSurvey project and your own environment which features and plugins apply to your version before you commit.
