Migration scenarios - Automate_Studio_Manager - Automate_Evolve - Latest

Automate Studio Manager Migration Guide
Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio Manager
Version
Latest
ft:locale
en-US
Product name
Automate Studio Manager
ft:title
Automate Studio Manager Migration Guide
First publish date
2018
ft:lastEdition
2024-02-16
ft:lastPublication
2024-02-16T10:31:20.160000

See the table below for the various migration scenarios.

Script Types Applicable Versions Migration Path
Single Transaction scripts (All data sources supported) 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager
Single Query scripts (All data source supported) 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager
Linked Transaction scripts 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager
Linked Query scripts 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager
Multi-Transaction scripts 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager
Multi-Query scripts 10.7, 11.x, 12.x NA
Cross-linked scripts 12.x NA
Query and Transaction scripts together in a data Template 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager (execution with some recommendations)
Transaction single and Transaction linked script together in a data template 10.7, 11.x, 12.x Move to Studio Manager/Evolve using Migration Manager (with limitation around template name)
Any other composite script types that are not natively supported 10.7, 11.x, 12.x Not supported
Managing specific scenarios

Composite script Scenarios for 10.x, 11.x, and 12.x SharePoint sites

  1. Round-trip scripts are composite scripts. A script is marked composite if the template contains more than one script information from the same site. The information of the composite is marked only by clicking the download button on the source site.
  2. We recommend migrating single and linked files before migrating composite scripts.
  3. When migrating composite scripts, read the preceding script and check its migration status.

    If it did not migrate (‘errored’), an error message will direct you to migrate that script first.

  4. After the preceding script is migrated, go to subsequent composite scripts from the same site to continue the migration.
  5. Round-trip scenarios and multiple scripts published in templates via non-standard routes (except for the multi-script submissions wizard feature) are not supported. As an alternative, migrate only the latest script and associated latest template. (That script is the only one that will remain published in the migrated template.)
  6. All scripts in a composite script bundle are on the same TeamSpace.
  7. Published scripts from other source foundation sites are removed from the template.
  8. Published Connect-only mode scripts are removed (for all templates independent of round- trip scenarios).
  9. Conflict resolution will restrict each template migration if reference scripts do not exist.