mWater vs ArcGIS Survey123

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.

ArcGIS Survey123 is Esri's form-centric data-collection application and connects directly to the wider ArcGIS platform. mWater is a monitoring and management platform that combines forms with persistent sites and assets, maps, indicators, dashboards, and operational workflows, with a strong focus on WASH and public-interest programmes.

At a glance

Requirement	mWater	ArcGIS Survey123
Primary strength	End-to-end monitoring programmes and shared registries	Smart forms inside the ArcGIS ecosystem
Form design	Visual survey designer with logic, validation, rosters, translations, and libraries	Web designer plus advanced XLSForm authoring in Survey123 Connect or Studio
Offline work	Offline surveys, maps, sites, assignments, and app workflows	Offline field app with maps, media, GPS/GNSS, signatures, and barcodes
GIS ecosystem	Built-in mapping, spatial layers, dashboards, imports, exports, and APIs	Direct integration with ArcGIS maps, feature services, dashboards, analysis, and enterprise tools
Access model	Free core platform with unlimited users; optional paid services	Requires an ArcGIS organization for authoring and non-public response workflows; licences and some Online operations have associated costs

Choose mWater when

Your programme needs a WASH-ready registry of facilities, water points, systems, customers, or infrastructure, not only form submissions.
You need repeat monitoring, indicators, data approvals, issue tracking, assignments, and workflows without assembling several ArcGIS products.
Large numbers of government, NGO, utility, or community users must participate without per-user charges for the core platform.
Your GIS needs are substantial but serve a broader monitoring and management process.

Choose ArcGIS Survey123 when

Your organization already standardizes on ArcGIS Online or ArcGIS Enterprise and has licences, administrators, feature services, and governance in place.
Collected data must immediately participate in ArcGIS web maps, geodatabases, spatial analysis, Experience Builder apps, or other Esri workflows.
You require Esri's field hardware integrations, geospatial ecosystem, or an advanced XLSForm workflow closely tied to feature layers.
The survey is one component of a larger enterprise GIS architecture.

Important differences in programme design

Survey123 is intentionally form-centric. The ArcGIS platform can supply the surrounding data model, maps, dashboards, automation, and apps, but teams must design and govern those pieces. mWater supplies more of the monitoring pattern directly: a site or asset persists, surveys accumulate against it, and programme users can analyze or act on the history.

Can they work together?

Yes. An ArcGIS system can remain authoritative for enterprise spatial layers while mWater manages WASH monitoring and field operations. Data can move through APIs, feature-service exports, scheduled files, or integration tooling. Preserve stable IDs and coordinate reference information, define which system may edit geometry, and avoid allowing two systems to become competing masters of the same feature.

Sources and verification

See the official Survey123 overview and the mWater platform overview. Confirm current ArcGIS user types, credits, and deployment terms with Esri or your distributor.