Skip to content

Update messaging for Migrations and Modernization and detail of engagement #247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
brianamarie wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update messaging for Migrations and Modernization and detail of engagement #247

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4919338
Settle Migration and Modernization as Percona + HexaCluster combined …
brianamarie Jul 23, 2026
44d3594
Tighten Migration and Modernization Option B copy after review.
brianamarie Jul 23, 2026
94e1ada
Clarify Mongo path ownership and tooling automation claims.
brianamarie Jul 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _sidebar.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
- [Expert Support](/offerings/expert-support/messaging.md)
- [ExpertOps](/offerings/expertops/messaging.md)
- [Expert Consulting and Services](/offerings/expert-consulting/messaging.md)
- [Database modernization and migration](/offerings/migration-program/messaging.md)
- [Migration and Modernization](/offerings/migration-program/messaging.md)
- [Solution bundles](/offerings/solution-bundles/messaging.md)

- Products
Expand Down
6 changes: 3 additions & 3 deletions offerings/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Percona offers complementary ways to meet customer needs across the full lifecyc
- **[Expert Support](expert-support/messaging.md)** is *reactive and advisory*: customers own execution, and Percona engineers respond when issues or questions arise.
- **[ExpertOps](expertops/messaging.md)** is *proactive and operational*: a flexible partnership where Percona engineers handle the parts of day-to-day database operations customers want support with, ranging from full operational ownership to shared workflows or targeted help with high-risk tasks.
- **[Expert Consulting and Services](expert-consulting/messaging.md)** are *proactive and project-based*: Percona experts help teams plan and execute complex, high-impact work such as architecture decisions, deep performance tuning, and scoped project delivery at the level of involvement the customer needs.
- **[Database modernization and migration](migration-program/messaging.md)** is the capability home for legacy exit and modernization programs, including **PACE** (Percona Assisted Cutover Engine). Buyers contract with Percona; delivery runs through Consulting and the HexaCluster partnership.
- **[Migration and Modernization](migration-program/messaging.md)** is the capability home for legacy exit and modernization programs. For proprietary exits such as Oracle to PostgreSQL, Percona partners with HexaCluster in one offer. Customers contract with Percona for the full engagement; a migration software license is part of that engagement when the path uses migration tooling.

## Which offering?

Expand All @@ -20,7 +20,7 @@ The main fork is **who runs day-to-day database operations**:
- **Your team executes**: [Expert Support](expert-support/messaging.md): Percona guides; you operate production.
- **Percona executes in your environment**: [ExpertOps](expertops/messaging.md): hands-on operational partnership.

Add **[Expert Consulting and Services](expert-consulting/messaging.md)** for bounded projects (architecture, deep tuning, scoped delivery) alongside either steady-state offering. When the buyer need is **legacy exit or modernization to open source**, use **[Database modernization and migration](migration-program/messaging.md)** (capability language and **PACE** program naming). **[Solution bundles](solution-bundles/messaging.md)** package Consulting + Support for known buyer moments when fixed scope fits; they are not ExpertOps subscriptions.
Add **[Expert Consulting and Services](expert-consulting/messaging.md)** for bounded projects (architecture, deep tuning, scoped delivery) alongside either steady-state offering. When the buyer need is **legacy exit or modernization to open source**, use **[Migration and Modernization](migration-program/messaging.md)**. **[Solution bundles](solution-bundles/messaging.md)** package Consulting + Support for known buyer moments when fixed scope fits; they are not ExpertOps subscriptions.

Percona also offers **database training** as a complementary service. Training builds in-house skill; it is not a substitute for ExpertOps operational coverage or Expert Support for production incidents.

Expand All @@ -42,7 +42,7 @@ When the need is a defined outcome on fixed scope with Consulting and Support pa
| [expert-support/messaging.md](expert-support/messaging.md) | Expert Support positioning |
| [expertops/messaging.md](expertops/messaging.md) | ExpertOps positioning |
| [expert-consulting/messaging.md](expert-consulting/messaging.md) | Expert Consulting and Services positioning |
| [migration-program/messaging.md](migration-program/messaging.md) | Database modernization and migration capability; PACE program naming |
| [migration-program/messaging.md](migration-program/messaging.md) | Migration and Modernization; Percona + HexaCluster for proprietary exits; Percona-wrapped contracting |
| [solution-bundles/messaging.md](solution-bundles/messaging.md) | Packaged Consulting + Support bundles |

