Privilege Cloud migration & platform consolidation
Two vaults are one too many. Whether you are moving to Privilege Cloud or merging regional platforms, the hard part isn't the tooling. It's the thousands of accounts nobody has looked at in years.
Two kinds of migration
Most migration requests we see take one of two shapes, and many projects combine them.
Self-hosted to Privilege Cloud
The Vault and the web portal become a service operated by the vendor; CPM and PSM move onto connector servers that stay in your network. You stop patching vault servers, and you start managing a SaaS tenant, its identity layer and its connectors.
Several platforms into one
Mergers, regional autonomy and old projects leave large organisations with several CyberArk platforms, each with its own conventions. Consolidating them cuts cost and audit effort, but only if the target design is cleaner than any of the originals.
Our method
- Inventory and clean-upAccounts, safes, platforms and owners. Dead accounts and orphan safes are retired before the migration, not after.
- Target designSafe naming, permission model, platform standards and connector topology, agreed with your security and operations teams.
- Tooling as codeMigration scripts against the REST API, infrastructure as code (Terraform, Git pipelines) for the components you keep, and repeatable dry runs.
- Waves and parallel runPerimeter by perimeter, with old and new platforms running side by side and a rollback plan for every wave.
- DecommissioningOld vaults are shut down only once recordings, audit trails and reports have a documented home.
What you keep, what you redesign
Credentials, safe structures and permissions can be carried over. A migration is still the right moment to fix the conventions that make daily operations painful.
Session recordings and audit history need a decision of their own: kept on the old platform for their retention period11Retention periods for session recordings are usually set by internal policy or by sector regulation (banking, insurance), not by the tool., exported, or archived. We document that decision with your compliance team before the first wave.
Field note
Insurance group
Five regional CyberArk platforms (Vault, PSM and PSMP, CPM, PVWA, Credential Providers, HTML5 gateway, PTA) merged into a single platform on AWS. The target was built as code with GitHub and Terraform Enterprise, then run with L3 support, training and troubleshooting sessions with the vendor.
Self-hosted or SaaS, now that it's Idira?
Palo Alto Networks is clearly investing in the SaaS side of Idira, and some new capabilities arrive there first. That is a good reason to look at Privilege Cloud; it is not, on its own, a reason to move. Regulatory constraints on where vault data lives, the maturity of your operations team and your existing investments weigh just as much.
We give you a written comparison for your context, not a default answer.
Questions
Before you ask
Do we have to re-onboard every account?
No. Accounts, safes and permissions can be migrated with their metadata. We still recommend retiring dead accounts first: it's the cheapest moment to do it.
What happens to our session recordings?
They need a deliberate decision: kept on the old platform until their retention period ends, exported, or archived. We document it with your compliance team.
How long does a Privilege Cloud migration take?
It depends on the number of accounts, platforms and integrations. A single mid-sized platform moving to Privilege Cloud is a matter of months rather than weeks; consolidations run in waves over several quarters.
Can our team stay operational during the migration?
Yes. Old and new platforms run in parallel, perimeter by perimeter, with a rollback plan for each wave.
● Next step
Tell us about your vaultVersion, size, deadline. We will tell you straight away whether we are the right people for it.