ArcMap retirement: migration options without losing the workflow
Plan after ArcMap’s March 1, 2026 retirement: inventory MXD, data and scripts, compare QGIS with ArcGIS Pro, and control coexistence.
Editorial review: 2026-09-23
ArcGIS Desktop, including ArcMap, retired on March 1, 2026. This is a lifecycle event for those products, not the retirement of ArcGIS Pro, ArcGIS Online or ArcGIS Enterprise. It does not mean existing installations suddenly stop opening files. Esri explains the retirement in A farewell to ArcMap.
The practical decision is which supported workflow should replace each dependency: ArcGIS Pro, QGIS, or a combination. Begin with outputs and operations, because replacing the application icon does not preserve a map series, a Python tool or geodatabase behavior.
1. Preserve the working reference
Before converting anything, preserve a copy of the map documents, source data, styles, scripts and generated outputs. Record the application version, coordinate system, external services and environment that produced the reference. Keep a PDF of an important layout and a small, known input/output pair for each recurring analysis.
Do not assume the current MXD contains all its data. Network paths, joined tables, fonts and database connections may live elsewhere. Open the project from a fresh workstation or user profile during assessment to reveal hidden dependencies. Use a controlled copy so a conversion cannot modify the only working dataset.
2. Inventory by behavior
| Dependency | ArcGIS Pro route | Open GIS route to investigate |
|---|---|---|
| MXD map and layout | Import, inspect differences and repair references | Rebuild QGIS project and layout from reference outputs |
| Shapefile or ordinary feature table | Validate fields, geometry and CRS | GeoPackage or PostGIS with explicit keys and types |
| Geodatabase rules and relationships | Check supported behavior and upgrades | Recreate constraints/forms/relations deliberately |
| Python 2 / ArcPy automation | Port environment and affected APIs | Rewrite required operations with PyQGIS, GDAL or SQL |
| ModelBuilder process | Check tools, parameters and compatibility | Implement equivalent processing graph or script |
| ArcObjects/.NET customization | Redesign against the Pro SDK where appropriate | Redesign application/plugin behavior |
| Specialist network or parcel workflow | Evaluate supported Esri migration path | Retain until a demonstrably equivalent workflow exists |
| Published services | Identify client and server dependencies separately | Test protocol and application changes independently |
Esri documents imports, unsupported or upgraded data types and Python changes in Migrate existing work. Import is not proof of perfect equivalence. For example, a different rendering engine can alter appearance, and data upgrades may affect backward compatibility. Inspect the exact version and dataset before modifying it.
3. Run two contrasting pilots
Select one frequent, portable task and one difficult dependency. A useful first task is loading an inventory, filtering records, joining a table and producing a departmental map. The second might involve a relationship, a model or a specialist editing operation. This avoids drawing a platform-wide conclusion from the easiest project.
For each pilot, name the original input, operation, expected output, tolerance and user. Compare feature counts and business identifiers, not only screenshot similarity. For geometry calculations, use the same coordinate transformation and method; differences in area can come from projection or ellipsoidal settings rather than broken software.
Use the QGIS introductory project for the desktop sequence and the reproducible lab for synthetic data and HTTP publication. Passing that lab is educational evidence. It does not validate your organization's geodatabase or production server.
4. Treat scripts as small software migrations
Run scripts against a fixed fixture and record output schema, values and failures before translating them. Separate I/O, spatial transformation and report generation. That makes it possible to retain one proprietary step while moving portable operations.
ArcGIS Pro uses Python 3 and arcpy.mp for map/project automation in place of arcpy.mapping. Changes also affect project objects and exports; see Esri's map automation migration guide. A syntax update does not establish equivalent behavior. For a PyQGIS rewrite, identify algorithms and parameters explicitly using the developer cookbook.
Check scheduled execution without an interactive desktop session. Confirm paths, database credentials, locale, date handling and failure notification. A tool that works only for its author during an interactive session has not replaced the scheduled workflow.
5. Design coexistence around one editing authority
A mixed environment is reasonable when different workflows mature at different speeds. Assign one authoritative editor for each dataset or partition. Publish a read-only derivative to the other environment when that meets the need. Record refresh frequency and how a user recognizes stale information.
Avoid independent, editable exports that must later be reconciled manually without a rule. A simple shared identifier and explicit update boundary are often more important than the choice of desktop client. If both clients must edit concurrently, test permissions, locks, constraint errors and recovery with the real database design.
6. Budget and retire in a controlled sequence
Compare training, scripts, layouts, data conversion, application changes, support and retained subscriptions. Do not include a historical purchase as a future saving. Align cutover with reporting obligations and renewal dates, and preserve a recovery path for work created during coexistence.
A workflow is ready when another user completes the task, the result meets its agreed tolerance, the responsible team can restore it and dependent consumers have been checked. A converted file count is insufficient. Record remaining dependencies with an owner and review date so temporary coexistence does not become an invisible permanent cost.
Use the cost model to compare the three routes, then the phased plan to sequence them. The outcome can legitimately retain specialized Esri capabilities while QGIS, PostGIS and open services take over portable workloads.