Oracle to PostgreSQL,
engineered to finish.
Trekport converts entire Oracle estates to PostgreSQL with production-grade fidelity. AST-based engine, 14-phase deployment orchestrator, deterministic output. The platform that lets the team running the migration ship the migration.
Built for the industries where downtime is not an option.
Built for the teams that ship the cutover.
Trekport ships as a desktop application, a command-line interface, and a web console. Same engine across all three. Same deterministic output. Every transformation is traceable to a rule.
AST-based conversion engine
Every Oracle object is parsed into a real syntax tree and re-emitted as PG-native SQL. No regex. The tree is the correctness path.
14-phase deployment orchestrator
Extensions, sequences, tables, types, indexes, constraints, procs, packages, triggers, views, MViews, synonyms, grants, FKs — in order, with retry on failure.
Per-object diagnostics
Every failure is classified into CONVERTER, CATALOG, EXTENSION, OUT_OF_SCOPE, or UNCLASSIFIED — with a concrete fix path.
SELECT NVL(salary, 0) FROM employees WHERE ROWNUM <= 10;
SELECT COALESCE(salary, 0) FROM employees LIMIT 10;
Catalog extractor
Pulls every Oracle catalog object into a portable on-disk tree the engine and the operator both read. Reviewable before a single statement runs.
Built for scale.
Engineered for throughput.
Parallel catalog extraction, iterative dependency-aware deployment, cascade-aware grant filtering. Trekport scales from a hundred-object pilot to enterprise estates exceeding 100,000 objects without breaking the run.
Catalog extractor.
Pulls every Oracle catalog object into a portable, inspectable format. Tables, indexes, types, sequences, packages, triggers, views, materialized views, synonyms, grants, role hierarchies, and database links. Ready for review before a single statement runs.
Compatibility layer.
Auto-installs orafce, pg_cron, http, pgcrypto, pg_trgm, and Trekport's Oracle compatibility extensions. Converted code finds the Oracle-equivalent functions it expects on the first try.
trekport_compat
Trekport-published shims for proprietary Oracle constructs your converted code calls into.
trekport_mod_plsql
htp.*, htf.*, owa_util.* mod_plsql helpers, native to PostgreSQL.
Air-gapped by default.
No data leaves your network. The engine runs locally. The CLI runs in your CI. The desktop application talks only to your source and target databases.
Iterative deployment.
The orchestrator retries failed objects with each pass as dependencies become available. Convergence is automatic. No hand-fix loops between runs.
Independent verification.
Conversion fidelity validated against a 500-plus pattern test suite covering DDL, PL/SQL constructs, query syntax, and Oracle built-in functions.
Deterministic conversion.
Auditable deployment.
Every converted object is classified, deploy-tested against a real PostgreSQL target, and reported with per-object diagnostics. No black-box rewrites. No silent failures. Every transformation is reviewable, reproducible, and tracked.
Built for the audit, not the demo.
Every Trekport run produces the artifacts change-management actually accepts: a per-object audit log, hard guardrails that block unsafe transformations, and a phase-level approval queue.
Audit trail
Every conversion decision logged with a rule reference, before and after. Exportable as JSON or CSV. Reviewable without engineering context.
Guardrail engine
Hard rules block unsafe transformations from reaching production. Configurable per environment. Defaults match enterprise change-management posture.
Approval queue
Optional human review checkpoint before each phase commits. Hold the line for procedures and packages, fast-path the trivial. Configurable per environment.
A small cohort gets in first.
The waitlist is the door.
Trekport is opening in waves. We're running pilots with a small set of database teams right now, tuning the engine against enterprise-scale estates and finalizing the security review. Join the waitlist and we will reach out when the next cohort opens.
Waitlist accounts get the next download link before the public release.
A migration architect walks the first run with you. No upsell, no professional-services bait.
The first cohort sets the roadmap. Tell us what your migration actually needs.
We respond within 48 hours. We don't resell or share the list.
Frequently asked questions
What database teams ask before they take the engine for a run. Anything missing? Reach out — we will answer it directly.