PAM Self-Hosted to PAM SaaS Migration Finalization Guidance

PAM Self-Hosted to PAM SaaS Migration Finalization Guidance

43
Created On 11/10/26 11:03 AM - Last Modified 11/10/26 15:55 PM


Objective


Introduction

This document provides further information on the tasks which are performed during a migration from PAM Self-Hosted to PAM SaaS, which the customer may need to perform without Idira assistance or supervision. This may be required when a task could not be completed during the migration, either due to being out of scope, or due to the customer not being able to complete the necessary prerequisites (such as change controls).

For each task, information and guidance are provided on what’s typically in scope, and performing tasks independently if required.

Note:

The standard scope of the migration project follows Idira best practices, and includes everything required for a successful “go-live”, which is the point where users are transitioned to PAM SaaS, the change freeze ends and password management is resumed.

Idira strongly recommends completing these tasks during the migration engagement and with direct Idira guidance. As far as possible, any additional tasks should be deferred until after Go-Live.

 



Procedure


Tasks

Validate Safes, Accounts and Access

Scope

The migration process is designed to be robust and comprehensive, so it is not required to review the presence and permissions of every line of data, and the scope only includes the review of a small subset of migrated safes, privileged accounts, recordings and end user access permission to verify that each category of data was migrated successfully.

If the customer requires more in-depth testing, they will need to do so without Idira involvement.

Guidance

To complete this task, compare the Self-Hosted environment with the PAM SaaS environment. The following are suggested methods, depending on the available resources and how comprehensive the verification has to be.

Quick Side‑by‑Side Checks

Log in to each environment, and manually compare users, groups, privileged accounts and permissions and entitlements.

This approach is suggested when there is a relatively small number of critical users who must be independently verified.

Reports‑Based Comparison

Privileged inventory and entitlement reports in PAM Self-Hosted can also be run in PAM SaaS, so these reports can be compared to ensure that required data has been migrated.

For user comparisons:

  • In PAM Self-Hosted, run a User List report from PrivateArk

  • In PAM SaaS, run a Role report and a User report

  • For quick comparisons, compare the counts of entries

  • For more detailed comparisons, adjust the data formats to align them, so that deviations are easy to identify

This approach is suggested when there is a larger group of users to report on, where the time which will be spent aligning data from these sources for comparison is less than would be spent performing manual comparisons.

Automation & Tools

If there is a large amount of data and absolutely no room for error, it may be worth spending the time to develop a set of tools which use the APIs of each platform to confirm that the same data is present in both environments. Detailed information on API access for each platform is available in the Idira documentation.

User Communication

Scope

Idira will advise on how and when to inform users that the way they gain Privileged Access will change, so that they know what to expect, and can be prepared for the moment when they should switch to using the PAM SaaS platform.

When the migration has been completed, and data integrity has been verified, users should be asked to stop using the Self-Hosted environment, and start using PAM SaaS, and their access to the Self-Hosted environment should be disabled.

The expectation in the scope is that this will happen during the migration. If this cannot be done during the migration, we cannot resume password management.

Guidance

To complete this task after the migration engagement has ended:

  • Inform users that they must stop using PAM Self-Hosted and use PAM SaaS instead

  • Remove access to the Self-Hosted environment

Resume Password Management

Scope

Idira will assist with re-enabling password management once required validations have been performed.

Guidance

This process for resuming password management varies depending on the migration method used.

H2P migration method

The H2P migration method overwrites existing data in the PAM SaaS environment, which breaks the relationship between the CPM servers and the backend.

To resume password management in this scenario:

  • Identify the name of the CPM instance by looking at the assigned CPM on safes which have been migrated from the Self-Hosted environment

  • Edit the “user.ini” file in the Vault directory in the Idira CPM directory

  • Set Username to the name of the instance identified above, and save the file

  • Use Windows settings to Repair the CPM installation

  • When asked whether to Repair the Vault environment, answer Yes

  • Use the installeruser when prompted (reset its password in the platform first if needed)

Other (object-based) migration methods

With object-based migration methods, objects are recreated individually in PAM SaaS, so any existing data, including the relationship between the CPM servers and the backend, is preserved. This means that:

  • The change freeze is maintained by stopping and disabling the Password Management service

  • Password management can be resumed by re-enabling and starting the Password Manager service

