{ "id": "qfield-vs-mergin-maps", "ids": [ "qfield", "mergin-maps" ], "title": "QField vs Mergin Maps: mobile field maps and geospatial data collection", "heading": "QField vs Mergin Maps", "kicker": "GIS and analysis software comparison", "deck": "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.", "description": "Compare QField vs Mergin Maps for mobile field maps and geospatial data collection.", "answerHeading": "Which option fits the requirement?", "answer": "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.", "checkedAt": "2026-10-25", "researchTag": "Deployment, compatibility and cost scope", "researchLimit": "Official product material reviewed. Acceptance checks are proposed exercises, not completed product trials, performance measurements or reliability guarantees.", "datasetDescription": "Seven technical differences and four proposed acceptance checks for QField vs Mergin Maps.", "type": "workflow-buying", "sharedBuyingNeed": "Evaluate alternative approaches to mobile field maps and geospatial data collection.", "rows": [ [ "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" ] ], "scenarios": [ { "name": "Collection pattern", "question": "Can the team configure a copied task with a location, required attributes and an attachment?", "left": "With QField, configure a copied task with a location, required attributes and an attachment.", "right": "With Mergin Maps, configure a copied task with a location, required attributes and an attachment.", "note": "The intended worker can complete the task without missing required information." }, { "name": "Offline recovery", "question": "Can the team create authorised sample records offline and reconnect through a test workflow?", "left": "With QField, create authorised sample records offline and reconnect through a test workflow.", "right": "With Mergin Maps, create authorised sample records offline and reconnect through a test workflow.", "note": "Records and attachments arrive without unexplained loss or duplication." }, { "name": "Shared editing", "question": "Can the team have two test users update a copied feature and review the result?", "left": "With QField, have two test users update a copied feature and review the result.", "right": "With Mergin Maps, have two test users update a copied feature and review the result.", "note": "The selected synchronisation and conflict process is understood." }, { "name": "Data handover", "question": "Can the team export or reopen collected records in the intended destination?", "left": "With QField, export or reopen collected records in the intended destination.", "right": "With Mergin Maps, export or reopen collected records in the intended destination.", "note": "Identifiers, coordinate context and attributes remain usable." } ], "exampleTable": { "caption": "Proposed checks using authorised copies of representative datasets, projects or models. Record software versions, required licences, dependencies, configuration and observed results.", "headers": [ "Requirement", "Proposed exercise", "Accept when" ], "rows": [ [ "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." ] ] }, "sections": [ { "id": "scope-and-architecture", "navLabel": "Architecture", "title": "Scope and architecture", "paragraphs": [ "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." ], "links": [ { "url": "https://qfield.org/", "label": "QField product information" }, { "url": "https://merginmaps.com/", "label": "Mergin Maps product information" } ] }, { "id": "cost-and-migration", "navLabel": "Costs & migration", "title": "Cost and migration planning", "paragraphs": [ "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." ] } ], "faqs": [ { "question": "How should we choose between QField and Mergin Maps?", "answer": "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." }, { "question": "Which costs belong in the comparison?", "answer": "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." }, { "question": "What should we validate before a production move?", "answer": "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." } ], "sources": [ { "url": "https://qfield.org/", "facts": "Official product scope, deployment and integration context used for mobile field maps and geospatial data collection." }, { "url": "https://merginmaps.com/", "facts": "Official product scope, deployment and integration context used for mobile field maps and geospatial data collection." } ], "relatedLinks": [ { "path": "/categories/gis-geospatial/", "title": "Gis Geospatial software" }, { "path": "/guides/software-buying-checklist/", "title": "Software buying checklist" } ] }