KoboToolbox alternatives in 2026.
When to switch, and what to switch to

If none of those is true, stay on Kobo. It is free for nonprofits, it is built on the same open standards as most of its rivals, and it does survey work very well.

Key takeaways

• Kobo changed in 2024. Its plan model now caps the free nonprofit Community plan at 5,000 submissions a month and 1 GB of file storage. Organisations that are not nonprofits now pay for every plan.
  • Photo-heavy surveys hit the storage cap before the submission cap. 5,000 submissions with one 500 KB photo each is about 2.5 GB.
  • XLSForm makes switching cheap. ODK, SurveyCTO, Ona and Survey123 all read XLSForm. CommCare, Avni and Zoho do not, so plan a rebuild for those.
  • The real question is often "form tool or system?" If you need one record per person, visit after visit, you are shopping for a beneficiary or case management system, not a better survey app.
  • At 200 enumerators, prices range from about US$130 to US$1,600 a month depending on the tool, before staff time.

Sound familiar? The baseline went well. Then the midline doubled the sample, someone added photo questions, and one morning enumerators could not submit.

Four changes since 2023 explain most of the "kobotoolbox alternatives" searches we see from partners:

1. The plan model. In May 2024 Kobo introduced Community, Professional, Teams and Enterprise plans. The free Community plan gives nonprofits 5,000 submissions a month, 1 GB of file storage, unlimited forms and unlimited data collectors. Kobo says it remains free for over 95% of users.
2. Paid plans for everyone else. The current pricing page lists a Starter plan at US$25 a month and charges US$99 a month for Community if you are not a nonprofit, government agency, UN body or educational institution. Social enterprises, CSR foundations registered as companies and research consultancies should check which category they fall into.
3. The end of the old humanitarian server deal. Kobo took over the former UN OCHA server on 1 September 2023. Legacy humanitarian users kept 25,000 submissions a month only until 1 March 2024. Older guides that say "the humanitarian server is unlimited" are out of date.
4. Hard stops in the field. In March 2026 a seed-distribution programme in Tanzania reported that new submissions were blocked at roughly 10,000 households, halfway to a 20,000-household target.

The other reasons are structural. Kobo stores data on its Global server (US) or EU server (Ireland), according to Kobo staff, with no India region on standard plans. Its dynamic data attachments let a follow-up form pull data from a baseline, but that is not case management with statuses and closures. And reporting beyond basic charts means exporting to Excel, Power BI or Looker Studio.

We say this to partners often: the cheapest migration is the one you don't do. Stay on Kobo if:

• You run cross-sectional surveys (baselines, endlines, needs assessments) rather than tracking individuals.
• You are a nonprofit under 5,000 submissions a month and can keep photos small (Kobo supports a max-pixels setting for images).
• Your M&E lead is comfortable with XLSForm and exports.
• US or EU hosting is acceptable to your board, funders and legal advisers.

In one disaster-response engagement we scoped, we put programme, volunteer and donor workflows in Zoho Creator but kept Kobo for the offline field-assessment step, because that is where Kobo was strongest. Hybrids like that are normal.

A few notes from delivery:

• ODK is the closest thing to "Kobo with more control". Kobo uses ODK's XLSForm and Enketo technology, and KoboCollect is a copy of ODK Collect, so most forms move with small edits. ODK Cloud's India region matters for Indian partners.
• SurveyCTO suits research teams and evaluators who need audit trails, back-checks and encryption. It is the priciest per submission. See the deep dive below.
• CommCare and Avni win when the job is following a person or household through a programme, offline, for years. Both need more setup than a survey tool.
• Google Forms is not a field tool: no signal, no submission.

For the broader field, including tools that are not Kobo competitors, read our round-up of the best offline data collection tools. For what a data collection app should do once it is live (IDs, validation, consent, dashboards), see our guide to choosing a data collection app for NGOs.

Kobo, ODK and SurveyCTO charge by submissions. CommCare charges by mobile user. Zoho Creator and Avni charge by user or hosting band. To compare them fairly, the table assumes each enumerator sends 100 submissions a month (about five a working day): 1,000, 5,000 and 20,000 submissions.

List prices from vendor pages, checked November 2026, before taxes, nonprofit discounts and implementation. Kobo's Professional price shows a monthly and an annual figure; ODK offers up to 20% off for yearly billing.

Two things the table hides. First, staff time is usually the larger cost: a self-hosted ODK server is free software but needs someone to patch it. Second, the cheapest row is not the cheapest system if your team still spends three days a month merging exports.

Because Kobo, ODK, SurveyCTO, Ona and Survey123 share the XLSForm standard, forms are rarely the hard part. You download the XLS from Kobo, adjust a handful of column names and functions, and redeploy. SurveyCTO's own guide to converting Kobo forms lists the changes: relevant becomes relevance, jr:choice-name() becomes choice-label(), language labels change format, and Kobo's xml-external lookups become pulldata() or server datasets.

The hard parts are elsewhere:

• Historical data. Export every project to CSV or XLSX with media before you cancel anything. Keep the Kobo _uuid column; it is your only link back to the original record.
• IDs. If your Kobo forms never generated a stable person or household ID, fix that before migrating, or you will import the same duplicates into the new tool.
• Rebuilds. Moving to CommCare, Avni or Zoho means rebuilding forms in their builders. Budget for it.

Many partners who ask us about Kobo alternatives are not describing a survey problem. They are describing a programme that has grown: three forms per participant, follow-ups every quarter, funders asking for disaggregated outcomes, and a programme manager who wants to see which villages are behind today.

That is the point at which you need a management information system, with a person or household as the core record. If you serve individuals, start with what a beneficiary management system should hold. If your work involves referrals, approvals or casework, read our guide to case management software for nonprofits. And before you design any of it, map your indicators from your Theory of Change to a data model.

Two patterns from our work:

• Keep Kobo as the collection layer. For an education programme in Sierra Leone, we kept offline collection in Kobo and built Looker Studio dashboards on top. It cost almost nothing in licences and worked because the programme needed reporting, not case tracking.
• Consolidate into one system. A carbon-project developer we scoped had hundreds of household-level volunteers, millions of records expected, and data spread across SurveyCTO, Kobo and Zoho Forms. The answer there was one database with case management and dashboards, with collection tools feeding it.

Moving to a system also raises the stakes on personal data. Household surveys often capture names, phone numbers, health details and children's information. India's DPDP Act does not force all data to stay in India, but it does require consent, purpose limits and security, and verifiable parental consent for children. Use our DPDP compliance checklist for NGOs when you choose where data will live.