AAP 2.6 Migration from AWX: Complete Upgrade and Data Migration Guide
By Luca Berton · Published 2024-01-01 · Category: installation
Migrate from AWX to AAP 2.6 with zero data loss. Export inventories, credentials, job templates, workflows, and schedules. Architecture differences, licensing, feature gaps, and step-by-step migration playbooks.
Why Migrate from AWX to AAP?
AWX is the open-source upstream of AAP's Automation Controller. While AWX is free, AAP 2.6 provides enterprise features that AWX lacks:
| Feature | AWX | AAP 2.6 | |---------|-----|---------| | Support | Community only | Red Hat 24/7 support | | Platform Gateway | ❌ | ✅ Unified entry point | | Automation Hub | ❌ (Galaxy only) | ✅ Private Hub | | Event-Driven Ansible | ❌ | ✅ EDA Controller | | Automation Mesh | ❌ | ✅ Distributed execution | | Lightspeed AI | ❌ | ✅ AI-assisted automation | | Certified Content | ❌ | ✅ Red Hat certified collections | | FIPS compliance | ❌ | ✅ | | Multi-year lifecycle | No (rolling release) | ✅ 18-month support | | Subscription | Free | Managed Nodes or RPM |
Migration Planning
Pre-Migration Inventory
Document everything in AWX before migrating:
Migration Checklist • [ ] Export organizations • [ ] Export credentials (re-create — passwords don't export) • [ ] Export inventories (static and dynamic sources) • [ ] Export projects (SCM URLs and branches) • [ ] Export job templates (with surveys) • [ ] Export workflow templates (with topology) • [ ] Export schedules • [ ] Export notification templates • [ ] Export teams and user mappings • [ ] Document custom credential types • [ ] Document instance groups • [ ] Note any custom venvs → map to EEs
Export from AWX
Using awx CLI
Using Ansible Playbook
Import to AAP 2.6
Using awx CLI Import
Import via Playbook
Key Differences to Handle
Virtual Environments → Execution Environments
AWX uses Python virtual environments. AAP 2.6 uses container-based EEs:
Build equivalent EEs:
API URL Changes
| AWX | AAP 2.6 | |-----|---------| | /api/v2/ | /api/controller/v2/ (via Gateway) | | Direct controller URL | Gateway URL |
Update all API integrations, CI/CD pipelines, and scripts.
Instance Groups → Automation Mesh
AWX instance groups are container groups or local groups. AAP 2.6 uses Automation Mesh with Receptor for distributed execution.
Post-Migration Validation
FAQ
Can I run AWX and AAP side by side during migration?
Yes. Install AAP 2.6 on new infrastructure and migrate gradually. Keep AWX running until all templates are validated on AAP. Use a cutover date to switch DNS/integrations.
Will my AWX playbooks work on AAP?
Playbooks are 100% compatible. The differences are in the platform (API URLs, EEs vs venvs, Gateway), not the automation content. Your roles, playbooks, and collections work identically.
Do I need to re-enter all credentials?
Yes. Credential secrets don't export for security reasons. Prepare a vault file with all credential values before migration. Better yet, migrate to an external secret backend (HashiCorp Vault, CyberArk) during the move.
What about AWX job history?
Job history doesn't migrate. AAP starts with a clean job log. If you need historical records for compliance, export AWX job data to an external system before decommissioning.
Is there a direct database migration path?
No. AWX and AAP use different database schemas. The supported path is API-based export/import. Red Hat does not support direct database migration between AWX and AAP.
Conclusion
Migrating from AWX to AAP 2.6 is a structured process: export from AWX, recreate credentials, import to AAP, convert venvs to EEs, and validate. The automation content (playbooks, roles, collections) is fully compatible — only the platform configuration needs migration. Plan for a parallel run period and validate thoroughly before decommissioning AWX.
Related Articles • AAP 2.6 Architecture and Components: Complete Guide • AAP 2.6 Execution Environments: Build, Manage, and Deploy Custom EEs • AAP 2.6 REST API Guide: Automate the Automation Platform • AAP 2.6 Comparison: What Changed from AAP 2.5 • AAP 2.6 Credential Management: Vaults, External Secrets, and Machine Credentials
Category: installation