{
  "id": "arcgis-field-maps-vs-mergin-maps",
  "ids": [
    "arcgis-field-maps",
    "mergin-maps"
  ],
  "title": "ArcGIS Field Maps vs Mergin Maps: mobile field maps and geospatial data collection",
  "heading": "ArcGIS Field Maps vs Mergin Maps",
  "kicker": "GIS and analysis software comparison",
  "deck": "ArcGIS Field Maps connects field activity to an ArcGIS environment. Mergin Maps combines mobile GIS projects with collaborative synchronisation. Choose around your desktop GIS, team permissions, offline collection and the actual hosting or subscription configuration.",
  "description": "Compare ArcGIS Field Maps vs Mergin Maps for mobile field maps and geospatial data collection.",
  "answerHeading": "Which option fits the requirement?",
  "answer": "ArcGIS Field Maps connects field activity to an ArcGIS environment. Mergin Maps combines mobile GIS projects with collaborative synchronisation. Choose around your desktop GIS, team permissions, offline collection and the actual hosting or subscription configuration.",
  "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 ArcGIS Field Maps vs Mergin Maps.",
  "type": "workflow-buying",
  "sharedBuyingNeed": "Evaluate alternative approaches to mobile field maps and geospatial data collection.",
  "rows": [
    [
      "Primary collection model",
      "Map-centred field work",
      "Collaborative mobile geospatial projects"
    ],
    [
      "Application environment",
      "ArcGIS mobile app and map configuration",
      "Field app and project synchronisation platform"
    ],
    [
      "Configuration",
      "Maps, forms and field workflows",
      "QGIS-oriented projects and data workflows"
    ],
    [
      "Offline boundary",
      "Confirm offline map and service requirements",
      "Test offline collection and subsequent project sync"
    ],
    [
      "Data handover",
      "Connected ArcGIS layers and organisation access",
      "Team project synchronisation and supported data workflows"
    ],
    [
      "Evaluation focus",
      "Map editing, offline use and field configuration",
      "Team roles, sync conflicts and project operations"
    ],
    [
      "Cost components",
      "Eligible user type, services, devices and support",
      "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 ArcGIS Field Maps, 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 ArcGIS Field Maps, 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 ArcGIS Field Maps, 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 ArcGIS Field Maps, 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": [
        "ArcGIS Field Maps connects field activity to an ArcGIS environment. Mergin Maps combines mobile GIS projects with collaborative synchronisation. Choose around your desktop GIS, team permissions, offline collection and the actual hosting or subscription configuration.",
        "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://www.esri.com/en-us/arcgis/products/arcgis-field-maps/overview",
          "label": "ArcGIS Field Maps 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 ArcGIS Field Maps, include eligible user type, services, devices and support. 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 ArcGIS Field Maps and Mergin Maps?",
      "answer": "ArcGIS Field Maps connects field activity to an ArcGIS environment. Mergin Maps combines mobile GIS projects with collaborative synchronisation. Choose around your desktop GIS, team permissions, offline collection and the actual hosting or subscription configuration."
    },
    {
      "question": "Which costs belong in the comparison?",
      "answer": "For ArcGIS Field Maps, include eligible user type, services, devices and support. 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://www.esri.com/en-us/arcgis/products/arcgis-field-maps/overview",
      "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"
    }
  ]
}