Migrate off Crunchy PostgreSQL, on your own timeline

Percona gives you a clear, tested path off Crunchy PostgreSQL Operator and on-prem solution, with migration planning built into your support contract. No forced rush. No unsupported gap.

Talk to a migration engineer

Read the migration guide

Why Percona

1. You're not locked into one offering

We offer support for the two most reliable open source ways to run PostgreSQL on Kubernetes: Percona Operator for PostgreSQL and support for the CloudNativePG operator.

2. The Percona Operator is a hard fork of Crunchy's

Same Patroni for high availability, same pgBackRest for backups, same PgBouncer for connection pooling. The CRDs coexist in the same cluster during the move, so nothing is torn down before the new setup is proven. Read the announcement

3. Ansible compatibility

If your Crunchy deployment is wired into Ansible automation - Percona will help to save automation rather than redesign everything from scratch.

4. You don't have to migrate today to start planning today

Commit to support now and your migration planning plan is ready whenever you are. Most teams start the assessment months before they touch a production cluster.

What's included in migration support

PostgreSQL support on any environmentArchitecture reviewMigration design and planningOperator migration, Crunchy to Percona or CloudNativePGData movement, your choice of methodFailover and performance validation

The migration guide

Part 1 of 3

Migrate to Freedom: Choosing a Truly Open Source PostgreSQL Operator

Part 2 of 3

Migrate from Crunchy Data PostgreSQL Operator to Percona PostgreSQL Operator: Standby Cluster Method

Part 3 of 3

Migrate from Crunchy Data PostgreSQL Operator to Percona PostgreSQL Operator: Backup-Restore and PV Reuse

More on the migration

Comparing Migration Methods from the Crunchy Data PostgreSQL Operator to the Percona Operator for PostgreSQL

Support for Crunchy Hardened PostgreSQL Ends Soon: Don't Get Caught Off Guard

Percona Operator for PostgreSQL 3.0.0: Hard Fork, OLM Scoping, Major Upgrades

FAQs

Real Answers.
No Corporate Doublespeak.

Clear, direct answers about downtime, automation, pacing, and what the migration engagement actually covers.

Some downtime is typically involved, though it's minimal. Because the Percona Operator is a hard fork of Crunchy's, built on the same Patroni, pgBackRest, and PgBouncer components, the CRDs from both operators can coexist in the same cluster during the move — so failover and performance are validated before the old setup is torn down, keeping the cutover window as short as possible.

We help preserve it. If your Crunchy deployment is wired into Ansible, migration support includes carrying that automation forward rather than redesigning it from scratch.

No. Migration design and planning is part of the engagement, and most teams start the assessment months before touching a production cluster. You choose the data movement method and pace.

Migration support covers Crunchy PostgreSQL deployments broadly, not only the Hardened distribution. Talk to a migration engineer about your specific setup.

No. Talking to a Percona engineer about your Crunchy setup has no cost and no obligation to migrate before you're ready.

Plan your move before the sunset date forces it

Talk to a Percona engineer about your Crunchy setup. No cost, no obligation, and no pressure to migrate before you are ready.

Talk to our migration team

Contact

Talk to
a Percona Expert

Not ready to migrate yet? That’s fine. Tell us about your current Crunchy setup and we’ll help you understand your options, identify the risks, and build a migration plan before you need it.