QField vs Mergin Maps
QField and Mergin Maps both support QGIS-oriented mobile work. Compare project compatibility, the selected sync service, team roles and offline conflict handling. Scope the complete deployment rather than equating an open-source app with a fully operated team service.
Which option fits the requirement?
QField and Mergin Maps both support QGIS-oriented mobile work. Compare project compatibility, the selected sync service, team roles and offline conflict handling. Scope the complete deployment rather than equating an open-source app with a fully operated team service.
Seven differences that change the shortlist
| Buying question | QField | Mergin Maps |
|---|---|---|
| Primary collection model | QGIS project-based field work | Collaborative mobile geospatial projects |
| Application environment | Open-source mobile GIS app | Field app and project synchronisation platform |
| Configuration | Prepared QGIS project and layers | QGIS-oriented projects and data workflows |
| Offline boundary | Test project packaging and synchronisation choices | Test offline collection and subsequent project sync |
| Data handover | QGIS-oriented data and optional connected services | Team project synchronisation and supported data workflows |
| Evaluation focus | Project compatibility, form behaviour and sync setup | Team roles, sync conflicts and project operations |
| Cost components | Devices, deployment, support and optional hosting | Selected plan or deployment, storage, devices and support |
Four worked buying briefs
These are hypothetical scenarios with explicit assumptions. They do not establish equal capabilities, measured usability or a negotiated price.
| Requirement | Proposed exercise | Accept when |
|---|---|---|
| Collection pattern | Configure a copied task with a location, required attributes and an attachment. | The intended worker can complete the task without missing required information. |
| Offline recovery | Create authorised sample records offline and reconnect through a test workflow. | Records and attachments arrive without unexplained loss or duplication. |
| Shared editing | Have two test users update a copied feature and review the result. | The selected synchronisation and conflict process is understood. |
| Data handover | Export or reopen collected records in the intended destination. | Identifiers, coordinate context and attributes remain usable. |
Collection pattern
Can the team configure a copied task with a location, required attributes and an attachment?
QField: With QField, configure a copied task with a location, required attributes and an attachment.
Mergin Maps: With Mergin Maps, configure a copied task with a location, required attributes and an attachment.
The intended worker can complete the task without missing required information.
Offline recovery
Can the team create authorised sample records offline and reconnect through a test workflow?
QField: With QField, create authorised sample records offline and reconnect through a test workflow.
Mergin Maps: With Mergin Maps, create authorised sample records offline and reconnect through a test workflow.
Records and attachments arrive without unexplained loss or duplication.
Shared editing
Can the team have two test users update a copied feature and review the result?
QField: With QField, have two test users update a copied feature and review the result.
Mergin Maps: With Mergin Maps, have two test users update a copied feature and review the result.
The selected synchronisation and conflict process is understood.
Data handover
Can the team export or reopen collected records in the intended destination?
QField: With QField, export or reopen collected records in the intended destination.
Mergin Maps: With Mergin Maps, export or reopen collected records in the intended destination.
Identifiers, coordinate context and attributes remain usable.
Scope and architecture
QField and Mergin Maps both support QGIS-oriented mobile work. Compare project compatibility, the selected sync service, team roles and offline conflict handling. Scope the complete deployment rather than equating an open-source app with a fully operated team service.
Map editing, structured surveys and rapid observations are different collection patterns. Confirm devices, positioning requirements, attachments, offline packages and sync conflict handling. A mobile app does not itself establish location accuracy or permission to collect a dataset.
QField product information ↗ · Mergin Maps product information ↗
Cost and migration planning
For QField, include devices, deployment, support and optional hosting. For Mergin Maps, include selected plan or deployment, storage, devices and support. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration.
Use test devices and authorised sample data. Create records offline, reconnect, review conflicts and verify attachments and identifiers in the destination system. Document collection permissions, device support and the handling of sensitive location information.
Questions before you choose
How should we choose between QField and Mergin Maps?
QField and Mergin Maps both support QGIS-oriented mobile work. Compare project compatibility, the selected sync service, team roles and offline conflict handling. Scope the complete deployment rather than equating an open-source app with a fully operated team service.
Which costs belong in the comparison?
For QField, include devices, deployment, support and optional hosting. For Mergin Maps, include selected plan or deployment, storage, devices and support. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration.
What should we validate before a production move?
Use test devices and authorised sample data. Create records offline, reconnect, review conflicts and verify attachments and identifiers in the destination system. Document collection permissions, device support and the handling of sensitive location information.
Turn the comparison into your own evaluation
Use the same criteria and priorities for both products, keep unknowns unassessed and record the plan and evidence behind your ratings.
Build a QField vs Mergin Maps scorecard →Keep the assumptions with the figures
Use the date, billing cycle, units and limits with each example. Check current account terms before purchasing. Unverified prices and model costs stay unpriced.
Download the buying examples as JSON ↓Share the comparison
Use these examples when discussing the shortlist with your team.