Migration

The Migration plugin provides a way to transfer certain configurable assets from one tenant to another. Your success with migrating configuration information using this plugin can be assured by understanding certain concepts and reviewing the tenant migration process. Follow the steps in these topics to prepare for and validate the migration.

IMPORTANT: Migration is not intended for updating tenants that have been running over time. Migrating workflows in particular can cause data loss if migrated over existing configuration.

Operational Map Concepts: For each of our applications, certain configuration settings are tied to an operational map, while others are global and apply across all operational maps. When choosing migration options, it is important to keep in mind which operational maps you are selecting in both the Export and Import functions. When you choose an asset for migration, only the configuration in the source operational map is migrated, and it applies only to the operational map you choose as the destination. You need to repeat the export and import steps for each operational map in your tenant. Additionally, migration currently is only able to migrate Mobile configuration to a destination map that has only Mobile toggled. Editor and GDBM can be migrated to a single destination map with only those toggled.

Tenant Concepts

Two important concepts regarding tenant jargon are as follows:

Source Tenant refers to the tenant where the configuration is complete, and it serves as the source of the desired configuration. In the Import dialogue, the field label is From Tenant.
Destination Tenant refers to the tenant receiving the configuration that was exported from the Source Tenant. In the Import dialogue, the field label is To Tenant.

Migrated Assets

The following lists contain all the assets, by product, that are migrated once the process is complete:

Editor and GDBM assets include:

Editor Configuration:
- Searches found within the Mapping plugin > {operational map name} > Searches.
- All data mapping configured on operational maps found within the Editor plugin > Editor Maps.
GDBM Configuration:
- Toggled settings found within the GDBM > Settings tab.
- Schedules that are associated with migrated operational maps, found within GDBM > Schedules.
- Programs that are associated with migrated operational maps, found within GDBM > Programs, including Reconcile Events, Pre-Post Reconcile Events, and Post Events.
- Handlers found within GDBM > Handlers.
- Exception: Control entries and Logs DO NOT migrate, but instead populate as the new schedules run.
Editor Client Workflows:
- Client dynamic workflows found within the Workflows plugin > Studio > Editor Client.
ArcGIS Server Workflows:
- Autoupdater Orchestration workflow and custom autoupdaters found within the Workflows plugin > Studio > ArcGIS Server
Toggles found within the Editor plugin > Advanced > Settings.
Filter and Sort configurations found within the Editor plugin > Advanced > Filter and Sort Configurations for the selected operational map.
Exception: Session Custom Properties or Dynamic Workflow buttons on Editor plugin > Advanced are NOT included.

Mobile assets include:

Mobile KV Storage
- Mobile configuration, including URLs found within the Mobile plugin > Basemaps. Migrations that include basemaps tend to create duplicates, so ensure that you identify and remove all duplicates.
- Configuration and workflows in Markup Types in the Mobile plugin > Markup Types (which leverages and matches the info below for Markup and Workflows).
- Exception: All configuration found within Tile Packages, Offline Packages, GPS, Designs, and Advanced are NOT included.
Mapping Configuration
- Searches found within the Mapping plugin > {operational map name} > Searches.
- Searches, Markup, and Outbound Messages found within Mobile plugin > Operational Maps > {operational map name}.
  - Filtering is NOT included.
- Exception: Replicas and Utility Network are NOT included. Access Control gets newly created with each operational map.
Mobile Markup Configuration
- Configuration for Markup Types that is available for all operational maps, found within the Markup plugin > Markup Types.
Mobile Client Workflows
- Client dynamic workflows found within Workflows plugin > Studio > Mobile Client.

Designer assets include:

Design Styles - Legacy:
- All Design Styles, complete with their .stylx files and settings such as Name, Reference Scale, whether it is the Default or not, Map Colors, and Reference Views.
  - The Backdrops are not included in the migration. Once the migration is complete, revisit Designer > Client Application > Design Styles to re-apply the Backdrops.
- If your tenant includes Electric and Gas, both sets of Design Styles are included in the migration.
Print Layout Elements - Legacy:
- All elements found within Designer > Print Layout > Element, including DynamicImage placeholders, InfoGrids, Maps, Overviews, Scales, and TextBlocks.
Print Page Layouts - Legacy:
- All layouts found within Designer > Print Layout > Page.
Print Images - Legacy:
- All uploaded StaticImages found within Designer > Print Layout > Element.
Tag Settings:
- All configured CU Tags found within Designer > Client Application > CU Tags.
- All configured Work Location Tags found within Designer > Client Application > Work Location Tags.
GIS Attributes Electric
- All fields that have been added for electric GIS Attributes; this includes the checkbox configurations for Required, Read-Only, and Show for Imported.
  
  IMPORTANT: After importing the GIS Attributes, return to Designer > Catalog > Electric GIS Schema > GIS Attributes to check the order of the fields. If the order was not set originally, the application isn’t able to determine order and the fields are sorted randomly.
GIS Attributes Gas
- All fields that have been added for gas GIS Attributes; this includes the checkbox configurations for Required, Read-Only, and Show for Imported.
  
  IMPORTANT: After importing the GIS Attributes, return to Designer > Catalog > Gas GIS Schema > GIS Attributes to check the order of the fields. If the order was not set originally, the application isn’t able to determine order, and the fields are sorted randomly.
Editing Templates
- All Palettes and Templates. If your utility has both gas and electric, both are included in the export and import.
  
  IMPORTANT: Restart the Designer XI application to see the imported Palettes and Templates.
CU Categories
- All categories as found in CU Categories.
Stamp Graphics
- All Stamp Graphics. If your utility has both gas and electric, both are included in the export and import.
  
  IMPORTANT: Restart the Designer XI application to see the imported Stamp Graphics.
Vector Print, Templates, Styles, and Labeling
- All pre-configured Page Templates, Design Styles (created to support vector printing first released at version 11.5), and Labeling (also created to support vector printing first released at version 11.5).

Special Consideration for Print Layouts, Elements, and Images:

You are able to toggle Layouts, Elements, and Images independently when performing the migration. However, keep in mind that Layouts include Elements and Images. Thus, if you migrate Layouts but do not migrate the Elements and Images that compose the Layouts, the Layouts do not render appropriately. Always consider the “child” components of Layouts when migrating.

If you choose to migrate these independently, the order of migration does not matter. The important part is that, in the end, all Layouts have their dependent Elements and Images.
It is perfectly acceptable If you want the Layouts but do not want the existing Elements and Images. You need to re-create the Elements and Images after migration. This could be handy if you are trying to “wipe the slate clean” and start over with new print components.