Jotform vs LimeSurvey

Jotform suits payment forms, templates and quick intake forms. LimeSurvey suits organizations running research-grade surveys that need quotas, multilingual questionnaires and statistical exports on servers they control.

On this page

Which fits your Jotform renewal: a survey platform or a form builder?

If your Jotform renewal is coming up, or a data residency rule is forcing the question, the first thing to settle is what the forms actually do. If most of them collect answers for analysis, such as employee climate instruments, research panels or multilingual feedback studies, LimeSurvey is the closer fit. Its strengths are survey logic, quotas, more than 30 question types, multilingual surveys in more than 80 languages, and statistical export plugins such as ExportR and ExportSTATAxml. If most of your forms are intake forms, payment requests, approval workflows or template-driven documents, Jotform's form builder and its app-style features are the more natural match, and a survey platform will feel like the wrong tool.

Many organizations have both kinds of work, so treat the decision as a split rather than a single swap. Inventory your active forms and tag each one by purpose. Note which ones take payments, generate PDFs, trigger approvals or rely on Jotform's templates, because those steps need a plan of their own, whichever platform takes the survey work. Also confirm which responses are personal data and where each platform would store them, since LimeSurvey's Community Edition keeps data on the server you run or on your provider's server, and the LimeSurvey Cloud regions are a separate commercial choice.

The decision turns on three questions. First, is the work survey-heavy or form-heavy? Second, which payment or PDF steps must keep running after the switch? Third, can your team run a LAMP-style server, meaning a PHP application with a supported database, patched and backed up over time? If the answer to the third question is no, a managed hosting arrangement or a fixed-scope implementation partner changes the cost picture, and that should be priced into the comparison before the renewal date.

Which platform fits which scenario

This table matches common survey and form scenarios to the platform that usually fits best, with the reason tied to the features each product offers. Read each row as a starting point, then confirm the points marked for checking against your own requirements and environment.

ScenarioBetter fitReason
Multilingual patient or citizen surveysLimeSurveyLimeSurvey supports multilingual surveys in more than 80 languages, which suits instruments that must reach respondents in several languages from one survey structure.
Research panels with quotasLimeSurveyLimeSurvey is built around survey design, and quota management and statistical exports are areas to confirm in your installed version and plugins such as ExportR or ExportSTATAxml.
Employee feedbackLimeSurvey or FormbricksBoth can run anonymous or link-based surveys, so choose LimeSurvey for complex branching and reporting, and Formbricks if the feedback is short and tied to in-product or website touchpoints.
Event registration with paymentsJotformJotform's payment forms and templates cover checkout flows that LimeSurvey is not designed to handle, so confirm which payment processors any self-hosted option supports before choosing it.
Intake forms with PDF outputJotformJotform offers PDF output and document-style templates; for LimeSurvey, plan a separate step to generate documents from exported responses.
HIPAA-covered intakeSelf-hosted LimeSurvey in your own environmentJotform's HIPAA capability starts at its Gold plan, while a self-hosted LimeSurvey instance keeps data inside your environment, where you define the safeguards and audit logs yourself.
Survey hosting location controlLimeSurvey (self-hosted)Self-hosted LimeSurvey stores responses on your or your provider's server, so you choose the region, while the LimeSurvey Cloud regions are a separate hosted option to compare.

Where survey data lives and who controls it

Where responses sit decides who can read them, how long they persist and which compliance questions you must answer. The cards below cover the hosting choices for LimeSurvey, the access model around them, and the evidence work that remains with your own team and auditors.

Self-hosted Community Edition

LimeSurvey Community Edition is free to download and self-host, and survey data is stored on the server you or your provider operate. Nothing leaves your environment unless you configure it to. The trade-off is that you own patching, backups, TLS and database administration. Confirm which PHP and database versions your instance needs before you plan the server build, and document who holds root and database access.

Cloud hosting region choice

LimeSurvey Cloud offers hosting in Germany, Finland, the UK, the USA, Canada and Australia. LimeSurvey recommends Germany or Finland for EU customers. Ask the vendor which region holds backups, support access logs and any subprocessor data, since the region of the primary database alone does not settle the question. Record the chosen region in your data inventory before the first survey goes live.

Administrator and respondent access

Jotform keeps access control inside its own account model, while a self-hosted LimeSurvey instance relies on the accounts, roles and authentication you configure. Limit the number of super administrators, separate survey designers from users who only read results, and decide how administrator logins are protected with strong authentication. Review who can export responses, since exports are where most survey data leaves the system.

