Question: Are there compatibility issues editing data in an enterprise geodatabase using both ArcGIS Desktop 10.8.1 and ArcGIS Pro 3.x? Can we use both software concurrently?
Background: As with many of us, my organization is using both ArcMap (10.8.1) and ArcGIS Pro (2.9). Our Enterprise GIS is at 10.9.1. After reading about the changes in ArcGIS Pro 3.x, we have been hesitant to upgrade beyond 2.9. Some of our users are effectively stuck with ArcMap for now (waiting on 3rd party add-ons to upgrade). We need to maintain functionality of being able to edit and work with enterprise geodatabases from both ArcMap and ArcGIS Pro. However, there are also some business cases that could benefit from the upgrade to ArcGIS Pro 3.x. So... we are sort of in a pickle at the moment.
Any and all help and advice would be greatly appreciated!
Solved! Go to Solution.
@Geodesy Editing of simple features should not cause any issues.
Refer to Client and geodatabase compatibility
Per this compatibility matrix, you should keep the geodatabase (SDE) at version 10.8.1.x to remain compatible with both ArcMap 10.8.1 and ArcGIS Pro 2.6. Note that ArcGIS Enterprise 10.9.1 is the last (most compatible) version with ArcMap 10.8.2 (last release). Starting at ArcGIS 11.0, many ArcMap dependent features are deprecated.
Removal of ArcMap-based runtime from ArcGIS Enterprise
Also, note that the compatibility matrix suggests staying at ArcGIS Pro 2.9 (if continuing to use ArcMap). I have seen users, editing with compatible version of ArcGIS Pro (say Pro 2.9); they may use later version for read-only functions, analysis, search, query (say Pro 3.1). You will quickly realize being in unsupported/incompatible versions for Desktop (ArcMap and Pro), Enterprise and Geodatabase. It becomes a huge issue for IT/GIS admins to maintain a mixed environment with limitations on upgrades, service packs, security patches. You may continue to operate mixed desktop apps, as long as there are no issues. But this not a best practice and does not align with ArcGIS implementation architecture patterns.
There are many enhancements in ArcGIS including geodatabase objects created by ArcGIS Pro. Solutions like ArcGIS Utility Network, Trace Network, Parcel Fabric, Pipeline Referencing are developed for ArcGIS Pro and comprise of GDB objects that can only be read by ArcGIS Pro. GDB functions like Attribute Rules, Contingent Values are specific to ArcGIS Pro.
@DanPatterson cited the lifecycle link that states ArcMap is in extended support and will be retired March 2026. There are many resources to start/plan Migration to ArcGIS Pro:
Migrate from ArcMap to ArcGIS Pro
ArcMap Life Cycle | Esri Support
you can put off the inevitable, but you might want to begin migrating to Pro sooner
Similar to what Dan said, Esri is employing the "adopt or die" method with their software.
We have similar issues where I work regarding third party add-ons that only work with ArcMap 10.6.1, etc. For those users, we kind of forced them to learn Pro but still use ArcMap when needing that add-on. Maybe it's time to have people live in both worlds until it's "time".
Adrian, harken back to the days of
ArcInfo-ArcView... then
ArcView-ArcMap... then
and so on.
and reflect on the bandage removal analogy. It is going to hurt in any event 😉
@Geodesy Editing of simple features should not cause any issues.
Refer to Client and geodatabase compatibility
Per this compatibility matrix, you should keep the geodatabase (SDE) at version 10.8.1.x to remain compatible with both ArcMap 10.8.1 and ArcGIS Pro 2.6. Note that ArcGIS Enterprise 10.9.1 is the last (most compatible) version with ArcMap 10.8.2 (last release). Starting at ArcGIS 11.0, many ArcMap dependent features are deprecated.
Removal of ArcMap-based runtime from ArcGIS Enterprise
Also, note that the compatibility matrix suggests staying at ArcGIS Pro 2.9 (if continuing to use ArcMap). I have seen users, editing with compatible version of ArcGIS Pro (say Pro 2.9); they may use later version for read-only functions, analysis, search, query (say Pro 3.1). You will quickly realize being in unsupported/incompatible versions for Desktop (ArcMap and Pro), Enterprise and Geodatabase. It becomes a huge issue for IT/GIS admins to maintain a mixed environment with limitations on upgrades, service packs, security patches. You may continue to operate mixed desktop apps, as long as there are no issues. But this not a best practice and does not align with ArcGIS implementation architecture patterns.
There are many enhancements in ArcGIS including geodatabase objects created by ArcGIS Pro. Solutions like ArcGIS Utility Network, Trace Network, Parcel Fabric, Pipeline Referencing are developed for ArcGIS Pro and comprise of GDB objects that can only be read by ArcGIS Pro. GDB functions like Attribute Rules, Contingent Values are specific to ArcGIS Pro.
@DanPatterson cited the lifecycle link that states ArcMap is in extended support and will be retired March 2026. There are many resources to start/plan Migration to ArcGIS Pro:
Migrate from ArcMap to ArcGIS Pro
Thanks to everyone for your replies. I really appreciate it. The compatibility matrix is most useful. This aligns with what I have read so far that you start encountering issues at Pro 3+ unless your entire organization is already migrated off ArcMap and using Enterprise 11.