It's always a good practice to have a DEV/STAGING environment along with a PRODUCTION environment for ArcGIS Enterprise. I frequently get asked how to migrate content from one to the other. Hosted services can be straight forward, and can easily be scripted (expect an update later to this toolset for this functionality), but referenced services can be rather difficult. For example, there are numerous prerequisites that are required for a service to be published from an Enterprise Geodatabase, such as:
- does the ArcGIS Service Account have necessary privileges
- is the geodatabase registered with the ArcGIS Server instance
- does the feature class in fact exist within the new geodatabase
- etc
These tools pick up once your services have been published to the other environment and you would like to begin migrating web maps, apps, and dashboards. Take a look at the video below on how to execute these tools.
These tools should only be used to migrate web maps/apps where the environments are the same version (i.e. 11.1). Migrating content between two ArcGIS Online organizations is also supported.
Currently, these tools have only been tested in ArcGIS Enterprise 11.1 and ArcGIS Online. If there are any issues, please report in the comment section below.
Updates
1/16/24: Added tools to copy hosted feature services and file based items.
1/29/24: Added option to run when portal has Windows Authentication enabled. Also, updated the Copy Dashboard tool to specify stand-alone layers.
2/12/24: Web Map item IDs now update
3/28/24: Added tool to copy Story Maps
Known Issues
- If hosted feature services exist in Enterprise, they will not successfully overwrite when executing the Copy Hosted Feature Services tool. Will successfully overwrite in AGOL. Possible bug with ArcGIS API for Python
- After Story Map is copied to Enterprise, the Story Map must first be opened in Edit mode and published before it can be successfully viewed. This is not the case for AGOL. Possible bug with ArcGIS API for Python