Service Bridge for Providers (Legacy) - Migration UtilityMigrate configuration data from Service Bridge for Providers (Legacy) to the new Service Bridge for Providers application This article will explain how to migrate Service Bridge configuration data, what configuration data will be migrated, and what configuration data is outside the scope of the migration utility. Note: There is no Service Bridge Consumer migration utility. Migration is limited to Service Bridge Providers. Consumers will register with the provider on the new application and their defined entitlements will determine which capabilities are delivered to that consumer. The migration utility is only capable of migrating Legacy configurations to the 1.x.x versions of the new Service Bridge for Providers. If upgraded to 2.x.x the migration utility cannot be used. Pre-requisites for running this migration utility: The Service Bridge for Providers (Legacy) application version must be greater than or equal to 3.2.4 Install the latest legacy global script include The Service Bridge for Providers application version must be 1.x.x to function. (See the highlighted not above) Install the latest global script include Admin has installed the Service Bridge Migration Utility update set (steps provided in below section)Run all operations as admin Important notes: The migration utility is built to migrate configuration data from the Legacy Provider application to the new Service Bridge Provider application. The configuration data which will be migrated are: Remote task definitions and related tablesRemote Choice definitionsTransforms and related tablesRemote record producers and related tablesCustomer criteria for entitlementsPersonas Note: Any configuration or customization beyond what is defined above is outside the scope of migration. This may include: Transactional data, like tasks. Existing tasks are to be worked and closed as usual.ANY customization or configuration. E.g. Business rules, Flows, Client scripts, and Script includes. It is important to use Push to current update set for production environments so that all provider instances (e.g., dev, test, prod) have the same sys_ids for the configuration data. If Push to current update set is not checked when records are migrated, there is not another chance through the utility to capture them in an update set. Use the migration utility in just one instance, and then use the update set(s) to add the captured configurations to the other instances.When using Push to current update set, if you have legacy configurations in different application scopes, we will only migrate the ones belonging to your current selected application scope. You will need to create an update set for each scope and run the migration once per scope.If not using Push to current update set all configurations will be migrated at once regardless of application scope. This should only be used for demo instances where there are no other instances in the stack. This migration utility can be run multiple times and will not create duplicates. Each run will only migrate configuration records that have not been previously migrated.It is important to note that configurations modified in Service Bridge for Providers (Legacy) after they have been migrated will not be migrated again. The Legacy and New Service Bridge applications can be run in parallel. This allows legacy consumers to be registered as needed into the new application. Once a consumer is migrated, their entitlements should be removed from the legacy application to keep new tasks from being created there.Once all existing tasks are closed for a consumer the legacy connection should be disabled. Import the migration utility update set on the Provider instance: Download Service Bridge – Migration Utility.xml to your local machine. Navigate to All > System Update Sets > Retrieved Update SetsFrom the header menu, right-click and select Import XMLSelect the file you downloaded and click UploadOpen the update set with name (SB Migration Utility) you just uploaded.Preview the update set and commit it.Now you should be able to see a new application menu All > Service Bridge Provider > Administration > Migration Utility.Only users with the admin role will be able to see this new menu and run migration. How to run Migration: Login as an admin userNavigate to All > Service Bridge Provider > Administration > Migration UtilityCreate a new Migration task by selecting below options.If Push to current update set is selected, migrated configurations are pushed into your currently selected update set.If Migrate Inactive records is selected, inactive configurations will also be migrated. By default the utility will migrate only active configurations.Once the migration task record is created you will be able to start the migration using the Start migration UI action.Successful or Failed migration messages will be add as work notes on this migration task. This way it is easy to find all migrated records.User will be able to create only one migration task and this utility will migrate all the configurations from Service Bridge for Providers (Legacy) application to Service Bridge for Providers application. Post Migration Checklist: Onboarding Service Bridge consumersChange the customer criteria to remove entitlements from the legacy application to keep new tasks from being created after registration.Once all existing tasks are closed for a specific consumer the legacy connection(IDR replication set) should be inactivated.