Plan your migration
Before beginning a migration, review the planning guidance for your deployment type and infrastructure requirements.
Plan your migration from RPM-based to operator-managed Ansible Automation Platform
Migrate your Ansible Automation Platform RPM 2.6 deployment to an operator-managed deployment on OpenShift Container Platform using the ansible.aap_snapshot collection.
The ansible.aap_snapshot collection is version-locked: the source deployment and the OpenShift Container Platform target must be running the same Ansible Automation Platform version. If your source deployment is RPM 2.4 on RHEL 8, review your options before continuing.
Route: RPM 2.4 (RHEL 8) → RPM 2.4 (RHEL 9) → RPM 2.6 (RHEL 9) → OCP 2.6 (using ansible.aap_snapshot)
Infrastructure requirement: New RHEL 9 hosts are required for the intermediate RPM 2.4 state. You must transfer the backup archive from your RHEL 8 source hosts to the RHEL 9 target hosts before running the restore.
Update your Ansible Automation Platform 2.4 environment to the latest minor release before you begin. Earlier Ansible Automation Platform 2.4 versions shipped with PostgreSQL 13. You must upgrade your PostgreSQL database to version 15 before migration, or your backup and restore will fail.
Stage 1: Back up and restore
Back up your RPM 2.4 deployment on RHEL 8 and restore it onto new RHEL 9 hosts running RPM 2.4.
Stage 2: Upgrade
Upgrade from RPM 2.4 to 2.6 on the RHEL 9 hosts. For more information, see the upgrade documentation for RPM deployments.
Stage 3: Migrate
Use the ansible.aap_snapshot collection to migrate from RPM 2.6 on RHEL 9 to OpenShift Container Platform.
Completing this migration also prepares your environment for future upgrades. RPM-based deployments are not a supported upgrade path to Ansible Automation Platform 2.7.