Engine-specific Support or Consulting scope (extensions, compatibility boundaries, advisory add-ons) belongs under `products/{engine}/`, not in offering files here. Offering files describe how Support, ExpertOps, and Consulting work across all supported engines.
Expand Down
4 changes: 2 additions & 2 deletions offerings/expert-consulting/messaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ Consulting is project-based and time-boxed. It complements steady-state [Expert

## Common scenarios

- **Migrations and upgrades:** Planned version, platform, or topology changes when source, target, and timing are largely set; delivered as defined projects with planning and hands-on execution where scoped.
- **Legacy exit and lifecycle transitions:** When license, vendor, or EOL pressure drives the case and teams are unsure of the right path, assessment scopes migration, modernization, EOL planning, or Extended Lifecycle Support (ELS). Percona delivers scoped work directly or through **PACE**, where Percona coordinates the engagement and HexaCluster delivers migration software and specialist services; customers contract with Percona only. Optional post-migration Expert Support follows cutover.
- **Migrations and upgrades:** Planned version, platform, or topology changes when source, target, and timing are largely set; delivered as defined projects with planning and hands-on execution where scoped. When End of Life (EOL) timing drives the case, assessment can also scope Extended Lifecycle Support (ELS) alongside the upgrade or migration path.
- **Legacy exit and modernization:** When license, renewal, or vendor pressure drives a move to open source targets, assessment scopes how complex the move is for the chosen target. Percona delivers scoped work directly or through a **Migration and Modernization** engagement with the Percona + HexaCluster partnership for proprietary exits such as Oracle to PostgreSQL. The customer contracts with Percona for the full engagement. Optional post-migration Expert Support follows cutover.
- **Assessments:** Structured health, performance, security, or compliance reviews with clear recommendations and deliverables.
- **Architecture and modernization:** Major design decisions and modernization paths across cloud, on-premises, hybrid, and Kubernetes environments.
- **Deep performance work:** Schema, query, configuration, and scaling work when bottlenecks or unclear storage and query behavior exceed advisory support scope.
41 changes: 20 additions & 21 deletions offerings/migration-program/messaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,36 +1,34 @@
# Database modernization and migration
# Migration and Modernization

**Assessment-led programs from evaluation to production. One Percona team, open source targets, support after go-live.**
**Assessment-led programs from evaluation to production. One Percona engagement, open source targets, support after go-live.**

@barrettch barrettch Jul 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are "assessment-led programs"? This reads like an invented phrase.

I think the point is to say that our experts evaluate migration feasibility and difficulty using tooling and expertise to provide practical migration guidance. For those that are a fit, we're connected the entire time through assessment, execution, hypercare, and ExpertSupport.

IMO, if this is top-level messaging, we should be more specific. As we use this with prompts further down the line, we can target specific audiences or types of collateral and filter this more specific messaging down to things like "evaluation to production".


Legacy and proprietary database estates drive renewal pressure, license drag, and operational risk. Percona helps teams assess exit paths, migrate or modernize to open source targets, and stabilize production after cutover with Expert Support on the destination environment.
Percona delivers Migration and Modernization as one accountable engagement from assessment through cutover, hypercare, and Expert Support. Percona stays present for the full journey, not only the conversion step.

@mmnosek mmnosek Jul 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that, maybe a slight fine-tuning suggestion: "Percona guides you through the whole journey to open source, not only the conversion step. "

This is to higlight that we are a partner that enable your entire organization to move to open source and the conversion is just a one of those steps if that makes sense.

@barrettch barrettch Jul 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd just cut the second sentence. It's redundant, essentially repeating the first sentence but with vague, overused marketing phrases.

Or, if we're trying to challenge, name the specific thing we're challenging. It seems like we're vaguely alluding that other vendors only do the conversion step - is that true?


Large heterogeneous exits and multi-phase modernization need accountable delivery from first assessment through post-migration support. Percona runs that work through **PACE**.
When teams need to leave a proprietary estate, especially Oracle for PostgreSQL, Percona partners with HexaCluster so migration expertise, project management, and support after go-live come together in one offer. Usual destinations are PostgreSQL, MySQL, and MariaDB.

## PACE program
Customers contract with **Percona** for the full program. It is transparent that a migration software license is part of the Percona engagement.

**PACE** (Percona Assisted Cutover Engine) is Percona's structured program to help customers migrate proprietary database workloads, such as Oracle or SQL Server estates, to open source alternatives quickly and safely. PostgreSQL is the most common target; MySQL and MariaDB are in scope where assessment confirms the fit.
Legacy and proprietary database estates drive renewal pressure, license drag, and operational risk. Percona helps teams assess exit paths, migrate or modernize to open source and source-available targets including the database and application layer, and stabilize production after cutover with Expert Support on the destination environment.

PACE packages assessment, migration execution, cutover, and post-migration support into one accountable engagement. Customers contract with Percona only. Percona coordinates the full program, including partner migration software and specialist services, so buyers have one relationship for transformation to open source.
Large heterogeneous migrations and multi-phase modernization need accountable delivery from first assessment through post-migration support. Percona runs complex proprietary exits through **PACE**, the in-program methodology for those Migration and Modernization engagements.

**Delivered by Percona**
## What the engagement covers

- Assessment coordination, scoping, and accountable program delivery through [Percona Expert Consulting and Services](../expert-consulting/messaging.md)
- Optional design and setup of target open source environments
- [Expert Support](../expert-support/messaging.md) on the destination stack after go-live
One accountable Percona engagement covers:

**Delivered by HexaCluster through the partnership**
1. **Proprietary database estate assessment** that confirms feasibility, the scope of required changes (including non-automated work), project cost, and the cost of supporting the destination estate after migration
2. **Migration execution**, including automated schema migration with validation after conversion, reliable data migration, live replication with change data capture (CDC), application-layer modernization, and cutover
3. **Training and enablement** for teams operating the destination environment
4. **Post-cutover hypercare** to stabilize the destination estate through the critical period after go-live
5. **Post-migration 24×7 Expert Support** on the destination stack

- Migration software and tooling, including HexaRocket
- Professional services for schema and code conversion, compatibility remediation, validation, and cutover execution
- Project management and coordination during the migration

Senior architecture and target-environment tuning may be delivered by Percona, HexaCluster, or both teams depending on project scope.
Tooling automates what it can; consulting covers the non-automated work the estate still requires. Teams get one accountable path from assessment through cutover, hypercare, and support, instead of stitching separate migration vendors, licenses, and post-cutover coverage.

## Focus migration paths

Assessment confirms source, target, and deployment model. Common PACE paths include:
Source and target are typically chosen before assessment begins. Assessment confirms feasibility, change scope, project cost, and post-migration support cost for that path. Common paths include:

@mmnosek mmnosek Jul 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think saying that source and target are chosen before the assessment is misleading. I would remove that first sentence and just start with "Assessment". Source is always there for years, and the prospect comes to us with the target rpetty much all the time. We don't choose it for them in practice.


| Source | Open source targets |
| Source | Common targets |
| --- | --- |
| Oracle | PostgreSQL, MariaDB |
| SQL Server | PostgreSQL |
Expand All @@ -40,7 +38,8 @@ Assessment confirms source, target, and deployment model. Common PACE paths incl
| MySQL | PostgreSQL, MySQL |
| MariaDB | PostgreSQL, MariaDB |
| Cassandra | PostgreSQL |
| MongoDB Atlas / Enterprise Advanced | Percona Server for MongoDB |

@mmnosek mmnosek Jul 24, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is not the space to blend all migrations into one table or offering. It should be about engines (switching engines/technologies). MongoDB -> MongoDB doesn't fit here. If we get into a different hosting model/distribution, this table would be super, super long. (e.g., AWS Aurora -> Percona Server for MySQL, MySQL Enterprise Edition to Percona Server for MySQL, EDB Postgres to Percona Postgres, Crunchy Postgres to Percona Postgres - the list of combinations is endless).

We should stick to:

Oracle -> PostgreSQL, MariaDB
SQL Server -> PostgreSQL
MySQL -> PostgreSQL
MariaDB -> MySQL
Sybase -> PostgreSQL
DB2 -> PostgreSQL


Targets may run self-managed, on Percona software, or on supported managed database services across major cloud providers. Other source and target combinations may be feasible; assessment sets the path.
Targets may run self-managed, on Percona software, or on supported managed database services across major cloud providers. Other source and target combinations may be feasible; assessment sets scope for the agreed path. Same-engine and MongoDB paths are Percona consulting unless assessment says otherwise.

Cutover approaches target near-zero downtime where application and operational constraints allow. Migration tooling automates much of the move; consulting covers schema, compatibility, and validation work the estate still requires.
Cutover approaches target near-zero downtime where application and operational constraints allow.
2 changes: 1 addition & 1 deletion products/postgresql/messaging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Unlike license-restricted PostgreSQL offerings and proprietary DBaaS services, P
- Open source without compromise: The Percona Distribution for PostgreSQL consolidates trusted community components into one enterprise-validated package, eliminating the cost and complexity of proprietary add-ons. Türk Telekom eliminated licensing costs, cut query times substantially, and boosted customer satisfaction by delivering high availability and resilience across critical services with Percona Distribution for PostgreSQL.
- Open source Kubernetes automation: Percona Operator for PostgreSQL is a hard fork of Crunchy PGO with Percona-owned development and community-driven evolution, extending the same inspectable PostgreSQL stack to Kubernetes without a vendor-tied operator control plane. On upgrade, upstream Crunchy resources migrate automatically to the `upstream.pgv2.percona.com` API group so Percona and Crunchy operators can coexist during adoption and teams can move without re-architecting clusters.
- Migration clarity when PostgreSQL licensing or managed-service roadmaps change: Vendor bundles and subscription models evolve on timelines teams do not control. Percona publishes positioning on portable PostgreSQL software versus proprietary distributions and managed PostgreSQL stacks ([Percona Software for PostgreSQL](https://www.percona.com/postgresql/software)), which helps organizations compare options on cleared public materials and plan moves without proprietary APIs that trap operational state.
- Legacy RDBMS exit to PostgreSQL for TCO: Assessment-led database modernization and migration from proprietary and legacy commercial databases helps teams cut license spend on [Percona Distribution for PostgreSQL](https://www.percona.com/postgresql/software) through [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). MySQL, MariaDB, Oracle, and SQL Server to PostgreSQL are common heterogeneous modernization paths; Percona delivers schema migration, code conversion, data migration and continuous replication, schema and data validation, and cutover, with migration scope and downtime tolerance confirmed during assessment.
- Legacy RDBMS exit to PostgreSQL for TCO: Assessment-led database modernization and migration from proprietary and legacy commercial databases helps teams cut license spend on [Percona Distribution for PostgreSQL](https://www.percona.com/postgresql/software) through [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). MySQL, MariaDB, Oracle, and SQL Server to PostgreSQL are common heterogeneous modernization paths; Percona delivers schema migration, code conversion, data migration and continuous replication, schema and data validation, and cutover.

**Performance and Reliability at Scale**

Expand Down
12 changes: 7 additions & 5 deletions reference/canonical-naming.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,13 +31,15 @@ Percona’s paid program for security and stability updates after a database ver

Live web paths and legacy PDFs may still say post-EOL support until commercial assets are updated. Canonical messaging in this repo should use **Extended Lifecycle Support (ELS)** so future edits do not drift back to deprecated program names.

## PACE and migration program naming
## Migration and Modernization naming

- **Capability:** Database modernization and migration
- **Program:** PACE (Percona Assisted Cutover Engine)
- **Partner:** HexaCluster (migration software and services; customers contract with Percona)
- **Public frame:** Migration and Modernization
- **HexaCluster:** Named for proprietary exits such as Oracle to PostgreSQL (usual destinations PostgreSQL, MySQL, MariaDB); do not imply Hexa covers every path in the tables
- **Contracting:** Customer contracts with Percona; transparent that a migration software license is part of the Percona engagement when tooling applies
- **Methodology:** PACE (one in-program mention on the offering page; program name not locked)
- **Do not name:** HexaRocket on public web

Full copy blocks: [migration-program/messaging.md](../offerings/migration-program/messaging.md).
Full copy: [migration-program/messaging.md](../offerings/migration-program/messaging.md).

## Community program naming

Expand Down
Loading
Loading