Catalogs exceed 100,000 objects. Sequential conversion of that volume turns into a multi-week effort.

Trekport extracts and converts at a sustained rate of up to 100,000 catalog objects per hour on a single workstation. Catalog extraction is parallel by schema, conversion is parallel by object, and deployment parallelizes where the dependency graph allows.

Billing and provisioning logic lives inside thousands of stored procedures and packages with deep call graphs.

The AST-based engine lowers Oracle packages to schema-plus-functions with state preserved. Cursor-driven control flow, BULK COLLECT, and FORALL constructs translate without manual rework. Compound triggers and dependency-ordered grants survive the cutover intact.

Network operations refuse to schedule maintenance outside narrow off-peak windows that vary by region.

The orchestrator runs in dependency-ordered phases that can pause and resume between windows. Idempotent phase semantics mean a partially-completed run resumes cleanly. No re-run required.

Subscriber tables hold billions of rows. Bulk-export of that volume through a generic ETL tool destroys the migration window.

The data path is a Rust streaming pipeline with bounded backpressure, parallel table workers, and a fast-path COPY where the schema allows. Throughput scales with the source and target hardware rather than with the converter. Tables containing temporal or BLOB columns automatically route to an INSERT path with explicit type casts.

Carrier billing has long-running batch reports tied to package state and DBMS_SCHEDULER jobs that cannot lapse during cutover.

Trekport catalogs every DBMS_SCHEDULER job, program, and schedule alongside the schema objects they depend on. Scheduled jobs translate to pg_cron entries where the schedule expression maps cleanly; the remainder are reported with the source schedule so operations can recreate them with the appropriate downstream orchestrator.