CA Migration to AVX Native PKI
The migration enables organizations to adopt a more secure, modern platform that is Post-Quantum Cryptography (PQC) ready and aligned with evolving security and compliance requirements, ensuring that all certificate enrollment is routed through the AppViewX Enrollment Server with no client-side changes required. For ADCS migrations, the process includes pre-validation and permission checks, discovery of active MSCA instances, CA mapping, and creation of equivalent certificate templates in AppViewX, with key attributes such as EKU and KU preserved. The entire workflow features real-time progress tracking, validation checkpoints, and rollback guidance, with a step-by-step interface that allows users to resume from the last completed step.
Prerequisite
- CA policy must have only issuer-based configuration.
- RBAC configuration for PKI must be reconfigured.
- There must be no custodian or CA in the in-progress state.
- For on-premise deployments, the required settings must be configured. See Settings.
- You must have the CA Migration ACF permission assigned to your role.
Navigate to CA Migration
- Go to Menu, select PKI.
-
Select CA Migration.
The CA Migration page is displayed.
-
Select the migration type based on your source CA.
- Migrating from AVX Standard CA to AVX Native CA, see Migrating from AVX Standard CA to AVX Native CA.
- Migrating from MS ADCS to AVX Native CA, see Migrating from MS ADCS to AVX Native CA.
-
Follow the step-by-step migration wizard to complete the migration.
The wizard supports resuming from the last completed step if the migration is interrupted.
ACF Permissions Required
| Permission | Description |
|---|---|
| View | Users can view and access the CA Migration page. |
| Add/Modify | Users can start, resume, and manage CA migration
workflows. Note: Enabling CA Migration Add/Modify
permissions also automatically enables Resource
Add/Modify permissions. |
