Add Optimized TCO legacy migration use case (heterogeneous paths)#177
Open
brianamarie wants to merge 13 commits into
Open
Add Optimized TCO legacy migration use case (heterogeneous paths)#177brianamarie wants to merge 13 commits into
brianamarie wants to merge 13 commits into
Conversation
Put migration detail in cost-optimization use cases (generic commercial sources, homogeneous/heterogeneous targets, Percona-led engagement with specialized tooling). Keep Expert Consulting to one common scenario bullet and align PostgreSQL TCO copy without naming competitors or partners. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
{ |
Contributor
New File Governance CheckNo added markdown files detected. Doc Coverage CheckNo new markdown docs detected. Manual waiver commands (maintainers)
Waiver JSON is stored in a hidden PR comment ( Triggered by |
Contributor
Messaging Smart Suggestions
Only auto-apply suggestions at high confidence with reviewer approval. Triggered by |
janwieremjewicz
previously approved these changes
Jun 3, 2026
janwieremjewicz
left a comment
janwieremjewicz
left a comment
There was a problem hiding this comment.
Other than the 3 comments it looks good to me. None of these seems to be a blocker TBH, more stylistic and ensuring that the narrowing of scope is on purpose.
brianamarie
commented
Jun 3, 2026
|
|
||
| - **Legacy and proprietary database migration to open source:** Renewal pressure on proprietary or legacy commercial databases drives moves to open source without new lock-in. | ||
| - **Sources:** Commercial proprietary RDBMS, commercial MySQL and MariaDB providers, other commercial PostgreSQL distributions, and other legacy commercial engines when assessment confirms a path. | ||
| - **Homogeneous and heterogeneous targets:** Open source PostgreSQL, MySQL, or MariaDB (Community) per Percona's MariaDB scope. **Homogeneous** paths stay within one engine family (e.g. on-prem to cloud on the same stack). **Heterogeneous** paths move legacy or proprietary engines to those targets. Proprietary-to-PostgreSQL paths are common; source-target pairs vary by estate. |
Collaborator
Author
There was a problem hiding this comment.
@brianamarie todo add in detail with Hexarocket and Hexacluster as enablers of this capability
brianamarie
added
Content & messaging
Contributor
Markdown hygiene auto-fixApplied safe markdown hygiene fixes and pushed one bot commit to this PR branch. Fixed files:
Triggered by |
brianamarie
commented
Jun 4, 2026
| - 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. | ||
| - 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: Teams exiting proprietary or legacy RDBMS footprints can reduce license and support spend by landing on Percona Distribution for PostgreSQL with assessment-led migration through [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope and source-to-target patterns are confirmed during assessment. | ||
| - Legacy RDBMS exit to PostgreSQL for TCO: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment. |
Collaborator
Author
There was a problem hiding this comment.
Suggested change
| - Legacy RDBMS exit to PostgreSQL for TCO: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment. | |
| - Legacy database to PostgreSQL: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope confirmed at assessment. |
…scope. Lou approved naming HexaCluster and HexaRocket once in the Optimized TCO engagement model, with heterogeneous proprietary-to-open-source language elsewhere. Covers sources, targets, and Oracle to PostgreSQL across the supported stack including MongoDB-compatible and Valkey paths. Co-authored-by: Cursor <cursoragent@cursor.com>
thefactremains
left a comment
thefactremains
left a comment
Member
There was a problem hiding this comment.
Review: comment only. Verified against gh pr diff 177 (4 files: use-cases-value-pillars/cost-optimization.md, offerings/expert-consulting.md, products/postgresql/messaging.md, use-cases-value-pillars/README.md). The TCO legacy-migration content reads well. Two items to consider before merge.
-
(Nit, likely CI) The additions use "proprietary-to-open-source" in several places (
offerings/expert-consulting.md,products/postgresql/messaging.md, anduse-cases-value-pillars/cost-optimization.md). Repo rule: "open source" is never hyphenated, and the ValeOpenSourceHyphenrule will likely report it. Suggest rewording, for example "from proprietary engines to open source." -
(Should-fix) The new legacy-migration use case in
use-cases-value-pillars/cost-optimization.mdnames HexaCluster and HexaRocket plus third-party marks (Oracle, SQL Server, EDB, MongoDB, Sybase, DB2, SAP HANA, Redis), butNOTICES.mdis not updated. NOTICES currently lists Oracle, MySQL, MongoDB, and Redis, so SQL Server, EDB, Sybase, DB2, SAP HANA, HexaCluster, and HexaRocket are not attributed. The HexaCluster and HexaRocket names were added in a later commit (cd29b7f) and are listed under "Out of scope / gating" in the PR description, so the description and the copy disagree. Perreference/brand-voice.md, confirm whetherNOTICES.mdneeds these trademarks added, record the HexaCluster and HexaRocket naming approval in the PR, and reconcile the description with the copy.
Surface schema conversion, real-time sync, and validation across cost pillar, PostgreSQL messaging, and Expert Consulting so high-intent heterogeneous paths are explicit. Co-authored-by: Cursor <cursoragent@cursor.com>
mmnosek
reviewed
Jun 12, 2026
|
|
||
| - **Migrations and upgrades:** Complex or high-risk moves delivered as defined projects, including planning and hands-on execution where scoped. | ||
| - **Legacy RDBMS migration to open source:** Assessment-led projects when license, support, or vendor roadmap risk drives the case. Source-to-target combinations and execution depth are scoped and quoted after assessment, not assumed for every engine pair. | ||
| - **Legacy migration to open source:** Assessment-led moves when license drag or vendor risk drives open source targets. Percona leads assessment and scoping; customers contract with Percona. Heterogeneous paths (including MySQL, MariaDB, Oracle, and SQL Server to PostgreSQL) may include partner migration tooling for schema conversion, real-time replication, and automated data validation together with Percona Expert Consulting, after assessment. |
There was a problem hiding this comment.
I don't think it's necessary to state that "customers contract with Percona"
There was a problem hiding this comment.
If this is meant for a human audience, this sentence needs to be rewritten: "Assessment-led moves when license drag or vendor risk drives open source targets. " e.g. to Assessment-led projects where license cost or vendor lock-in drives modernization to open source database stack." or similar.
| - 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. | ||
| - 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: Teams exiting proprietary or legacy RDBMS footprints can reduce license and support spend by landing on Percona Distribution for PostgreSQL with assessment-led migration through [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). Scope and source-to-target patterns are confirmed during assessment. | ||
| - Legacy RDBMS exit to PostgreSQL for TCO: From proprietary and legacy commercial databases, teams cut license spend on Percona Distribution for PostgreSQL via assessment-led [Percona Expert Consulting and Services](https://www.percona.com/services/consulting). MySQL, MariaDB, Oracle, and SQL Server to PostgreSQL are common heterogeneous motions; assessment confirms application SQL scope, cutover approach, and tooling fit for schema conversion, real-time synchronization, and pre-cutover data validation. |
There was a problem hiding this comment.
I think "application SQL scope" is inaccurate. Assessment confirms migration scope. In the same line, we don't need to confirm tooling fit for schema conversion. It sounds like we are not sure if we can do that, which is not true, and neither is it good as a public messaging.
There was a problem hiding this comment.
In addition to that, we're missing important items. The actual list of what we take care of:
- Schema migration
- Code conversion
- Data migration and continuous replication
- Schema and data validation
- Cutover
| - **Database variation is the norm:** Most organizations run more than one database engine. Analyst research from [Gartner on polyglot persistence and data-architecture complexity](https://www.gartner.com/en/articles/reduce-your-data-architecture-complexity-with-polyglot-persistence), [Thoughtworks](https://www.thoughtworks.com/radar/techniques/polyglot-persistence), and the [Data on Kubernetes community](https://www.redhat.com/en/engage/state-kubernetes-security-report-2024) shows a clear shift toward polyglot data environments, with teams operating multiple databases side by side to serve different workloads. | ||
| - **Operational sprawl increases overhead:** Multiple monitoring systems, backup tools, and vendor SLAs mean more people, tickets, and handoffs. [Liquibase reports](https://www.liquibase.com/blog/why-financial-services-leaders-are-re-evaluating-open-source-for-database-change-management) that tool sprawl and lack of standardization increase deployment errors by up to 70%, translating directly into downtime, rework, and audit risk. | ||
| - **Proprietary license drag:** Commercial proprietary database licenses and legacy database contracts often dominate TCO through per-core licensing, mandatory support bundles, and audit exposure, even when infrastructure utilization is flat or falling. | ||
| - **Proprietary license drag:** Commercial proprietary and legacy database contracts dominate TCO through per-core licensing, support bundles, and audit exposure even when utilization is flat. |
There was a problem hiding this comment.
Since Percona has per-core support pricing available we should not talk about it that way.
| - **Transparent, usage-based pricing:** Percona solutions are scoped to real deployment needs and cost-optimization goals, not license math. Expert Support and ExpertOps Subscriptions scale with actual environment size, with no per-core pricing, license gates, or hidden fees. For defined projects such as migrations, architecture reviews, or performance assessments, Expert Consulting and Services engagements are offered with transparent estimates, with clear deliverables and predictable outcomes. | ||
| - **Licensing elimination:** $0 in database licensing. All software licenses are available to use for free under open source and source-available licenses. | ||
| - **Legacy database migration to open source:** When proprietary license and support costs drive the business case, [Percona Expert Consulting and Services](https://www.percona.com/services/consulting) helps teams migrate to open source alternatives with assessment-led scope, defined deliverables, and a lower long-term run-rate. | ||
| - **Legacy database migration to open source:** When license and support costs drive the case, [Percona Expert Consulting and Services](https://www.percona.com/services/consulting) delivers assessment-led migration to open source with a lower run-rate on Percona software and support. Heterogeneous moves (for example MySQL, MariaDB, Oracle, or SQL Server to PostgreSQL) may combine Expert Consulting with partner migration tooling for schema conversion, real-time replication, and automated data validation after assessment confirms fit. |
There was a problem hiding this comment.
Not sure we should highlight the fact it may contain partner migration tooling.
|
|
||
| ### Use cases | ||
|
|
||
| - **Legacy and proprietary database migration to open source:** Licensing and renewal pressure on proprietary commercial databases pushes teams toward open source and source-available alternatives. Percona delivers assessment-led planning and production-minded execution across MySQL, MariaDB Community, PostgreSQL, MongoDB-compatible workloads, Valkey, and Redis. |
There was a problem hiding this comment.
MongoDB-compatible sounds like we have some non-MongoDB (just API compatible) database that we provide. It shouldn't be treated differently than MySQL.
Why we specifically talk about MariaDB Community? In general, are those target databases that we aim to list here?
| ### Use cases | ||
|
|
||
| - **Legacy and proprietary database migration to open source:** Licensing and renewal pressure on proprietary commercial databases pushes teams toward open source and source-available alternatives. Percona delivers assessment-led planning and production-minded execution across MySQL, MariaDB Community, PostgreSQL, MongoDB-compatible workloads, Valkey, and Redis. | ||
| - **Homogeneous vs heterogeneous paths:** Same-engine moves (for example, on-premises to cloud on one stack) differ from replatforming across engine families. Heterogeneous proprietary-to-open-source work needs different scope, tooling, and timeline than lift and shift within one database. |
There was a problem hiding this comment.
One thing to consider would be to talk about homogenous as "migration" and heterogenous as "modernization" .
|
|
||
| - **Legacy and proprietary database migration to open source:** Licensing and renewal pressure on proprietary commercial databases pushes teams toward open source and source-available alternatives. Percona delivers assessment-led planning and production-minded execution across MySQL, MariaDB Community, PostgreSQL, MongoDB-compatible workloads, Valkey, and Redis. | ||
| - **Homogeneous vs heterogeneous paths:** Same-engine moves (for example, on-premises to cloud on one stack) differ from replatforming across engine families. Heterogeneous proprietary-to-open-source work needs different scope, tooling, and timeline than lift and shift within one database. | ||
| - **Common sources:** Oracle, SQL Server, commercial PostgreSQL (including EDB estates with Oracle compatibility), commercial MySQL and MariaDB, MongoDB Atlas and Enterprise Advanced, Sybase, DB2, SAP HANA, Redis, and other legacy platforms. |
There was a problem hiding this comment.
Redis Enterprise, Oracle MySQL Enterprise Edition, MariaDB Enterprise (since we call out details of MongoDB, as an example)
| - **Legacy and proprietary database migration to open source:** Licensing and renewal pressure on proprietary commercial databases pushes teams toward open source and source-available alternatives. Percona delivers assessment-led planning and production-minded execution across MySQL, MariaDB Community, PostgreSQL, MongoDB-compatible workloads, Valkey, and Redis. | ||
| - **Homogeneous vs heterogeneous paths:** Same-engine moves (for example, on-premises to cloud on one stack) differ from replatforming across engine families. Heterogeneous proprietary-to-open-source work needs different scope, tooling, and timeline than lift and shift within one database. | ||
| - **Common sources:** Oracle, SQL Server, commercial PostgreSQL (including EDB estates with Oracle compatibility), commercial MySQL and MariaDB, MongoDB Atlas and Enterprise Advanced, Sybase, DB2, SAP HANA, Redis, and other legacy platforms. | ||
| - **Common targets:** Open source PostgreSQL, MySQL, and MariaDB Community for cross-engine moves; Percona Server for MongoDB for MongoDB-compatible workloads; Valkey for teams leaving proprietary Redis offerings. |
There was a problem hiding this comment.
I would avoid using "MongoDB-compatible workloads." Why MongoDB is in a different "category" than Postgres/MySQL/MariaDB?
| - **Common sources:** Oracle, SQL Server, commercial PostgreSQL (including EDB estates with Oracle compatibility), commercial MySQL and MariaDB, MongoDB Atlas and Enterprise Advanced, Sybase, DB2, SAP HANA, Redis, and other legacy platforms. | ||
| - **Common targets:** Open source PostgreSQL, MySQL, and MariaDB Community for cross-engine moves; Percona Server for MongoDB for MongoDB-compatible workloads; Valkey for teams leaving proprietary Redis offerings. | ||
| - **Engagement and partnership:** Customers contract with Percona. Percona leads assessment and scoping. For selected heterogeneous proprietary-to-open-source paths, Percona partners with HexaCluster and may use HexaRocket, HexaCluster's multi-source, multi-target migration platform, together with [Percona Expert Consulting and Services](https://www.percona.com/services/consulting), after assessment confirms fit. HexaRocket automates schema conversion, real-time replication from sources including MySQL, MariaDB, Oracle, and SQL Server, and pre-cutover data validation so teams reduce manual refactor risk and can pursue near-zero-downtime cutovers where application and operational constraints allow. | ||
| - **MySQL and MariaDB to PostgreSQL:** A frequent heterogeneous motion when commercial MySQL licensing, Oracle MySQL 8.0 EOL pressure, or PostgreSQL consolidation drives replatforming. Assessment covers stored routines and triggers, charset and collation mapping, application SQL rewrite scope, and acceptable cutover downtime. Where tooling fit is confirmed, delivery may synchronize live workloads to [Percona Distribution for PostgreSQL](https://www.percona.com/postgresql/software) with schema conversion and validation before cutover. |
There was a problem hiding this comment.
I think MySQL 8.0 EOL pressure is not a reason for anyone to move to PostgreSQL, at least not a pattern. Software goes EOL all the time, actually. Postgres has a more aggressive EOL policy than MySQL LTS versions.
| - **Common targets:** Open source PostgreSQL, MySQL, and MariaDB Community for cross-engine moves; Percona Server for MongoDB for MongoDB-compatible workloads; Valkey for teams leaving proprietary Redis offerings. | ||
| - **Engagement and partnership:** Customers contract with Percona. Percona leads assessment and scoping. For selected heterogeneous proprietary-to-open-source paths, Percona partners with HexaCluster and may use HexaRocket, HexaCluster's multi-source, multi-target migration platform, together with [Percona Expert Consulting and Services](https://www.percona.com/services/consulting), after assessment confirms fit. HexaRocket automates schema conversion, real-time replication from sources including MySQL, MariaDB, Oracle, and SQL Server, and pre-cutover data validation so teams reduce manual refactor risk and can pursue near-zero-downtime cutovers where application and operational constraints allow. | ||
| - **MySQL and MariaDB to PostgreSQL:** A frequent heterogeneous motion when commercial MySQL licensing, Oracle MySQL 8.0 EOL pressure, or PostgreSQL consolidation drives replatforming. Assessment covers stored routines and triggers, charset and collation mapping, application SQL rewrite scope, and acceptable cutover downtime. Where tooling fit is confirmed, delivery may synchronize live workloads to [Percona Distribution for PostgreSQL](https://www.percona.com/postgresql/software) with schema conversion and validation before cutover. | ||
| - **Oracle to PostgreSQL:** A frequent heterogeneous motion when proprietary licensing or support costs dominate TCO. Assessment confirms compatibility-mode SQL scope, data-type mapping, and downtime tolerance. Tooling fit and execution depth are scoped during assessment. |
There was a problem hiding this comment.
Not sure what "compatibility-mode SQL scope" is.
Percona-led migration and modernization copy with workload-led guidance, ELS options, and HexaCluster on selected heterogeneous paths. Removes HexaRocket and partner-forward hedging; adds qualified near-zero downtime wording for Avi review. Co-authored-by: Cursor <cursoragent@cursor.com>
Surfaces Michal's full delivery list (schema migration through cutover) in Expert Consulting and PostgreSQL TCO messaging, aligned with the cost pillar. Co-authored-by: Cursor <cursoragent@cursor.com>
Resolve conflicts in use-cases-value-pillars/README.md and use-cases-value-pillars/cost-optimization.md. Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
Author
|
/impact-ok all |
Contributor
|
🤖 Recorded |
Contributor
Messaging Impact Check
postgres-cost-claim (WARN)PostgreSQL cost/TCO claims usually impact shared value proof messaging. Required review files:
Suggested additional scan:
licensing-or-open-source-claims (WARN)License and open source positioning changes are cross-cutting. Required review files:
Suggested additional scan:
offering-name-or-tier-change (WARN)Offering naming updates should stay aligned across offering pages. Required review files:
Suggested additional scan:
product-messaging-module-touch (WARN)Product messaging modules often need checks against company framing and shared pillars or offerings. Required review files:
Suggested additional scan:
Manual waiver commands (maintainers):
Waiver state is stored in Triggered by |
…ilable Vale rule Percona.PSMDBOpenSource blocked the migration targets line for pairing "open source" with Percona Server for MongoDB. Clarify SSPL/source available inline while keeping the open source framing for PostgreSQL, MySQL, and MariaDB. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Out of scope / gating
NOTICES.mdchanges.Made with Cursor