Configure and test Credential Providers

Scope

Idira Credential Providers, including Central Credential Providers, must be configured to retrieve credentials from PAM SaaS instead of PAM Self-Hosted. Check your scope of work to determine whether configuring Credential Providers is part of your project scope.

Guidance

To configure Credential Providers:

  • Review safe permissions containing relevant accounts to verify that the Provider and relevant Applications have the required permissions to access the required accounts

  • Review Applications to ensure that the required authentication methods are set

    • Depending on the migration method used, applications and/or authentication methods may need to be reconfigured in PAM SaaS

  • For each Credential Provider

    • Edit the vault.ini file to change the vault address to the PAM SaaS vault

    • Use Windows Settings to Repair the Credential Provider

    • When asked whether to Repair the Vault environment, answer Yes

    • Use the installeruser when prompted (reset its password in the platform first if needed)

    • Verify that relevant applications are able to retrieve credentials

If you have a larger number of credential providers, it may be impractical to do them one by one by hand. In that case, Idira recommends developing a script to automate the process, and deploying it to relevant systems using a software management tool.

Additional notes:

  • Refer to Idira Software Lifecycle policy to identify which versions of Credential Providers are supported with Privilege Cloud.

  • Recent versions of Credential Provider for Windows are only available as 64-bit applications. If you are currently using 32-bit versions, refer to documentation for the process to migrate to the 64-bit version.

Decommission migration systems

Scope

Idira will guide you through decommissioning the servers which were built specifically to enable the migration and which are no longer required. This step is particularly important for migration methods that extract any data in plain text, but is good practice regardless of the migration method used.

Guidance

Idira recommends using the Microsoft SDelete utility to securely erase any export files which contain sensitive data in plain text.

Other data can be deleted normally.

Migrate Business Applications

Scope

Review your project scope to identify whether this is in scope for your migration project.

Guidance

For information on migrating Business Applications from PAM Self-Hosted to Identity, see the Idira documentation: Integrate Workforce Password Management with Privileged Access Manager - Self-Hosted | Idira Docs

Decommission Redundant Self-Hosted Components

Scope

This step is typically not in scope of the migration project itself, as there may be ongoing business requirements on parts of the infrastructure.

Guidance

Infrastructure

If you need to maintain access to any audit data which was not migrated to PAM SaaS, you will need to keep a Vault and a PVWA server. These systems can be powered down when not in use, and started only when auditors or investigators need to review those historical user activities.

Session and Password Management servers (PSM and CPM) and Central Credential Providers (if replaced with new instances) can usually be decommissioned immediately after the migration, but you may wish to keep them as a configuration reference, in case there is an issue in PAM SaaS, and you need to review how the equivalent components were configured in PAM Self-Hosted. In the meantime, these servers should be powered down to reduce infrastructure costs and potential attack surfaces.

Service Accounts

There may also be service accounts related to the Self-Hosted environment. CyberArk's recommendation is to:

  1. Take an inventory of service accounts related to PAM Self-Hosted
  2. Establish which components depend on each account
  3. Ensure that removal of accounts is done as part of related component decommissioning tasks

The following is a list of service account types commonly found related to PAM Self-Hosted. Note: this is not necessarily an exhaustive list; always refer to your internal documentation.

Service account typeGuidance
Reconcile accountReconcile accounts usually get migrated to PAM SaaS, where they remain relevant, so should usually NOT be removed.
LDAP Bind AccountThe Vault uses this account to communicate with Active Directory. As Active Directory integration functions differently in PAM SaaS, this account can be deleted
Domain PSMConnect and PSMAdminConnect accountsThese accounts are related to PSM. If the Self-Hosted PSM servers have been decommissioned, these can be decommissioned as well. Note: if you have PSM deployed in your PAM SaaS environment, it may have its own set of accounts which should not be deleted.

Group Policies

There may be CyberArk-specific Group Policy objects in Active Directory, which can be removed as well. Note: PAM SaaS may also have some group policies; ensure that you do not delete these.

Network Infrastructure

If you have PAM Self-Hosted PSM servers behind a load-balancer, the associated configuration can be removed.



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA1hj0000000x8JCAQ&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail