Independent enterprise technology-change research

PT-2026-059 · 20 July 2026

PlatformTrace

Enterprise platform migrations, examined in public.

Database migration · Completed · High confidence

URBN moves Sterling OMS from Oracle to AlloyDB

URBN migrated the 11 TB Oracle database supporting IBM Sterling Order Management System to AlloyDB for PostgreSQL on Google Cloud.

Evidence boundary: The completed bounded workload is Sterling OMS. The record does not claim that every URBN Oracle workload was retired.

What was reported

URBN moved the production database behind IBM Sterling Order Management System from Oracle to AlloyDB for PostgreSQL.

Verified facts

  • The source database was an 11 TB Oracle environment.
  • AlloyDB for PostgreSQL is the destination.
  • The affected workload is IBM Sterling OMS.
  • The customer-authored account describes the migration as completed.

What is not established

  • The exact cutover date.
  • Retirement of every Oracle workload across URBN.
  • The full residual archive or rollback arrangement.

PlatformTrace analysis

This is a high-value named database-engine migration because the source, destination, workload and scale are all explicit. The scope remains deliberately limited to Sterling OMS.

Sources

  1. Google Cloud article co-authored by URBN's CIO.

Corrections and updates

No correction is currently open. Wider Oracle-retirement evidence will be treated as a separate event unless it clearly belongs to this workload.