- The migration works for both Studio Manager and Evolve mode for standard workflows only (for example, 1-Step, 2-Step, and NDRs); custom workflows are not within scope.
- Script Migration. Only those scripts with production status are migrated. Rejected, in-review, archived, or other scripts cannot be migrated; they will not be downloaded into the local storage utility. Scripts mapped to all data sources except SharePoint are migrated.
-
Only the latest version of each script is migrated. Scripts are migrated along with the
latest templates associated with it. When metadata and the contents from the source have
been downloaded into local storage, you cannot overwrite them with a refresh operation;
instead, you must add new entries.
Note: If metadata is downloaded without its contents, please be aware of the following: If the source metadata is changed, and you perform a refresh operation, the metadata is not overwritten. And when you try to download its content, you will receive a validation message indicating a version mismatch.
Be aware of the following while downloading metadata without its contents:
- Metadata is not overwritten if the source metadata is changed, and a refresh operation is performed.
- When you try to download its content, you will receive validation messages indicating a version mismatch.
- Datafiles (submitted templates as a datafile) are not migrated.
- The script workflow process history will not be migrated.
- Multi-scripts are migrated only if they have an Excel data source.
- Supporting files for all scripts are migrated along with the solution in Studio Manager/Evolve.
- Supporting files of different libraries will be migrated like what is shown in studio, for example, supporting document of one library only will be migrated.
- Input files are migrated with the solution/script.
- Templates are only migrated along with script solutions; individual template migration is not supported. You must re-download templates from the new Studio Manager/Evolve environment. Local saved templates downloaded from previous UserGovernance/Foundation sites will not work. Only the latest script version template is migrated.
- Query without a template is migrated; a new template is generated as well as headers and publishing information. Here, the default template name is the script name.
- Rejected, In-Review, Archived, or other scripts cannot be migrated; they will not be downloaded into the local storage utility. Scripts mapped to all data sources except SharePoint are migrated.
- Only the latest version of each script is migrated. Scripts are migrated along with the latest templates associated. When scripts and the contents from the source have been downloaded into local storage, you cannot overwrite them with a refresh operation; instead, you must refresh the library and download the fetched scripts.