Expired subscription and data retention

When a LimeSurvey Cloud subscription expires, the account falls back to the Free package and keeps access to collected responses. Read this as a retention question, not a backup plan. Confirm how long responses and uploaded files persist after a survey closes, who deletes them on request, and how deletion propagates to backups and exports you have already made.

Compliance evidence stays with you

Self-hosting moves control of the data to you, which also moves the evidence burden. Your auditors will ask about access reviews, change records, backups and encryption settings for the survey server. DeployOpen can prepare systems, controls and evidence for a compliance assessment, but it does not issue audit reports, attestations or certifications. Those come from independent auditors and certification bodies.

Data protection terms with the provider

If you use LimeSurvey Cloud, your data protection obligations depend on the contract and processing terms the provider offers, not on the hosting region alone. Ask for the data processing agreement, the list of subprocessors and the breach notification process in writing. For self-hosted deployments, the equivalent work is internal: a documented processing record, retention schedule and tested restore procedure for survey data.

What GPL licensing means for a LimeSurvey deployment

LimeSurvey is licensed under GPL v2.0, with the option to use any later GPL version, and the Community Edition is free to download and self-host. For an organization running surveys internally, that means no per-response, per-seat or per-form fee to the software publisher. The cost of running it sits in the server, the database, the staff who operate it and any support contract you choose to buy. Using the software for internal survey work, collecting responses from staff, customers or the public, and keeping the data on your own infrastructure does not by itself trigger the copyleft obligations of the GPL. Those obligations concern distribution of the software, not its use inside your organization. The obligations do become relevant when you modify LimeSurvey or give copies of a modified version to someone outside the organization, such as a partner, a subsidiary or a hosting provider that serves your surveys under its own brand. In those cases the GPL generally requires that the recipients receive the corresponding source code under the same license terms. Plugins, custom themes and integrations that are built against LimeSurvey's code can fall under the same question, so confirm how your team and any implementation partner will package and share custom work before you start. Also confirm whether your contract with any hosting provider or implementation firm assigns ownership of custom code to you.

Jotform's plans are commercial subscriptions measured by active forms, monthly submissions, views and storage, and the terms that govern use are set by the vendor. Those terms can change at renewal, and the right to keep using a feature often depends on staying on a paid tier. A self-hosted LimeSurvey deployment works differently: the license does not expire, and the version you installed remains yours to run. The practical question is not whether you may use the software, but whether your organization is prepared to maintain it. Security fixes arrive in new releases, and older branches reach end of support. The 6.17.19 line reached end of support on August 31, 2026, so your upgrade plan is a license-independent operational task you still need to own. Before you rely on this reading, ask qualified counsel to review the license terms against your intended use, especially if you plan to offer surveys to external parties through a modified build, embed LimeSurvey in a commercial product or sign agreements that restrict source disclosure. Ask your implementation partner for a written list of every custom component and its license, and record who holds the right to modify and redistribute each one.

The server LimeSurvey needs to run

LimeSurvey is a PHP application backed by a relational database, so the self-hosted option is a small web stack you operate yourself. The cards below cover the supported components, the version lifecycle, and the recurring work that moves cost from the subscription line to your own staff.

PHP runtime and extensions

LimeSurvey requires PHP 8.1.29 or later, with the mbstring and PDO drivers enabled. Confirm the exact PHP build and extension list against the current release notes before you provision a server, because hosting images from older distributions often ship older PHP. Your platform team owns PHP patching on the same schedule as the operating system.

Supported database engines

LimeSurvey supports MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Pick the engine your database team already backs up, monitors and patches, because survey responses live in this database. Ask your DBA to confirm the engine version is still within its vendor support window for the planned life of the instance.

Current stable line and support window

Community Edition 7.6.0 is the latest stable release. The 6.17.19 line reached end of support on August 31, 2026, so any instance still on it no longer receives fixes. Plan upgrades as a recurring task with a test instance, and confirm the support period for any line you intend to run before you go live.

Patching and upgrade effort

Each LimeSurvey upgrade changes the application code, plugins and sometimes database structure, so an upgrade needs a staging copy, a tested plugin list and a rollback plan. Budget this as internal or contracted labor. Ask any implementation partner for a written upgrade runbook and the expected effort per release, rather than assuming a patch is a single command.

