Migrating from ArcMap to ArcGIS Pro: Concerns vs. Reality

ArcMap and ArcGIS Pro were developed to work in completely different environments and with very different data.  Most performance impacts are due to using under-resourced hardware for ArcGIS Pro functions.

The main challenge facing organisations is utilising a suitably resourced machine to operate ArcGIS Pro on.  Under resourced hardware results in poor performance including the infamous "spinning wheel" display whilst undertaking geoprocessing functions.

Below shows a comparison of required resources for each product, and further details can be found on the Esri website:-

If you are unsure if your PC will have sufficient specifications to run ArcGIS Pro adequately, Esri recommends using the "CanYouRunIT?" application to undertake the analysis.

In my experience, GIS users have always had to battle with ICT to get better performing PC's.  How many ArcMap users have had to write business cases to justify a higher performing "CAD Spec" PC?  Similarly, ArcGIS Pro users will need to justify a higher performing "Gaming Spec / Virtual Reality Spec" PC to meet the performance needs of this new technology.  With the right hardware, you will find ArcGIS Pro will fly and you won't be frustrated by the spinning wheel.

The testing we have done aligns with Esri's ArcGIS Pro product roadmap publication, with all core functions and tools migrated into ArcGIS Pro. While there are some unsupported "tools that are not available in ArcGIS Pro", most either offer like-for-like functionality or a new tool to achieve the same results as were available in ArcMap.

In our experience, chances are there will be a solution or tool to achieve the same outcome, it just may be different to how ArcMap did it.

Custom add-ins for ArcMap will not be compatible with ArcGIS Pro. To manage Add-ins in ArcGIS Pro, users will need to do things a little differently, by creating custom add-ins using the ArcGIS Pro SDK 2.7 for the Microsoft .NET Framework.

If you've developed custom geoprocessing tools using python there is a chance some may work, while others may not. Esri has included a geoprocessing tool called Analyze Tools for Pro which will determine whether or not your tool will function in ArcGIS Pro. ArcMap geoprocessing tools use the now deprecated Python 2 while ArcGIS Pro utilises Python 3.

We recommend rebuilding core python Add-ons in ArcGIS Pro and storing them in a shared Toolbox, which multiple ArcGIS Project files can access, as they are far more versatile than Map Documents.

By producing template Tasks in Projects that contain the required Toolboxes and Python Notebooks these projects can be Packaged and shared for user collaboration either as a file or within the Portal environment.

These are then searchable to the organisation via ArcGIS Enterprise and Tasks create standardised procedures for operating within a project.

Yes and No.

• If you use a basis geometric network like watercourses or rail lines, without complex functions like outage tracing, then YES this can be used by converting the Geometric Network to a Trace Network, which is administered by ArcGIS Pro.
• If you use a complex geometric network such as a utility, with complex functions like network outage calculations based on interactions with other assets like valves, then NO you cannot migrate to ArcGIS Pro.  You must migrate your geometric network data model to the Utility Network model, which is administered by ArcGIS Pro.

Unfortunately for our utility clients, the Trace Network solution is designed around simple linear networks and doesn't support complex network functions such as network isolation traces, which requires complex relationships between asset classes.

In the words of Chaucer, all good things must come to an end.

Most organisations have an IT policy that dictates they only use "supported products". After early 2026, ArcMap will no longer be supported, which means operating systems, database version and security patches will cease to be developed and released.

There are undoubtedly a few challenges in migrating from ArcMap to ArcGIS Pro, but I believe these are outweighed by the following opportunities:-

• GIS to the cloud - by migrating away from a LAN based system, Enterprise GIS can be deployed in your choice of cloud platform, without the need for costly desktop virtualisation such as Citrix
• Transition Desktop Users to thin client users- Gone are the days of non-GIS professionals (e.g. Planners, environmental scientists) trying to work out how to use Desktop GIS, chained to a desk.  Now data capture, data editing and data viewers can all be accessed through thin client device apps and webapps on almost any device, in whatever environment they are working in.
• Utility Network - ArcGIS Pro is the foundation administration tool for the Utility Network, which has some significant new functionality for managing, administering and operating assets.
• BIM - GIS Integration - The Digital Engineering and Geographic Information worlds are finally aligning, and whilst the BIM integration is still emerging in the Esri suite, there are some great tools already available to incorporate and publish 3D web services and 3D scenes
• Geoprocessing Traceability - ArcGIS Pro allows you to see your historical geoprocessing functions, so you have traceability of historical data processes, and allows users to re-run them as required
• New ways to Publish Services - ArcGIS Pro allows you to administer and publish your data in many new ways, to extend the thin client experience:-
  • Web Feature Layers
  • Web Tile Layers
  • Vector Tile Layers
  • Map Image Layer
  • Stand-alone Table
  • Web Scene Layer
  • Web Imagery Layer
  • Web Elevation Layer