Bridgeport

Upload your own CSV or JSON to run a real migration simulation, or explore with sample data.

PythonFastAPIPostgreSQLMongoDBRedisDocker

⬆Drop a CSV or JSON file to migrate your own data

🔒All data is processed in your browser. Nothing is uploaded to any server.

Schema Mapping Configuration

Bridgeport maps fields from the legacy PostgreSQL schema to the target MongoDB collection. Fields marked with a gold indicator have active mappings. The unmapped field (legacy_ref) will be archived but not transferred.

Source — PostgreSQL

legacy_customers
cust_idSERIAL
full_nameVARCHAR(120)
email_addrVARCHAR(255)
phone_numVARCHAR(30)
signup_dtTIMESTAMP
acct_statusINT
legacy_refVARCHAR(50)

Target — MongoDB

customers
_idObjectId
nameString
emailString
phoneString
createdAtDate
statusString

Transformation Rules

cust_id (SERIAL)→_id (ObjectId)Generate ObjectId, store original as metadata

signup_dt (TIMESTAMP)→createdAt (Date)Parse ISO 8601, convert timezone to UTC

acct_status (INT)→status (String)Map: 1 → "active", 2 → "suspended", 3 → "closed"

email_addr→emailValidate format, flag if null or malformed

phone_num→phoneNormalise to E.164, flag if null

Bridgeport v1.2.0 — Armdia Systems

Engine idle

← Back to case study