Backups for responses and uploads

Back up the database and the upload directory together, since question files and response attachments are stored outside the database. Test restores on a schedule, and record the recovery point you can meet. Confirm with your backup platform that it captures both sides consistently, because a database restore without matching files leaves broken references.

Hosting and operations ownership

Self-hosting means your organization carries TLS certificates, the web server, PHP-FPM tuning, monitoring, access control and the cron jobs LimeSurvey relies on. Decide who answers at 2 a.m. when a survey stops accepting responses. Compare this with LimeSurvey Cloud, where the hosting and database are supplied by the vendor but regional hosting and subscription terms apply.

What a self-hosted LimeSurvey costs compared with Jotform

Is LimeSurvey free to run compared with a Jotform subscription?

LimeSurvey Community Edition is free to download and self-host, so the license line disappears, but the operating cost moves to your own infrastructure and people. Jotform is priced by active forms, monthly submissions, form views and storage, so its bill rises as your survey volume grows. With LimeSurvey, you pay for the server, storage, backups, administration and any outside help you choose. Compare your current Jotform invoice with those components, not with zero. Ask your team to pull the last twelve months of invoices so the comparison starts from your real plan and add-ons.

What drives the recurring cost of hosting LimeSurvey yourself?

Recurring costs follow three drivers: compute, storage and the labor to keep the instance running. Compute depends on the number of concurrent respondents and the database you choose. 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, so your database licensing and maintenance differ by choice. Storage grows with uploaded files and retained responses. Plan for patching: the 6.17.19 line reached end of support on August 31, 2026, so you must stay on a supported release such as 7.6.0.

Which LimeSurvey costs are one-time migration costs?

One-time costs cover the work of moving out of Jotform and standing up the new instance. These include building the server environment, installing and hardening LimeSurvey, rebuilding survey logic and question structures, testing multilingual versions, exporting past Jotform submissions and uploaded files, and changing embeds on your website. Plugins such as ExportR and ExportSTATAxml may need configuration if you rely on statistical exports. Staff time for testing and sign-off is also one-time. Ask for these as separate line items so you can see what is paid once and what continues each year.

What does DeployOpen charge for a LimeSurvey implementation?

DeployOpen does not publish a price list. Its engagements are usually fixed-scope, with scope, deliverables and timelines agreed in writing before work starts, and a quote follows from that written scope. Optional services can include planning, implementation, customization, integration, hardening, backup setup, upgrades, documentation and support. Ongoing support, upgrades and continuous testing are available as retainers. Ask for each service as a separate line so you can decide which parts your own team will handle. Any fee you see should trace back to a deliverable listed in the scope.

How much internal staff time does a self-hosted survey platform need?

The staff time depends on who will own the instance and how much of it you build yourself. Typical ownership tasks include applying security updates, monitoring the server, checking backups, managing user accounts and answering survey-builder questions from colleagues. A small team may absorb this into existing duties, while a regulated organization usually needs named owners and documented procedures. Estimate hours by listing each task, its frequency and the role responsible. Treat this as an internal figure you measure, since no supplied source gives a duration for it.

What should I request in a quote for a LimeSurvey deployment?

Ask for a written scope that lists each deliverable, the environment it runs in, and the acceptance criteria. Request separate line items for planning, installation, hardening, migration of surveys and responses, backup configuration, documentation, training and any retainer for upgrades or support. Ask which database engine and PHP version the quote assumes, how uploaded files and responses are migrated, and what happens during the cutover from Jotform. Confirm who holds administrator credentials at handover and what documentation you receive.

Does LimeSurvey Cloud change the cost comparison?

LimeSurvey Cloud is a hosted option that replaces the server line with a subscription, so it is a different cost model from self-hosting. As read in October 2026, its plans include Basic with 1,000 responses per month and 1 admin user, Expert with 10,000 responses per year and 3 admins, Business with 50,000 responses per year and 5 to 10 admins, and Corporate by quote, with checkout in euros. Hosting regions include Germany, Finland, the UK, the USA, Canada and Australia. Confirm current limits on the LimeSurvey pricing page before you compare it with your own server costs.

What hidden costs appear after a LimeSurvey go-live?

