{
  "id": "mergin-maps-vs-arcgis-survey123",
  "ids": [
    "mergin-maps",
    "arcgis-survey123"
  ],
  "title": "Mergin Maps vs ArcGIS Survey123: mobile field maps and geospatial data collection",
  "heading": "Mergin Maps vs ArcGIS Survey123",
  "kicker": "GIS and analysis software comparison",
  "deck": "Mergin Maps fits collaborative QGIS-oriented field projects. Survey123 fits structured forms and geographic survey records in ArcGIS. Compare survey complexity, map editing, offline sync and the destination data model before changing the collection workflow.",
  "description": "Compare Mergin Maps vs ArcGIS Survey123 for mobile field maps and geospatial data collection.",
  "answerHeading": "Which option fits the requirement?",
  "answer": "Mergin Maps fits collaborative QGIS-oriented field projects. Survey123 fits structured forms and geographic survey records in ArcGIS. Compare survey complexity, map editing, offline sync and the destination data model before changing the collection workflow.",
  "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 Mergin Maps vs ArcGIS Survey123.",
  "type": "workflow-buying",
  "sharedBuyingNeed": "Evaluate alternative approaches to mobile field maps and geospatial data collection.",
  "rows": [
    [
      "Primary collection model",
      "Collaborative mobile geospatial projects",
      "Structured form-based collection"
    ],
    [
      "Application environment",
      "Field app and project synchronisation platform",
      "ArcGIS survey apps and form design"
    ],
    [
      "Configuration",
      "QGIS-oriented projects and data workflows",
      "Survey forms, rules and geographic questions"
    ],
    [
      "Offline boundary",
      "Test offline collection and subsequent project sync",
      "Confirm the selected form and device offline behaviour"
    ],
    [
      "Data handover",
      "Team project synchronisation and supported data workflows",
      "Survey records in the ArcGIS environment"
    ],
    [
      "Evaluation focus",
      "Team roles, sync conflicts and project operations",
      "Question logic, attachments, validation and data export"
    ],
    [
      "Cost components",
      "Selected plan or deployment, storage, devices and support",
      "Eligible ArcGIS access, services, 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 Mergin Maps, configure a copied task with a location, required attributes and an attachment.",
      "right": "With ArcGIS Survey123, 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 Mergin Maps, create authorised sample records offline and reconnect through a test workflow.",
      "right": "With ArcGIS Survey123, 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 Mergin Maps, have two test users update a copied feature and review the result.",
      "right": "With ArcGIS Survey123, 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 Mergin Maps, export or reopen collected records in the intended destination.",
      "right": "With ArcGIS Survey123, 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": [
        "Mergin Maps fits collaborative QGIS-oriented field projects. Survey123 fits structured forms and geographic survey records in ArcGIS. Compare survey complexity, map editing, offline sync and the destination data model before changing the collection workflow.",
        "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://merginmaps.com/",
          "label": "Mergin Maps product information"
        },
        {
          "url": "https://www.esri.com/en-us/arcgis/products/arcgis-survey123/overview",
          "label": "ArcGIS Survey123 product information"
        }
      ]
    },
    {
      "id": "cost-and-migration",
      "navLabel": "Costs & migration",
      "title": "Cost and migration planning",
      "paragraphs": [
        "For Mergin Maps, include selected plan or deployment, storage, devices and support. For ArcGIS Survey123, include eligible ArcGIS access, services, 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 Mergin Maps and ArcGIS Survey123?",
      "answer": "Mergin Maps fits collaborative QGIS-oriented field projects. Survey123 fits structured forms and geographic survey records in ArcGIS. Compare survey complexity, map editing, offline sync and the destination data model before changing the collection workflow."
    },
    {
      "question": "Which costs belong in the comparison?",
      "answer": "For Mergin Maps, include selected plan or deployment, storage, devices and support. For ArcGIS Survey123, include eligible ArcGIS access, services, 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://merginmaps.com/",
      "facts": "Official product scope, deployment and integration context used for mobile field maps and geospatial data collection."
    },
    {
      "url": "https://www.esri.com/en-us/arcgis/products/arcgis-survey123/overview",
      "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"
    }
  ]
}