Migration

This section describes how to migrate automation assets from Artificial Intelligence for IT Operations Automation Service (AS) to Bridge Automation Service (BAS) and validate the migrated content.

Initiate the AS to BAS migration

Prerequisites

Before starting the migration, ensure that:

Dedicated CACF credentials have been created and configured in Connections Management as described in Pre-migration.

Automation service access groups have been migrated to Bridge IAM, and the corresponding BAS roles have been assigned to maintain the same level of access.

Automation Service role	Bridge Automation Service role
Administrator	Orchestration administrator
Editor	Orchestration editor
Operator	Orchestration operator
Viewer	Orchestration viewer

Migrate Catalogs, Schedules, and Events from AS to BAS

Prerequisite: Ensure that the user performing the migration has the Orchestration Administrator or Bridge Administrator role.

From the main menu , go to Catalogs → Orchestration Catalog → Operations.

In the AIOPS Automation Services - Convergence section, select AIOPS Automation Services Migration catalog item.

Run the catalog item to migrate the following AS assets to BAS:

Public catalogs

Private catalogs

Schedules

Events

Monitor the workflow execution and verify that the migration completes successfully.

Do not run multiple migration jobs simultaneously. Wait for the current migration job to complete before starting another migration.

Run the migration catalog item

Select More actions menu (...) from the AIOPS Automation Services Migration catalog item and select Run.

Select the appropriate version and connection.

Select the connection that was created using the dedicated CACF credentials in Bridge connections manager.

On the Parameters page, click Next without entering any values.

On the Target & Hosts page, click Next without selecting targets or hosts.

On the Review & Submit page, click Run.

Verify migration status

From the main menu , go to Services → Platform Services → Bridge Automation → Workflow Executions.

Locate the AIOPS Automation Services Migration workflow, review the Status column to determine whether the migration is: Completed, Running and Failed.

To view execution details, select the More actions menu (...) and then select View Details.

Review the list view to view the status of migration steps.

The Activities tab helps identify completed, in-progress, and failed migration tasks.

If a migration activity fails, see Troubleshooting and FAQTroubleshooting and FAQ. After the migration workflow completes successfully, the supported automation assets are available in BAS.

Public catalogs

Public catalogs from AS are migrated to BAS, and:

Catalogs enabled in AS are automatically enabled in BAS.

All associated catalog configurations are migrated.

Migrated public catalogs appear in Orchestration Catalog with the Global label.

To activate a catalog, select the More actions menu (...) and then select Activate.

Private catalogs

Private catalogs from AS are migrated to BAS and enabled by default, and:

All associated catalog configurations are migrated.

Migrated catalogs are placed in the Advanced Delivery – Single Owner Asset category.

Catalogs are available from Orchestration Administration.

Schedules

Schedules from AS are migrated to BAS and are disabled by default. After migration:

From the main menu , go to Bridge Automation Services → Schedules.

Review the migrated schedule configuration.

Validate execution details, parameters, and target information.

Enable schedules only after validation is complete.

To view schedule details, select the More actions menu (...) and then select View.

Events

Event triggers from AS are migrated to BAS and are disabled by default. After migration:

Review each event configuration.

Verify trigger conditions.

Validate associated workflows and catalog mappings.

Enable events only after validation is complete.

Migration behavior and limitations

Subsequent migration executions skip previously migrated items and migrate only newly added or changed assets from AS. If a migrated catalog must be recreated, retire the catalog before rerunning the migration.

All content and user authorizations that exist in the AS tenant are considered approved by the Delivery Platform Engineer (DPE).

Only GEMU-based automation content is migrated to BAS.

The following items are not migrated:

Legacy Artificial Intelligence for IT Operations Automation Service content

GHES-based content

Schedules associated with excluded content

Events associated with excluded content

This behavior is part of the content sanitization process defined by the Delivery COE.

Verify migrated content

After migration, verify that all expected assets are available and function correctly.

Verify catalogs

After migration, verify that all expected public and private catalogs have been migrated correctly and are available in Bridge Automation Service (BAS). Validation helps ensure that catalog configurations were migrated successfully and that catalog items can be executed as expected.

Compare catalog counts

From the main menu , go to My Automations, record the number of Private catalogs and Public (Certified) catalogs.

In Bridge Automation Service, go to Orchestration Catalog and record the number of Catalogs in Advanced Delivery – Single Owner Asset (private catalogs) and Catalogs in Components with the Global - Enforced label (public catalogs).

Verify that the BAS catalog counts match the AS catalog counts.

Test migrated catalogs

Open a migrated catalog.

Select Run.

Select the appropriate connection.

Provide credentials and inventory information as required.

Review any migrated parameter values.

Select Run.

To verify execution:

From the main menu , go to Services → Platform Services → Bridge Automation → Workflow Executions.

Select the More actions menu (...) and then select View Details.

Open the Output Parameters tab.

Verify that all activities completed successfully and produced the expected results.

Verify schedules

