Migrate all saved projects from one server to another

Overview:
This article shows one way to migrate saved projects from one server to another, by moving the source data for one of the indices in the Document Store role.  There are a few things to note before proceeding:

• Some parts of the saved project may be environment-specific and the projects may not load or be visible in their new location.
• This method will not work if migrating from a clustered environment.
• There are extra considerations that will need to be taken when migrating into a clustered environment.
• Migrating your saved projects from one server to another will replace the projects on the destination with the projects from the source.  We cannot combine saved projects from multiple sources.

ArcGIS Enterprise:
Extra steps are required in order to migrate Saved Projects from an old instance of Essentials federated with ArcGIS Enterprise to a new instance of Essentials federated with the same or a different instance of ArcGIS Enterprise. The steps below can be completed before or after migrating the Saved Projects folder, but it's simpler to run these steps first.

1. Run the Essentials Post Installer of the old instance of Essentials and open the security store editor.
2. Find the AGS Issuer Seed and copy it down. This issuer seed is also stored in the Saved Projects JSON.
   1. Example: urn:gcx:ags:75FF8C3A-A9D7-410A-8A01-8D4AE6E1779A
3. Now install and/or run the Essentials Post Installer of the new instance of Essentials. Ensure this new instance is connected to your new/old instance of ArcGIS Enterprise through the Sign-In page.
4. Open the security store editor through the new Essentials instance post installer.
5. There will be a new issuer seed in this instance of Essentials which needs to be changed to the old instance. If this is not completed, then all migrated saved projects will remain orphaned, and no users will be able to open their saved projects.
6. The simplest way to accomplish this process is to copy the entire security store XML from the new post installer and paste it into a text editor like Notepad++. Do a FIND/REPLACE where you FIND the new issuer seed and REPLACE it with the old issuer seed. There should be around 5 instances of the issuer seed in the security store XML.
7. Copy the whole security store XML from your text editor with the updated issuer seed and paste it over the security store in the new Essentials instance post installer with the security store editor. Apply the changes and close the security store (finishing the post installer is only required if you made other changes to the post installer itself).
8. Now you can proceed with the next section of this article, or if you've already moved the Saved Projects folder to the new instance, then you can check to ensure Saved Projects are appearing in the viewers for the correct users.

Migrate the Saved Projects Folder:

1. From the source server, navigate to the following directory: C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\<cluster>\nodes\0\indices

2. Copy the docs_geocortex_essentials_users_documents folder from the source folder to the desktop of the destination server(s), or a similar temporary location.

3. Stop Core on the destination server(s)
4. Move the docs_geocortex_essentials_users_documents folder out of the C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\<cluster>\nodes\0\indices folder, into a temporary location on the server(s)
5. Move the docs_geocortex_essentials_users_documents folder from the desktop into the C:\Program Files\Latitude Geographics\Geocortex Core\Data\DocumentStore\DocumentStore\<cluster>\nodes\0\indices folder on the target server(s)
6. Start Core on the (first) destination server.  Once it's started, start Core on the other server(s) if applicable
7. Log into Essentials manager, and go to the Security and Data tab.  
8. Click on Documents under the Data Store section on the left side
9. The migrated saved projects should all now appear in the Manager interface.
10. You can have your users verify that they see their saved projects when signed into the appropriate Essentials site/viewer. If the saved projects appear in Manager but users cannot see them then the projects are likely orphaned and you should verify if the previous section in this article was missed.