Hidden costs usually come from ongoing maintenance rather than the initial build. Watch for version upgrades that require testing of surveys and plugins, backup storage growth as responses accumulate, certificate and monitoring tools, and staff turnover that leaves one person holding all administration knowledge. Budget for periodic restore tests, because a backup you have never restored is not a proven control. Ask your provider to document each recurring task so the cost of ownership stays visible after the project closes.

How a move from Jotform to LimeSurvey proceeds

The sequence sorts Jotform forms into surveys and transactional forms, stands up a self-hosted LimeSurvey server, rebuilds the survey logic and multilingual versions, and moves past responses and uploaded files before the website embeds are switched.

  1. Inventory and classify every Jotform form

    The survey owner and an administrator list every active form, its owner, its response volume, its question types, its conditional logic and its integrations. Each form is tagged as a survey (research, feedback, questionnaires, quotas) or as a transactional form (payments, PDF generation, approvals, app-style data entry). Only the survey group goes to LimeSurvey in this move. The step is done when every form has a tag, an owner and a named destination, and the transactional list is handed to whoever will replace payment and PDF steps.

  2. Stand up the LimeSurvey server

    Your infrastructure team installs LimeSurvey Community Edition, which is free to download and self-host, on infrastructure you control. The team confirms the PHP version, the mbstring and PDO drivers, and a supported database (MySQL, PostgreSQL, MariaDB or MSSQL) against the requirements in the project repository, and selects the release line before installation. Backups, TLS, administrator access and the location of stored survey data are configured now, so that data residency is settled before any respondent data arrives. The step is done when a test survey can be created, answered and exported on the production-grade environment.

  3. Rebuild survey logic, quotas and question types

    Each classified survey is rebuilt in LimeSurvey using its question types, conditional display rules and quotas. Jotform conditions and hidden fields rarely map one for one, so the team rewrites each rule on paper first and then implements it, noting any logic that LimeSurvey expresses differently. Quotas are configured from the survey design, not from a spreadsheet afterwards. The step is done when a reviewer has walked every path through each rebuilt survey and signed off the list of intentional differences from the Jotform original.

  4. Test multilingual versions and exports

    Each language version is entered, translated and checked in the target language, including the consent text, the data protection notice and any validation messages. The survey team then runs test responses through every language and confirms the statistical and raw exports open correctly in the tools analysts use. Plugins such as the export plugins supplied with LimeSurvey should be checked against the analysis software before they are relied on. The step is done when each language has a sign-off from a native reader and the export test matches expected values.

  5. Export past responses and uploaded files

    Past submissions and uploaded files are exported from Jotform in a format that can be checked row by row, then imported or stored where LimeSurvey can reference them, under the access rules set in the earlier step. Record counts, date ranges and file counts are compared between the source export and the destination, and any file that cannot be linked to its response is logged as an exception. The administrator confirms with the data owner which historical data must be kept, for how long, and where it is archived. The step is done when the reconciled counts match and the exception list has an owner.

  6. Replace payment and PDF steps with other tools

    Jotform's payment collection and PDF generation are not part of LimeSurvey, so each transactional form from the first step is handled by a separate tool chosen with the business owner. Options include a payment provider's own checkout, a document generator in your infrastructure, or a workflow tool, and each choice is checked for where it stores personal and payment data. The team confirms that no payment data flows through LimeSurvey and that any PDF output is stored under the same controls as the original responses. The step is done when each transactional form has a documented replacement and an approved data flow.

  7. Swap website embeds and retire the Jotform forms

    Each Jotform embed on your websites and internal portals is replaced by the LimeSurvey link or embed that the survey owner approved, and the change is tested in each browser and on mobile devices used by respondents. Notifications to the team and to respondents are updated, and the old Jotform forms are closed to new responses only after the replacement is live. The team keeps the Jotform account active until the exports from the earlier step are verified and archived. The step is done when no page points at a Jotform form and the account can be closed.

Questions buyers ask before switching from Jotform to LimeSurvey

How much effort does a switch from Jotform to LimeSurvey take?

The effort depends mainly on how many forms are live, how many questions each one has, and how much conditional logic sits inside them. LimeSurvey organizes work around surveys, question groups and questions, so a Jotform form with many branches usually needs its logic rebuilt by hand and tested again. Plan the work in four parts: inventory the active forms and their owners, rebuild the surveys in a test instance, move the response history, and repoint the links and embeds on your websites. Ask any implementation partner for a written scope that lists each survey, the export format for past responses, and who signs off on the test results before cutover.

Can our team migrate the surveys without outside help?

