Migration to PostgreSQL
Many organisations want to reduce Oracle licensing costs or escape lock-in around RAC, Data Guard, RMAN & OEM. Others are moving away from SQL Server, MySQL or MariaDB as part of a cloud-first strategy. Whatever your starting point, PostgreSQL is a proven destination.
Kangaroot has deep expertise in both Oracle & PostgreSQL. We make migrations predictable, controlled & low-risk.
Why organisations migrate
- Rising Oracle licensing costs (CPU, options, packs)
- Complex compliance audits & unpredictable cost increases
- Lock-in around RAC, Data Guard, RMAN, OEM, OLVM
- Cloud-first strategies incompatible with proprietary constraints
- Desire for open source flexibility & long-term independence
What we deliver
Every migration starts with a clear picture of what you have & what it will take:
- Assessment report & high-level summary
- Migration plan & risk analysis
- Cost reduction analysis
- Schema conversion & query rewriting (PL/SQL → PL/pgSQL)
- Data integrity validation
- HA/DR redesign (Patroni, BaRMAN, pgBackRest, streaming replication)
- Performance tuning post-migration
- Execution, validation & operational handover
- Optional 24/7 support via Kangarun
Three migration pathways
-
Oracle → PostgreSQL (native)
Schema conversion, PL/SQL → PL/pgSQL rewriting, performance tuning & HA/DR redesign. The cleanest long-term path; full independence from proprietary tooling.
-
Oracle → EPAS (EDB Postgres Advanced Server)
Oracle compatibility mode for minimal code changes. Enterprise features including data masking (TDE), auditing & password policies. The right choice when rewriting isn't feasible short-term.
-
Hybrid approach
Some workloads on PostgreSQL, some on EPAS, unified monitoring & operations. For organisations that need a phased transition without a hard cutover.
Proof
Smals, the Belgian nonprofit ICT organisation behind +320 government institutions, has migrated nearly 4500 databases away from Oracle. Kangaroot was part of that story.
FAQ
-
Can we migrate without downtime?
Yes. We plan migrations in phases, production workloads keep running while the migration happens. The approach depends on your architecture & risk tolerance; we map that out in the assessment.
-
How long does a migration take?
It depends on complexity, volume & the pathway chosen. A focused assessment gives you a realistic timeline before any commitment.
-
Do you support migrations from SQL Server or MySQL too?
Yes. Oracle is the most common source, but we handle migrations from SQL Server, MySQL & MariaDB as well.
-
What happens after the migration?
Operational handover is part of every engagement. If you want us to keep running it, Kangarun takes over from there.