mWater vs KoboToolbox

Short answer: These products overlap, but they are designed around different primary jobs. The right choice depends less on a feature checklist than on the data model, users, workflows, and operating environment you need to support.

KoboToolbox is a widely used form and data-collection platform, particularly in humanitarian and development work. mWater includes form-based data collection but extends further into persistent mapped registries, repeated monitoring, indicators, dashboards, assets, issues, and operational workflows.

At a glance

Requirement	mWater	KoboToolbox
Primary strength	Ongoing monitoring and management built around sites and assets	Rapid design and deployment of data-collection projects
Offline collection	Surveyor apps and web workflows with offline maps and cached records	KoboCollect on Android and offline-capable web forms
Longitudinal model	Surveys can attach to persistent sites, people, and assets over time	Projects primarily organize form submissions; linked-data designs require deliberate setup
Analysis and action	Maps, dashboards, indicators, approvals, assignments, issues, and workflows	Tables, reports, maps, exports, APIs, and connections to external analysis tools
Form standards	Visual designer, question libraries, imports, logic, validation, and multilingual forms	Visual Formbuilder plus strong XLSForm/ODK compatibility

Choose mWater when

You are not only running a survey: you must maintain a registry and return to the same water points, schools, health facilities, households, customers, or assets.
Managers need live dashboards, maps, indicators, data approvals, issue tracking, and work processes in the same environment.
Different organizations need to collaborate on shared records with controlled visibility and editing rights.
Your programme is expected to continue through many monitoring rounds rather than end after one dataset is delivered.

Choose KoboToolbox when

Your immediate need is to deploy a questionnaire quickly for an assessment, evaluation, registration, or emergency response.
Your team already works fluently with XLSForm or the ODK ecosystem.
Android enumerator collection through KoboCollect, or a respondent-facing web form, matches the field workflow.
You plan to export or connect submissions to separate GIS, business-intelligence, statistical, or case-management systems.

Migration and coexistence

Teams often start in KoboToolbox because it is fast to launch, then need a persistent registry and operational monitoring. mWater can import Kobo survey designs and historical data, and scheduled integrations can continue to pull Kobo submissions. Before migrating, decide how repeated submissions map to stable site identifiers, preserve choice codes and languages, test repeat groups and media, and retain the original submission IDs for traceability.

The practical decision

For a bounded survey, KoboToolbox may be the simpler answer. For a long-running programme in which data must describe real-world entities, accumulate history, drive dashboards, and trigger action, mWater usually reduces the number of separate systems required. If an organization already has reliable Kobo operations, integration may be lower risk than an immediate replacement.

Sources and verification

See KoboToolbox's official guides to data collection and the platform, plus mWater's guides to importing Kobo forms and importing Kobo data.