A team with someone who has administered LimeSurvey, a working PHP and database stack, and time to test can do a small migration alone. The risk rises with the number of surveys, the presence of multilingual content, and the need to keep response histories consistent. Most teams find that the server build, backups, upgrades and access control take more ongoing attention than the surveys themselves. A fixed-scope engagement from DeployOpen can cover planning, building the platform inside your own infrastructure, rebuilding selected surveys and handing over documentation, while your staff keep ownership of the survey content.

Which parts of the switch need internal staff?

Some decisions can only be made inside your organization:

How long does a Jotform to LimeSurvey migration typically take?

The duration is driven by the number of active surveys, the complexity of logic and quotas, the number of languages, the volume of historical responses and uploaded files, and how many systems link to the forms. Surveys with quotas or statistical exports need more validation than a simple contact form. Internal review cycles and change approvals often take longer than the technical work. Ask for a timeline in the written scope that ties each milestone to a deliverable, and confirm with your security team how long they need to review the new hosting before anything goes live.

Is LimeSurvey Cloud an option instead of self-hosting?

Yes, LimeSurvey offers a hosted service in several regions, including Germany, Finland, the UK, the USA, Canada and Australia, and it recommends Germany or Finland for EU customers. Its plans are sized by responses per month or per year and by admin users. Cloud removes server administration, but your data then sits with the provider in the region you choose. If your requirement is that responses, uploaded files and respondent data stay on your own servers, self-hosted Community Edition is the option that meets it. Confirm the hosting location, backup policy and contract terms directly with LimeSurvey before deciding.

What happens to collected responses if a LimeSurvey Cloud subscription lapses?

When a LimeSurvey Cloud subscription expires, the account falls back to the Free package and keeps access to the responses already collected. The fallback changes what you can do, not what you already hold, so you can still view and export that data. Before relying on this, check the Free package limits for new surveys and responses, and set a calendar reminder for renewal dates. Export your results to your own storage on a regular schedule so that continuity does not depend on a single account state.

Can Jotform payment forms and PDF steps move to LimeSurvey?

No, not as payment collection. LimeSurvey is built for surveys and collects responses, so payment processing and the PDF generation tied to Jotform's payment forms need a separate tool. Plan for a payment provider integration or a different workflow engine, and confirm that the chosen tool meets your payment card and data handling obligations. Templates for invoices, receipts or registrations usually need to be rebuilt outside LimeSurvey and then linked from the survey.

What does the server for LimeSurvey need, and who pays for it?

LimeSurvey Community Edition is free to download and self-host, so the recurring costs are the server, database, storage, backups, monitoring and staff time for upgrades. The software requires PHP 8.1.29 or later with mbstring and PDO drivers, plus a supported database such as MySQL 8.0, PostgreSQL 14, MariaDB 10.3.38 or MSSQL 2019 or later. Your infrastructure team or a partner would be paid for setup and hardening, and your own staff for ongoing operations. Ask any quote to separate one-time build work from recurring support, and to show the hosting location of every component.

How DeployOpen helps you evaluate and move to self-hosted LimeSurvey

DeployOpen is a Chainscore Labs company that plans, implements, customizes, hardens, backs up, upgrades and documents self-hosted open-source platforms inside your own infrastructure. For Jotform vs LimeSurvey, we start by checking whether your forms are really surveys, then build and hand over a LimeSurvey instance you control.

How we scope

  • Inventory which Jotform forms are surveys and which are payment, PDF or intake forms
  • List question types, multilingual needs, quotas and statistical exports your teams rely on today
  • Agree the hosting location, database engine and PHP runtime in a written, fixed-scope plan

How we build

  • Install LimeSurvey on your own servers or cloud account, with the database and PHP versions it requires
  • Rebuild priority surveys, translations and quota logic, then test skip logic and exports
  • Configure plugins such as ExportR or ExportSTATAxml where your analysts need them, and test them

How we hand over

  • Document the architecture, backup routines, upgrade path and admin roles in a handover pack
  • Provide a test report covering survey logic, access control and export accuracy for your review
  • Walk your administrators through creating surveys, managing responses and applying upgrades

How we support

  • Offer ongoing support, upgrades and continuous testing as a retainer after handover
  • Track LimeSurvey release and end-of-support dates so your upgrades stay on supported lines
  • Review backups and restore tests on a schedule agreed in your written support scope

Sources and further reading

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.