Acquia sells managed hosting and tooling for Drupal through its Cloud Platform. Because Drupal is GPL, leaving Acquia means running the same Drupal codebase yourself or with another host.
Comparing Acquia Cloud Platform with running Drupal on your own servers, Kubernetes or another cloud: what Acquia manages today such as backups, environments and platform tooling, what moves to your team or a support partner, and which Acquia add-ons need replacements.
Moving a Drupal site off Acquia: taking database backups with the Acquia CLI and copying files separately, replicating environments and deployment pipelines, replacing Acquia-specific modules and settings, testing performance and cutting DNS over with a rollback plan.
Cost of ownership by component for Drupal on Acquia against self-hosting: the platform subscription and add-ons, against infrastructure, CDN, backups, security updates on Drupal's monthly release windows, upgrades such as Drupal 10 to 11, and the people who run them.
What to take before leaving Acquia: database backups from the interface or Acquia CLI, uploaded files that backups do not include, the codebase from your Git repository, configuration and environment settings, and a checklist to confirm the export restores cleanly elsewhere.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.