Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Migrating data to Deployment Manager 5

Updated on July 14, 2022

Use the migration assistant feature to safely migrate data, including roles, operator records, and pipelines to the version 5.x model. Only users with the Super Admin role can perform pipeline, operator and roles migration.

Note: If you are on 4.x version of Deployment Manager, moving to latest version of Deployment Manager does not impact any of the existing pipelines working on 4.x version. We recommend installing and configuring Deployment Manager 5.x to test and migrate a single pipeline before performing a full migration.

Pipeline migration

  1. Import the Deployment Manager 5.x RAPs and restart the server.
  2. Log in to Deployment Manager using the DMReleaseAdmin operator.
  3. In the lower-left corner of the application, click the Operator icon, and then select Switch to Dev Studio.
  4. Open the operator record, and then update the default access group to SuperAdmin.
  5. Log out of the application, and then log in as the DMReleaseAdmin operator.
  6. On the Deployment Manager banner, click the info icon.
  7. Click Migration assistant.
  8. In the Pipeline Migration section, select the pipelines that you want to migrate.

    Note: Migrate dependent pipelines first. View dependencies link provides details of all pipeline dependencies.

  9. Click Migrate.
  10. Confirm the pipeline migration by clicking Submit.
  11. When the migration is complete, the pipelines indicate the status of their migration:
    Indicates that the migration of the pipeline is successful. Expanding the row provides additional details on the pipeline migration.
    Indicates that the creation of pipeline failed. Click View log to understand the cause of the failure.
    Not migrated
    Indicates that the pipeline is not migrated and the user can start the migration as required.
  12. If pipeline migration fails due to a loading error, ensure that the open ruleset in which pipeline case types are stored is present in the Deployment Manager 5.x application stack.
  • Stop all active deployments. Any deployments in progress are automatically aborted during the update.

Migrating the operator

After a successful update to the 5.x version, you can update operators from the Migration assistant page. Operator migration migrates the existing roles to associate them with selected operators.

  1. On the Deployment Manager banner, click the info icon.
  2. Click Migration assistant.
  3. In the Operator Migration section, select the operators that you want to migrate.
  4. Click Migrate.
  5. Confirm the operator migration by clicking Submit.
  6. The operators table provides the status of operator migration:
    Indicates that the selected operator migration succeeded.
    Indicates that either role or operator migration failed. For more information, you can click View update logs on the Migration assistant page.
    Not migrated
    Indicates that the operator is not migrated and the user can start the migration as required.

    Note: Operators that you migrate manually to version 5.x are not tracked by the operator migration feature.

Updating access group

If you are updating to version 5.x, ensure the PegaDevOpsFoundation:Administrators access group is updated to point to version 5 of the PegaDevOpsFoundation application. Perform this update for all candidates that are updated to PegaDevOpsFoundation 5.x.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us