ArcGIS vs QGIS for cadastre and government: decision criteria
Compare ArcGIS Pro and QGIS across editing, analysis, automation, cadastre, networks and support, with a ten-task pilot and transparent total-cost criteria.
Editorial review: 2026-09-23
Compare ArcGIS Pro with QGIS for desktop tasks; evaluate servers, identity, fieldwork and applications separately. QGIS is not a single equivalent of the entire Esri platform. A team can use QGIS for analysis while retaining an ArcGIS service it still needs.
The test that changes the decision
For cadastre, choose a test batch containing relationships, domains, geometries and contractually required deliverables. Validate outputs using the receiving authority's procedure. Installing a plugin does not establish regulatory compliance or institutional approval. Do not base procurement on a historical regulation or an alleged certification without verifying its source.
Compare equivalent costs
Request the complete current cost and an alternative estimate with the same scope, availability and volume. Include retained licenses, infrastructure, support, internal hours, training, integration and coexistence. Do not use another country's public list price as a Colombia or LATAM quotation. Taxes, discounts and purchased entitlements can change the result.
When to retain and when to proceed
Retain the current component when an essential capability lacks a proven replacement or transition costs exceed expected benefits. Proceed when the pilot completes the task, an operating owner exists and TCO remains acceptable under a less favorable scenario. Data ownership and provider choice also matter, but express them as concrete requirements: exports, formats and recovery times.
This comparison is an editorial evaluation guide, not a parity certification or benchmark. Check versions, licensing and documentation when defining procurement scope.
ArcGIS Pro vs QGIS: a capability matrix for a real decision
Evaluate the exact ArcGIS Pro license and extensions already used, not an unspecified “ArcGIS” bundle. On the other side, name the QGIS release, providers, plugins and support arrangement. A function available in an optional plugin is not the same operational commitment as a tested, maintained departmental workflow.
| Workflow | ArcGIS side to inventory | QGIS/Open GIS approach to evaluate | Migration acceptance |
|---|---|---|---|
| Vector editing | Feature types, templates and rules | QGIS editing plus storage constraints | Same permitted edits and useful rejection messages |
| Raster analysis | Actual tools and required extensions | Processing providers and explicit algorithm parameters | Comparable outputs, units and no-data treatment |
| Spatial joins and overlays | Environment, tolerance and selected inputs | Equivalent operation with reviewed defaults | Reconciled keys, counts and geometry differences |
| Cartography | APRX maps, fonts, symbols and labels | QGIS styles and label expressions | Approved output at required scales |
| Print series | Layouts and map-series logic | Layouts and Atlas | Correct page count, order, extent and content |
| Database access | Supported database and geodatabase pattern | PostGIS connection and defined write path | Actual clients read and edit as intended |
| Domains and relations | Coded values, subtypes and relationship classes | Reference tables, constraints and QGIS relations | Codes and child records preserve meaning |
| Automation | ArcPy, ModelBuilder and schedules | PyQGIS, Processing, SQL or external scripts | Repeatable results and recoverable failures |
| Specialized cadastre | Parcel-specific objects and procedures | Explicit model and workflow implementation | Required deliverables accepted through actual validation |
| Utility networks | Network model, traces and operational rules | Separate network design or retained Esri component | Required traces and updates independently demonstrated |
| Multiuser versions | Reconcile/post and conflict procedures | Designed transactional or service workflow | Named conflict cases resolved without lost work |
| Web maps and identity | Portal items, groups and services | Separate publication and application architecture | Permissions and consumer contracts preserved |
| Offline fieldwork | Maps, forms, services and devices | QField project and chosen synchronization | Complete return including photos and conflicts |
| Support | Vendor/reseller scope and internal team | Commercial open-source support and internal team | Incident ownership and recovery window defined |
This is a planning matrix, not a binary product scorecard. Some rows are desktop tasks; others expose dependencies that prevent a desktop-only comparison from answering the whole procurement question.
What QGIS can replace first
Start with workflows whose inputs and outputs are already portable: thematic maps, spatial queries, data inspection, standard vector processing and recurring map exports. Their acceptance tests can be bounded and repeated with a small shared dataset. The QGIS pilot gives a complete first exercise; the style migration guide expands the delivered-map requirement.
Then evaluate repetitive analysis and data-management tasks. Their migration value may come from removing manual exports or making scripts easier to run, not just from removing a license. Measure the user's time with the same task before and after training. A faster expert on one product compared with an untrained beginner on the other is a training comparison, not a reliable software benchmark.
Keep an explicit list of retained components. A department might move map production to QGIS while retaining a specialized ArcGIS service and a few licenses. That can be a rational outcome if the reduced dependency and total cost are worthwhile. “Everything must migrate” can force expensive redevelopment of a low-volume specialist task.
Where apparent equivalence breaks down
A database polygon is not the same object as a fully configured parcel-management workflow. Likewise, a graph-routing algorithm does not automatically reproduce Utility Network's domain model, associations, validation and operational procedures. For specialized systems, compare the actual required behavior and data lifecycle. Do not claim equivalence because both systems display pipes or parcels.
Project files, automation and cartography are migration work. APRX, QGZ, ArcPy and PyQGIS are not interchangeable labels. A translated script may need new handling for field types, geometry validity, coordinate transformations and failure recovery. Use the automation guide to test one operation before estimating an entire library.
Licensing also requires specificity. Esri documents multiple ArcGIS Pro license levels and tool-dependent requirements. Identify the entitlement that enables each current workflow, including any extension. QGIS has no per-seat software license charge, but support, deployment, training, integration and specialized development still have costs. Neither “we pay for ArcGIS” nor “QGIS is free” gives a complete comparison.
A ten-task evaluation for a municipal team
Run the following proposed evaluation with synthetic or authorized data. Record software versions, hardware, input version and acceptance criteria before starting. It is a suggested test plan, not an already executed benchmark.
- Import the same dataset and reconcile business identifiers, null values and geometry types.
- Reproduce a map at the operational scale with approved labels, legend and attribution.
- Correct a deliberate attribute error while rejecting an invalid code.
- Correct a deliberate geometry error without changing unrelated boundaries.
- Join observations to assets and reconcile the resulting record count.
- Run a representative analysis with declared CRS, units and tolerance.
- Export the required exchange format and open it in the receiving tool.
- Create the required print or report output, including the difficult edge case.
- Repeat the task under a second analyst's account on another workstation.
- Restore the project and data from a copy after simulating a lost working directory.
For cadastre, add the receiving authority's actual validation procedure and required model version. For a utility, add the relevant network or field-return task. Generic map production cannot stand in for those domain tests.
Score mandatory capabilities before weighted preferences
First identify requirements that cannot fail: a required delivery format, an approved editing path, a critical network operation or recoverable field records. A high score for styling cannot compensate for failure of a mandatory task. For remaining preferences, a simple 0–3 scale is useful: unavailable, possible with unresolved work, passes with documented limitations, or passes as required.
Attach evidence to each score: output file, reproducible command, reviewed screenshot or recorded task result. Do not fill a matrix from memory or marketing descriptions. Record who performed the work and who accepted the output. Separate one-time configuration effort from recurring analyst effort.
Weight criteria before seeing the preferred product's score. Otherwise a team can unconsciously change the weighting to justify its initial preference. Repeat the economics with lower expected savings and higher support effort to see whether the decision remains reasonable.
Compare total cost with retained dependencies visible
Use actual invoices or current quotes for the existing scope. Count only costs the migration can really remove. A license already included in a broader agreement may have a different avoidable cost than its public list price. Retained server services, geocoding and identity integration may continue to incur costs after desktop migration.
For QGIS, include packaging, training, project conversion, script work, support, database operation and parallel running. Record hours and rates transparently. The TCO calculator accepts your assumptions and can show negative savings; the fictional municipal scenario illustrates arithmetic without presenting a client outcome.
Practical decisions by situation
| Situation | Sensible next move |
|---|---|
| Mostly maps and standard analysis | Run a QGIS desktop pilot with actual deliverables |
| Heavy ArcPy automation | Inventory scripts and port one representative pipeline |
| Specialized Esri data model | Preserve the operational component while testing alternatives |
| Growing number of occasional viewers | Evaluate web delivery and permissions separately from desktops |
| Small team with no operations capacity | Compare managed support offers as well as self-hosting |
| Mandated interoperability deliverables | Test exchange and receiving validation before selecting software |
Is QGIS suitable for government use?
Evaluate it through the actual requirements, information-security rules, delivery formats and support capacity of the organization. Neither open-source status nor a commercial brand automatically proves institutional suitability. Reproducible task results and a maintainable operating arrangement are stronger evidence.
Is a hybrid GIS a failed migration?
No. Retaining a component can be an intentional decision when it serves a proven dependency. Document its cost and integration boundary so coexistence remains visible. Reassess when requirements or alternatives change; do not describe a retained dependency as eliminated.
Specific sources: ArcGIS Pro license levels, Utility Network scope, and the QGIS user manual.
Sources and documentation
Next step
Continue in the Open GIS collection. For a specific project, use the total-cost calculator and request an assessment.