After migration, verify that all schedules have been migrated successfully and retain their expected configuration. Validation helps confirm that schedule counts, frequencies, and execution settings in BAS match those in Artificial Intelligence for IT Operations Automation Services before schedules are enabled.

From the main menu , go to Bridge Automation Services → Schedules, record Schedule count and Schedule frequency.

Compare Schedule count and Schedule frequency.

Verify that Schedule counts and frequencies match.

Migrated schedules remain disabled until validated and approved.

Verify events

After migration, verify that all event-driven automations have been migrated correctly to BAS. Validation helps ensure that event rules, trigger conditions, workflow mappings, and input configurations are preserved and function as intended before event rules are enabled.

In the Artificial Intelligence for IT Operations Automation Service main menu , go to Settings.

Open the Event Settings section to review the DSS topics configured for event processing.

From the main menu , go to My Automations.

Locate an automation that contains event-based execution settings, and then select Set up.

Open the Automated Execution section.

Review the event configuration and record the following information:

Trigger conditions

Associated automation

Input mappings

Event processing configuration

From the main menu , go to Bridge Automation Services → Event Rules.

Locate the migrated event rule.

Select View to review the event rule configuration.

Verify that:

All expected event configurations have been migrated.

The trigger conditions match the original configuration in AS.

The associated workflow or catalog is correct.

Input mappings have been migrated correctly.

Migrated event rules are in the Disabled state, where applicable.

Do not enable migrated event rules until the corresponding event-driven automation in Artificial Intelligence for IT Operations Automation Service has been retired. Enabling event processing in both platforms can result in duplicate automation executions.

If any expected event rules are missing or configuration discrepancies are identified, document the details and notify the migration support team for further investigation before enabling the event rules for production use. For more information, see Support.

Migration reports

Account eligibility and executive summary report

The migration service validates each Automation Service account and its associated CACF instance to determine migration eligibility.

The report includes account information such as:

Field	Description
Account Name	Account registered in Kyndryl Bridge
Kyndryl Bridge ID	Unique Kyndryl Bridge account identifier
Artificial Intelligence for IT Operations ID	Unique Artificial Intelligence for IT Operations account identifier
Automation GSMA Code	GSMA code associated with the account
BAC ID	BAC code associated with the account
Country Name	Country or region associated with the account
Artificial Intelligence for IT Operations Active Runner Set (Y/N)	Indicates whether an execution platform is configured
Convergence Eligibility (Y/N)	Indicates whether the account meets migration requirements
Convergence Catalog Item Creation (Y/N)	Indicates whether the migration catalog item was created

Migration execution results

The Migration execution results table provides a summary of migration and convergence activities. It includes details about execution history, workflow identifiers, request information, migration status, and the results of migrated assets such as access groups, catalogs, schedules, and events.

Field	Description
Total Executions	Number of migration execution attempts
Last Convergence Workflow ID	Most recent convergence workflow identifier
Request Date	Date and time of the latest convergence request
Requested By	User who initiated the convergence
Status	Current or final migration status
Converged Item Details	Results for access groups, public catalogs, private catalogs, schedules, and events. For each migrated asset type, the report provides: Total Success Skipped Error

Cut-off workflow results

The Cut-off workflow results table provides information about the most recent cut-off workflow execution. It includes request details, workflow status, and the status of actions performed during the cut-off process, such as disabling Automation Service event settings and schedules, and enabling corresponding Bridge Automation event rules and schedules.

eld	Description
Last Cut-off Workflow ID	Most recent cut-off workflow execution
Request Date	Date and time of the request
Requested By	User who initiated the request
Status	Current or final status
Event Settings Disabled in AS (Y/N)	Indicates whether all AS event settings were disabled
Schedules Disabled in AS (Y/N)	Indicates whether all AS schedules were disabled
Event Rules Enabled in BAS (Y/N)	Indicates whether BAS event rules were enabled
Schedules Enabled in BAS (Y/N)	Indicates whether BAS schedules were enabled

This report helps delivery teams and leadership validate migration readiness and track progress across migration phases.

View detailed migration results

Detailed migration results are available in the Output Parameters tab of the latest AIOPS Automation Services Migration workflow execution.

From the main menu , go to Services → Platform Services → Bridge Automation → Workflow Executions.

Open the latest migration workflow.

Select View Details.

Open the Output Parameters tab.

Users can copy the output directly from the interface for further analysis or reporting.

Migration result statuses

For detailed information about migrated items, review the migration results in the following table. The table describes the migration status values and error conditions that can appear in the Converged Items Details section of the migration report.

Status	Description
Total	Total number of migration-eligible items. Obsolete GHES-based Private and/or Public Catalog are excluded.
Success	The item was successfully created in BAS.
Skipped	The item already exists and was not recreated during the current migration execution. Examples: "reason": "catalog_item_already_exists" "reason": "schedule_already_exists"
Error	The item could not be migrated due to an error. Detailed error information is retained for troubleshooting. Examples: outcome failure: public catalog item "catalog_item_name" not found - it may not have synced down from KPC yet outcome failure: catalog item "catalog_item_name" not found for automation "catalog_item_name" "reason": "unknown"