Migration Processes

Mobile Migration Process

Prepare the destination tenant:

• Populate Markup Settings credentials.

• Create an operational map with a temporary name, denoting it as the migration target.

• Ensure the toggle is on for Mobile functionality, and that Mobile is the only toggle for that map.

• Manually create Assignment Types in the Workflows plugin to match the names of the Assignment Types in the source tenant.

• Familiarize yourself with Markup Types, Assignment Types, and Mobile Client Workflows in the destination tenant to aid in post-migration validation.

Perform the migration:

• When creating your Snapshots in the source tenant for migration, we recommend you include Mobile KV Configuration and Mapping Configuration together. A few KV items are associated to operational maps.

• A second snapshot with Mobile Markup Configuration and Mobile Client Configuration is a good pairing.

Perform post-migration corrections in the destination tenant:

• You need the URL of the correct feature service that is to be used in the Destination Tenant, described in the Migration topic.

• You also need the URL of the Default Palette map that is to be used in the Destination Tenant.

• Migrated items are listed in the Mobile section of the Migration topic.

• Items not migrated include Replicas, Filters, Tracing, Tile Packages, Offline Packages, GPS settings, Design settings, and Advanced settings.

• In the Mapping plugin, update the Display Name and the URL of the operational map.

• On the Searches subtab for the selected operational map, view each search to ensure that layers and field names are all connected. If there are any errors, you can address them in the Edit view of each search.

• In the Markup plugin > Markup Types:

  • Correct the URL for the Default Palette for each Markup Type.

  • Remove Service Specific Settings for Unknown Operational Maps from the source, and add them for the destination, if needed.

  • Identify and remove any duplicate items.

GDBM Migration Process

Prepare the destination tenant:

• Create an operational map to receive the configuration. The name and URL you set here persist after the migration.

• Toggle on the setting for GDBM. This service can also have Editor toggled on, plus both configurations can be migrated to the same operational map.

• Ensure the destination tenant has sufficient licenses for simultaneous processing, as configured in the source tenant. Refer to step 2 in the Add or Edit Scheduled Entries topic in the GDBM Implementation Guide.

Perform the migration:

• When creating your Snapshots in the source tenant for migration, GDBM and Editor can exist in a single snapshot, and they can fortuitously be migrated to the same operational map.

Perform post-migration corrections in the destination tenant:

1. Migrated items are listed in the GDBM and Editor section of the Migration topic.

2. Correct the Webhook Secret as needed for your destination tenant.

3. Identify and delete duplicated schedules.

4. Migration allows you to import overlapping schedules, which is not allowed when providing manually in the app. In coordination with a visual check to ensure no overlapping times, you can edit the schedule and note the red error message at the bottom.

Editor Migration Process

Prepare the destination tenant:

1. Create an operational map to receive the configuration. The name and URL you set here persist after the migration.

2. Add machine-to-machine credentials.

   NOTE: This is a crucial step. Refer to the Add a New Operational Map topic and step #7 for more information plus steps to add credentials.

3. Toggle on the setting for Editor. This service can also have GDBM toggled on, plus both configurations can be migrated to the same operational map.

4. Regarding network editing, for all Editor functionality to work, ensure you have completed all the steps on your Utility Network that would enable editing, including building topology and initializing subnetworks.

5. If you are planning to use AutoUpdaters, you need to complete that configuration as well, and this includes installing an SOI (Server Object Interceptor). Refer to the ArcGIS Server Configuration topic for more information.

Perform the migration:

• When creating your Snapshots in the source tenant for migration, GDBM and Editor can exist in a single snapshot, and they can fortuitously be migrated to the same operational map.

Perform post-migration corrections in the destination tenant:

• Correct the AutoUpdater orchestration workflows to point to the correct operational map ID.

• Validation for much of the Editor configuration is done by performing edits in ArcGIS Pro, in particular on the electric Utility Network.

• Once migration is complete, Session Manager is ready to move through a workflow.