Create a more streamlined way to transfer/clone ArcGIS StoryMaps from one organization to another. There are several suggested ways to clone and/or transfer an ArcGIS StoryMap from one organization to another. However, these are “workarounds” and still requires a lot of work in order to transfer, including the proper permissions in the source and destination organizations, bugs and other issues depending on the version of ArcGIS API for Python one is using, and having to “re-build” a StoryMap in the destination organization if certain layers don’t transfer but instead are “referenced” back to the source organization.
We are seeing a number of users from our University who are collaborating with organizations who have AGO orgs and wish to transfer their work to the partner/collaborator upon completion.
As the demand to create ArcGIS StoryMaps increases across our campus, so too does the demand to transfer/clone ArcGIS StoryMaps. The inability to quickly and efficiently create a clone and transfer to another organization is becoming a larger blocker.
Here are some existing resources for cloning/transferring ArcGIS StoryMaps pulled from the community.
Notebook from Peter Knoop: https://community.esri.com/t5/arcgis-storymaps-blog/cloning-arcgis-storymaps/bc-p/903720#M43
ArcGIS API for Python sample code: https://developers.arcgis.com/python/samples/clone-storymap-version2/
AGO Assistant Common Workflow to Copy a StoryMap: https://guide.assistant.esri-ps.com/docs/common-workflows
There are already lots of posts on this topic, but I can't find a formal idea: https://community.esri.com/t5/forums/searchpage/tab/message?q=Transfer%20storymaps&advanced=false
