35+ YEARS IN MARKET
Continuously operating since 1990. 25,000+ consulting hours delivered and 596+ critical production incidents resolved. Pattern recognition only decades of real operation can build.
ORACLE → POSTGRESQL MIGRATION — SINCE 1990
Your app runs on Oracle Enterprise but uses 20% of its features. The rest is license burning $9k per core per year. PostgreSQL does 95% of the same, no royalty. We migrate without rewriting the application.
Oracle migrations delivered for
THE BUDGET THAT DOESN'T CLOSE
License rises 12% per year in USD
Oracle Enterprise + Partitioning + Diagnostic Pack + RAC. Each renewal hurts more. The exchange rate doesn't help. CFO has asked for license cuts twice already; IT hasn't answered.
Fear of breaking the application
PL/SQL with 200K lines. Triggers, packages, types, autonomous transactions. Nobody wants to be the person who rewrites it all. So it stays, paying.
Generic consulting doesn't really migrate
Runs a 10-table POC, invoices, leaves. Real migration is composite partitioning, sequences vs identity, NUMBER with scale, ROWNUM vs ROW_NUMBER. Details that sink the project.
HTI runs an honest assessment first
Before promising ROI, we run ora2pg in report mode on your schema. We deliver a report on what migrates automatically, what needs manual work, and what (perhaps) isn't worth migrating. No inflated proposal.
METHODOLOGY
We don't sell dreams. We sell predictability. Each phase delivers a concrete artifact: compatibility report, tested converted schema, PL/pgSQL with test coverage, rehearsed cutover plan.
Quantitative analysis of schema, tables, indexes, sequences, packages, triggers, types. Score of automatic compatibility vs manual work. ROI calculated in USD and local currency.
DDL translated with type mapping (NUMBER→NUMERIC, VARCHAR2→VARCHAR, DATE→TIMESTAMP), sequences, constraints and functional indexes. Git-versioned.
Packages, procedures and triggers converted with equivalent semantics. Replacement of non-1:1 features (autonomous transactions → dblink, sequences.NEXTVAL → nextval).
Oracle range/list/hash partitioning translated to PostgreSQL 11+ declarative partitioning. When native partition pays off, when an extension does (pg_partman).
Oracle→PostgreSQL replication with Debezium/GoldenGate/SymmetricDS during coexistence. Cutover rehearsed in a controlled window, with documented technical rollback.
Configured VACUUM/ANALYZE, autovacuum tuned per hot table, per-session work_mem, BRIN indexes for append-only, extended statistics. Optimized PostgreSQL, not default.
SPECIALISTS ON BOTH SIDES
Oracle→PostgreSQL migration only works with a team that masters Oracle deeply (knows what's leaving) AND PostgreSQL deeply (knows what's coming in). Rare. HTI has it.
A bad migration locks you into a PostgreSQL worse than the Oracle you had. We deliver an environment tuned for the scale you'll have in 3 years, not today's.
DELIVERED PROJECTS
PUBLIC AGENCY
Migration without rollback
Migration from Oracle 11g (12TB, 800+ tables, 300+ PL/SQL packages) to PostgreSQL 14 with Debezium and a 4h cutover. Annual savings: $850K in license.
TELECOM
RAC to Patroni
Exit from 4-node Oracle RAC to PostgreSQL HA with Patroni + etcd. Same availability SLA, a fraction of the cost, infrastructure running on Kubernetes.
FINTECH
From assessment to go-live
Full migration in 6 months for a fintech with 200M records and critical batch processing. Zero transactional loss, cutover downtime < 2h.
PHASES
Assessment & business case
ora2pg report mode, analysis of real Oracle feature usage, ROI calculation over 12/24/36 months. Deliverable: a decision document for CFO + CTO.
Conversion and testing
Schema converted, PL/SQL translated, functional and load test suite. PostgreSQL environment mirroring Oracle in staging.
Replication and parallel run
Oracle and PostgreSQL running in parallel with CDC. Continuous divergence validation, fine-grained tuning. Cutover risk reduced to a documented operation.
Cutover & sustainment
Cutover rehearsed three times before the real one. Go-live with technical rollback plan. 90 days of hypercare. Then, continuous PostgreSQL remote DBA.
FAQ
Most can. The cases where we don't recommend it: heavy use of Oracle Multitenant + Pluggable DBs with automated lifecycle, strong dependency on Oracle Spatial 3D / Oracle Text with features that have no equivalent, or an app that issues Oracle-specific hints at massive volume. The assessment says so clearly.
For a database up to 2TB with moderate PL/SQL, expect 3–4 months from assessment to go-live. Above 10TB or with very complex PL/SQL, 6–9 months. Always with Oracle+PostgreSQL parallelism at least 1 month before cutover.
Yes. Paid POC (fixed scope, 4 weeks) where we convert 10–20% of the most complex schema and prove technical viability and performance gain. If the result is negative, you cancel and only lost the POC — not 6 months of migration.
They stay. PostgreSQL supports most BI tools (Power BI, Tableau, Metabase) with native driver. SQL with very Oracle-specific syntax (CONNECT BY, MODEL clause) is converted to standard SQL or WITH RECURSIVE.
Yes, with a PostgreSQL Remote DBA contract — the same team that migrated keeps operating. It's the most efficient way: knowledge of the migrated environment stays with whoever built it.
20 minutes with a Senior DBA. Tell us your Oracle environment (version, size, features used) and we'll return a viability and ROI estimate at no commitment.
Migration stack
WHY HTI
Sustaining critical environments in Brazil since 1990. We're not a generic consultancy that learned databases — we are The Database Company.
Continuously operating since 1990. 25,000+ consulting hours delivered and 596+ critical production incidents resolved. Pattern recognition only decades of real operation can build.
The only MySQL Authorized Education Center (AMEC) of Oracle University in Brazil — achieved twice. Over 1,000 DBAs trained in official HTI courses.
DBAs operate from a restricted-access room at PIT São José dos Campos: 24h CCTV, biometric access, dedicated rack. No remote freelancers, no improvised workstations. Compliance that goes beyond internal policy.
Behavioral monitoring developed in-house. Detects anomalous ingestion patterns and access to protected objects — no third-party tool dependency.