ArcMap officially retired on March 1, 2026. For local governments still using ArcMap, the next step is a structured ArcMap migration plan that addresses the maps, data, scripts, integrations, extensions, and business processes the software supports.
Esri is no longer planning future ArcMap releases, and software updates, patches, and hot fixes are no longer available. ArcMap-based extensions, ArcCatalog, ArcScene, ArcGlobe, ArcReader, and ArcGIS Engine are also included in the retirement. Review Esri’s ArcGIS Desktop retirement notice.
ArcMap may continue to open in some environments, particularly where an organization holds perpetual licences. Continued operation should not be confused with continued support. Compatibility issues, security concerns, unsupported third-party components, staff turnover, and changes to connected systems will make legacy workflows increasingly difficult to maintain.
A successful transition requires more than installing ArcGIS Pro. Local governments should use ArcMap retirement as an opportunity to assess how GIS work is completed, remove unnecessary processes, document institutional knowledge, and modernize the workflows that support public services.
Why ArcMap Migration Requires a Workflow Assessment
Many ArcMap environments have developed over decades. They often include hundreds of map documents, personal folders, shared drives, Python scripts, custom toolbars, database connections, printed map templates, and processes known only to one or two employees.
Moving every file into ArcGIS Pro without reviewing its purpose can reproduce the same complexity in a new platform.
A better ArcMap migration starts with business questions:
- Which workflows support essential government services?
- Who uses each workflow, and how frequently?
- What information does the workflow produce?
- Which systems supply or receive the data?
- Where are staff completing repetitive manual steps?
- Which maps, tools, and reports are still required?
- Which legacy items can be retired?
- Could a web, mobile, or automated workflow serve users more effectively?
The goal is to preserve required business outcomes while improving how the work is completed. A structured GIS Strategic Enterprise Planning assessment can help local governments document their current environment, identify gaps, and create a practical modernization roadmap.
1. Inventory Your ArcMap Environment
Begin by identifying everything that depends on ArcMap.
The inventory should include:
- MXD files
- Map templates and layouts
- Layer files and style files
- Python scripts and script tools
- ModelBuilder models
- ArcObjects applications
- Custom add-ins and toolbars
- Third-party extensions
- File and enterprise geodatabases
- Personal geodatabases
- Database connections
- Published map and feature services
- Scheduled tasks
- Exported reports and map books
- Connections to CAMA, tax, permitting, public safety, document-management, and other business systems
For each item, record its owner, users, purpose, frequency of use, data sources, outputs, dependencies, and operational importance.
Do not assume that every file deserves to be migrated. Duplicate, outdated, test, and abandoned MXDs should be archived or removed from the active migration queue. This reduces migration effort and gives staff a cleaner ArcGIS Pro environment.
The inventory should also identify undocumented workflows. If only one employee knows how a tax map, assessment layer, or monthly report is produced, document the process before that knowledge is lost.
Organizations that need additional capacity can use Sidwell’s GIS services and workflow analysis to document their current processes, dependencies, data sources, and operational requirements.
2. Assess and Prioritize Your MXD Files
ArcGIS Pro can import ArcMap map documents through its Import Map function. Layouts, definition queries, data frames, and many other map elements can be carried into an ArcGIS Pro project. Each ArcMap data frame becomes a separate map within the project.
Imported maps should still be reviewed. ArcGIS Pro uses a different drawing engine, so labels, symbols, transparency, fonts, layouts, and other visual elements may display differently. The imported map also does not remain connected to the original MXD.
Esri recommends reviewing imported content and validating the result. See Esri’s guidance for migrating existing ArcMap work.
Classify MXDs into three groups:
Priority 1: Mission-critical
These maps support essential or time-sensitive operations, such as:
- Parcel maintenance
- Assessment and taxation
- Addressing and emergency response
- Elections
- Planning and permitting
- Public works operations
- Statutory or regulatory map production
- Public property information
Migrate and test these workflows first.
Priority 2: Frequently used
These maps support recurring internal analysis, reporting, field operations, departmental requests, and public communication. Migrate them after the mission-critical workflows are stable.
Priority 3: Infrequent, duplicate, or obsolete
Archive these files with appropriate documentation. Avoid spending project resources rebuilding maps that no longer deliver business value.
For each migrated MXD, test data connections, joins, relates, queries, labels, symbology, layouts, map series, exports, and printing. A map that opens successfully has not necessarily passed operational testing.
Sidwell’s ArcGIS Pro migration services cover environment analysis, installation, licensing, data migration, scripts, layouts, workflows, and staff preparation.
3. Review Python Scripts and Models
ArcMap uses Python 2.7, while ArcGIS Pro uses Python 3. Existing scripts may require modification before they will run in the ArcGIS Pro environment.
The arcpy.mapping module used for automating maps and layouts in ArcMap has been replaced by arcpy.mp. Differences in syntax, libraries, string handling, encoding, and tool availability can also affect existing scripts.
Esri provides the Analyze Tools For Pro utility to identify issues that may prevent Python scripts and script-based geoprocessing tools from running in ArcGIS Pro. Review Esri’s Python migration guidance.
For every script or model, determine:
- What business process does it support?
- Is it still being used?
- How frequently does it run?
- Is it launched manually or through a scheduled task?
- Which data, folders, databases, and credentials does it require?
- Does it depend on a retired tool or unsupported library?
- Who owns and supports the code?
- What happens if the automation fails?
Some scripts should be converted. Others should be rewritten, replaced with an ArcGIS Pro geoprocessing tool, moved into ArcGIS Enterprise, or retired.
Treat automation testing as a business validation exercise. Compare the ArcGIS Pro output against an approved ArcMap result and document the expected outcome.
4. Evaluate Extensions and Custom Tools
ArcMap add-ins and ArcObjects applications do not automatically run in ArcGIS Pro. Esri states that application-level .NET add-ins written for ArcMap will not run in ArcGIS Pro. ArcObjects-based tools may need to be rebuilt using the ArcGIS Pro SDK for .NET, replaced with standard ArcGIS Pro functionality, or retired.
Create an extension and customization register that identifies:
- Product or tool name
- Vendor or developer
- Current version
- Business purpose
- Number of users
- Licence and maintenance status
- ArcGIS Pro compatibility
- Replacement option
- Required redevelopment
- Testing owner
- Target retirement date
Contact third-party vendors early. Confirm whether an ArcGIS Pro version exists, whether it requires a separate purchase, and whether the new version provides equivalent functionality.
Custom development should be justified by a clear operational need. If ArcGIS Pro, Parcel Fabric, Workflow Manager, Experience Builder, Field Maps, or another supported application can replace a custom tool, using supported functionality may reduce long-term maintenance risk.
Local governments should also confirm that their land-records tools support ArcGIS Pro. Sidwell’s Parcel Administrator supports parcel-number management, historical data creation, and integration with tax and CAMA systems.
5. Test Data and System Integrations
Local government GIS rarely operates independently. ArcMap workflows may exchange information with:
- CAMA and tax systems
- Land-records systems
- Permitting platforms
- Document-management systems
- Computer-aided dispatch
- Asset-management systems
- Work-order platforms
- Enterprise databases
- Public GIS applications
- Imaging and oblique imagery platforms
- Scheduled file transfers
- Web services and APIs
Document how data enters and leaves each workflow. Confirm database drivers, authentication methods, service URLs, data formats, field mappings, scheduled processes, and security requirements.
Most file and enterprise geodatabases can be used in ArcGIS Pro, but some data models require conversion or upgrading. For example, personal geodatabases are not supported in ArcGIS Pro. Legacy parcel fabrics, geometric networks, annotation, dimension feature classes, and raster catalogs may also require specific migration decisions.
Create backups before upgrading shared data. Some ArcGIS Pro capabilities, including certain geodatabase functionality, can make datasets unavailable to ArcMap. Plan this change carefully when ArcMap and ArcGIS Pro will operate in parallel.
Integration testing should involve both GIS and the departments that rely on the resulting information. Technical connectivity alone does not prove that the end-to-end workflow is functioning correctly.
6. Confirm Licensing, Infrastructure, and Governance
ArcGIS Pro licensing should be planned according to how employees work.
Named User licensing is the default model. ArcGIS Pro access and licence level are associated with a user’s ArcGIS Online or ArcGIS Enterprise account. Current user types provide different ArcGIS Pro licence levels:
- Creator includes ArcGIS Pro Basic.
- Professional includes ArcGIS Pro Standard.
- Professional Plus includes ArcGIS Pro Advanced and several extensions.
Single Use and legacy Concurrent Use arrangements may still exist in certain ArcGIS Desktop deployments, but Concurrent Use licensing was deprecated in July 2025. Local governments should review their long-term licensing direction instead of carrying forward a model that may no longer fit the organization. Review the current ArcGIS Pro licensing options.
The technical review should also cover:
- Workstation requirements
- Graphics capability
- Operating-system compatibility
- Virtual desktop environments
- Network performance
- Storage capacity
- ArcGIS Online or ArcGIS Enterprise access
- Identity management and single sign-on
- Extension assignments
- Offline access requirements
- Software-update procedures
- Project, template, and naming standards
Establish governance for ArcGIS Pro projects, shared resources, Python environments, add-ins, templates, and published content. Without standards, the new environment can quickly develop the same inconsistencies found in the old one.
7. Train Staff and Use a Phased Migration Roadmap
ArcGIS Pro uses a ribbon-based interface, project files, panes, multiple maps and layouts, and different editing and sharing patterns. Experienced ArcMap users still need structured training and time to adapt.
Training should be role-based and connected to real work.
An assessor or parcel editor needs different training from a GIS analyst, public works technician, application administrator, or employee who only prints maps. Generic software demonstrations rarely provide enough preparation for operational change.
A practical training plan should include:
- ArcGIS Pro navigation and project structure
- Data connections and catalog management
- Editing and quality-control procedures
- Symbology, labelling, and layouts
- Geoprocessing
- Map series and exports
- Python and ModelBuilder, where applicable
- Sharing to ArcGIS Online or ArcGIS Enterprise
- Department-specific exercises
- Updated standard operating procedures
- Access to coaching after deployment
Use a phased roadmap rather than a single conversion date.
Phase 1: Discover
Inventory the environment, interview users, document workflows, identify dependencies, and confirm business priorities.
Phase 2: Design
Define the ArcGIS Pro environment, licensing model, project standards, data architecture, integration approach, and training plan.
Phase 3: Pilot
Select a representative workflow with manageable risk. Migrate it, test it with real users, document what changes, and refine the migration process.
Phase 4: Migrate
Move workflows in priority order. Require technical and business-owner approval before declaring each workflow complete.
Phase 5: Transition
Set an internal deadline for ending routine ArcMap use. Maintain a documented exception process for any remaining legacy dependency.
Phase 6: Optimize
Review performance, staff feedback, support requests, and opportunities to use web, mobile, automation, and enterprise capabilities.
What Local Governments Should Do Now
If ArcMap remains part of daily operations, take these immediate actions:
- Assign an executive sponsor and migration lead.
- Inventory MXDs, scripts, extensions, integrations, and data.
- Identify the workflows that cannot be interrupted.
- Confirm ArcGIS Pro licensing and workstation readiness.
- Select one representative workflow for a pilot.
- Develop role-based training.
- Establish a phased schedule for ending routine ArcMap use.
The highest-risk approach is allowing ArcMap to remain in production without a documented migration plan. The software may continue to open, but the surrounding environment will keep changing.
Turn ArcMap Retirement Into a Modernization Opportunity
ArcMap migration gives local governments a timely reason to evaluate how GIS supports land records, assessments, public works, public safety, planning, and public access.
The strongest migrations preserve the organization’s essential knowledge while removing redundant maps, fragile automation, outdated customizations, and unnecessary manual steps. They also create a foundation for modern parcel management, web GIS, mobile operations, system integration, and enterprise collaboration.
Sidwell helps local governments assess existing GIS workflows, migrate ArcMap environments, implement ArcGIS Pro, modernize Parcel Fabric, update integrations, and prepare staff for long-term success.
Sidwell helps local governments assess existing workflows, migrate ArcMap environments, implement ArcGIS Pro, modernize Parcel Fabric, update integrations, and prepare staff for long-term success. Explore Sidwell’s ArcGIS Pro services or contact our team to discuss your ArcMap migration priorities.
Will existing Python scripts work in ArcGIS Pro?
ArcMap uses Python 2.7, while ArcGIS Pro uses Python 3. Some scripts may require minor updates, while scripts that rely on arcpy.mapping, unsupported tools, custom libraries, or legacy integrations may need significant changes. Each script should be assessed according to its business purpose and operational importance.
What should be migrated first?
Begin with workflows that support essential government operations, including parcel maintenance, assessment and taxation, addressing, emergency response, elections, planning, permitting, public works, and public property information. Frequently used internal workflows should follow. Duplicate, obsolete, and low-value items can be archived rather than migrated.
Does an ArcMap migration require Parcel Fabric changes?
Organizations using a legacy parcel fabric may need to migrate their parcel data to the ArcGIS Pro Parcel Fabric. This process can include data assessment, cleanup, schema configuration, workflow development, testing, and staff training. Learn more about Sidwell’s Parcel Fabric migration services.
How can Sidwell support an ArcMap migration?
Sidwell can assess the current GIS environment, identify workflow dependencies, configure ArcGIS Pro, migrate maps and data, update scripts, support Parcel Fabric modernization, test integrations, and train staff. Explore Sidwell’s ArcGIS Pro migration services to begin planning the transition.