Perform Device Migration

This chapter describes how to run and manage a Device Migration job.

Create a Device Migration job

This topic explains how to create a Device Migration job by selecting devices, selecting a migration MOP, and entering job inputs.

Perform this task when you are ready to start a migration after preparing devices and a migration MOP.

Before you begin

  • Ensure the source and target devices are onboarded and reachable.

  • Verify that a migration MOP is available.

  • Confirm that any required device roles or labels are assigned.

  • Ensure you have permission to create and run migration jobs.

Procedure

Step 1

From the main menu, choose Device Management > Device Migration.

Step 2

The New Device Migration window appears, with the first step, Select Devices, highlighted. Select all devices that will participate in the migration, including the device being replaced, the device that will receive services and traffic, and any additional devices required for traffic diversion or validation.

Step 3

Click Next. The New Device Migration window is refreshed, with the next step, Assign Device Roles, highlighted. Assign a role to each selected device.

  • Source for the device being migrated

  • Target for the device receiving configuration and traffic

  • Neighbor for devices used during traffic diversion or validation

Note

 

  • You can assign the same role to multiple devices. This is useful when several devices share the same function in the migration—for example, when multiple neighboring devices participate in validating or diverting traffic during the migration.

  • Assigning a device role does not modify the device configuration. Roles are used only to control how actions reference devices during execution.

Step 4

Click Next. The New Device Migration window is refreshed, with the next step, Select MOP, highlighted. Select a custom migration MOP that defines the stages, actions, and validation logic for the migration.

The selected MOP must already exist and must be designed to operate using the assigned device roles.

Note

 

All inputs required by the actions must be defined in the migration MOP. These typically include references to existing services, parameters used to create or update services, and values required for validation checks. All inputs must be explicitly provided.

Step 5

Click Next. The New Device Migration window is refreshed, with the next step, Execution Settings, highlighted. Provide an appropriate Job name and select the Execution sequence. Specify whether the migration job should execute immediately or be scheduled to run at a later time. The execution timing applies to the job as a whole.

  • Provide an appropriate Job name

  • Select the Execution sequence: Choose whether the migration job should start immediately or be scheduled for a later time. The execution timing applies to the job as a whole.

  • (Optional) Enter Job tags to help identify the job later.

Important

 

You can run the stages in a migration MOP back-to-back—either immediately or at a scheduled time—or you can run each stage at different times. This page allows you to define the stage schedule, including setting individual execution times and adding delays or gaps between stages if needed.

Step 6

Click Next. The New Device Migration window is refreshed, with the final step, Summary, highlighted. Review the device migration settings you selected. Click Run Job to submit the job.

The migration job is created and appears on the CWM Solutions Jobs page.

Monitor a Device Migration job

After submission, the migration job is queued for execution based on the selected timing. The job executes each stage defined in the migration MOP in order. All actions in a stage complete before the next stage begins. If an action fails, execution stops at that point, and the job enters a failed state.

Use this procedure to monitor the progress and outcome of a Device Migration job.

Procedure

Step 1

From the main menu, choose Workflow Automation > CWM Solutions Jobs.

Step 2

Identify the migration job using its name or status.

Step 3

Observe how the job progresses through the defined migration stages.

Step 4

Select individual actions to view execution status, inputs, outputs, and validation results.

Step 5

Use action-level messages to determine where issues occurred and whether corrective action is required.

Retry a Device Migration job

Retry allows a failed migration job to be executed again. When a job is retried, you can execute the entire job or resume execution from a specific stage.

Use this procedure to retry a migration job.

Procedure

Step 1

From the main menu, choose Workflow Automation > CWM Solutions Jobs.

Step 2

Locate the job that failed and review the action where the failure occurred.

Step 3

Choose and select Retry. You can choose to retry the entire job or a specific stage.

Note

 

If you choose to retry a specific stage, the previously completed stages are not re-executed.

Click Retry to confirm.

Step 4

The job is retried as per your selection.

Step 5

Observe job execution to confirm successful completion.

Rerun a migration stage

Use this procedure to rerun a stage of the Device Migration job.


Note

Rerun operation is useful when earlier assumptions need to be revalidated or when migration inputs have changed.

Procedure

Step 1

From the main menu, choose Workflow Automation > CWM Solutions Jobs.

Step 2

Identify the job that must be re-executed.

Step 3

Choose and select Rerun.

The Rerun Stage window appears.

Step 4

Select the migration stage. Click Rerun to confirm.

Step 5

Track progress as the job reruns the selected migration stage.

Failure handling and validation

Action evaluation

Each action evaluates its outcome based on defined success conditions. Optional warning or failure conditions may also be configured. If the success condition is not met, the action is marked as failed by default.

Failure visibility

Failure information is available at multiple levels:

  • Action-level details in the Jobs page show inputs, outputs, and evaluation results.

  • Workflow execution details provide additional diagnostic information about where and why a failure occurred.