Some enterprise IT teams may think that they need to make a major decision when it comes to the future of their Oracle database estate by either staying entirely on Oracle or migrating everything to an entirely new system.
The good news is that they do not have to take an all-or-nothing approach. A selective modernization strategy can help organizations preserve what is stable and working in their Oracle systems today while introducing PostgreSQL for new or selected workloads. for new or selected workloads. This balanced approach enables organizations to optimize their current environment while modernizing at a pace that aligns with business priorities.
The Business Case for Selective Modernization
Selective modernization can improve the economics of the database estate without forcing a large-scale migration. Moving suitable workloads to Postgres can reduce proprietary licensing and support costs, freeing budget for other modernization priorities. A phased approach can also avoid the concentrated cost and complexity of migrating everything at once, including additional testing, training, tooling, and operating processes.
But the more important benefit may be flexibility. Operating a mixed Oracle and PostgreSQL environment allows organizations to preserve critical business operations while introducing new technology at a pace aligned with their priorities and readiness.
This approach can also provide greater architectural choice as the organization grows. Rather than relying on one vendor across the entire database estate, teams can select the platform that best fits each workload. However, realizing that value requires consistent governance, security, tooling, and operating standards across both environments.
Mixed database environments are already gaining traction. Redgate’s 2026 State of the Database Landscape, based on responses from more than 2,200 data professionals, found that 84 percent of organizations manage two or more database platforms and 31 percent manage four or more.
PostgreSQL can be a strong fit for selected workloads because it combines enterprise-grade capabilities with open-source flexibility. Organizations can support modern applications, cloud strategies, and AI workloads while reducing proprietary licensing constraints. Choosing a 100% open-source PostgreSQL platform also helps avoid replacing one form of vendor lock-in with another.
Getting Started: Postgres Candidates and Oracle Keepers
As a first step, start by evaluating what workloads should stay on Oracle, and what could be a good candidate for Postgres. What are the top criteria in the evaluation? Workload characteristics such as business criticality, feature and compatibility requirements, custom code, integrations, data volume, and the operational consequences of failure can all impact the decision of what stays on Oracle and what may be a strong candidate for Postgres.
Other factors include anticipated or required performance, availability, and security, as well as compliance requirements and implications. Again, this is a workload-by-workload decision and is not an enterprise-wide change.
Other Considerations: Skills, Talent and Timing
Selective modernization requires specific technical knowledge, both to make the evaluations and decisions above and to implement and operate Postgres across selected workloads. Without consistent governance, tooling, and operating standards, a mixed database environment can create new complexity rather than reduce it.
For example, Postgres requires experienced database professionals, with knowledge of monitoring, backup and recovery, performance tuning, governance, and security. In addition, enterprises will need a clear support model across planning, migration, optimization, and ongoing operations for their mixed Postgres/Oracle environment.
Execution: A Phased Approach that Protects the Oracle Estate
Using a phased execution approach will give IT teams time to test and monitor the progress of the migration along the way, while limiting risk and disruption to end users. Teams may begin with new workloads or contained proof points that are not customer-facing to see how the process goes and what challenges may arise that can be addressed proactively in future migrations. This is an opportunity to learn, share information, and then standardize. Later, teams can expand deliberately and effectively, drawing upon what they learned from earlier migration projects.
During migration, independent third-party support can help keep the Oracle environment stable. Instead of upgrading or renewing simply to maintain vendor support, organizations can continue running proven Oracle systems with expert support while selected workloads move to PostgreSQL. This gives IT teams room to focus on migration without putting business-critical Oracle operations at risk.
Spinnaker Support provides a bridge across the full journey, from evaluating the Oracle estate and identifying PostgreSQL candidates to migration, optimization, security, and 24/7 ongoing support. The result is a phased roadmap grounded in business priorities and technical requirements rather than vendor deadlines.
The Modernization Road Ahead
Modernization should expand options, not limit them. By evaluating Oracle and PostgreSQL workloads based on business value, technical fit, migration complexity, operational readiness, and risk, organizations can determine what to migrate and what should remain in place. From there, teams can build a phased plan that protects the current estate while using third-party expertise to close skills gaps and make future migrations more efficient and repeatable.
Start with an Oracle Estate Assessment to segment your estate and build a phased roadmap that protects stable Oracle operations.
