Teradata D → MongoDB
AI-first ETL from Teradata D into MongoDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Teradata D into MongoDB
Datrise syncs Teradata D's records, events, and configuration objects into MongoDB as a collection per source entity. Flexible or custom fields land in native nested documents, and timestamps such as created, updated, and status changes are typed as BSON Date.
Sync is incremental: Datrise uses upserts by stable id with updateOne(upsert) on the source primary key, so re-runs update only what changed. Optional sharding on the entity id for large collections. Mongo has no fixed schema, so Datrise keeps field types consistent across documents to avoid mixed-type query surprises.
Ideal for document-oriented apps that want CRM data in their existing Mongo store.
Endpoints
Teradata D: SaaS or API data source for analytics and warehouse sync.
MongoDB: Document database for flexible schemas.
How Teradata D entities map to MongoDB
| Teradata D entity | MongoDB object | Notes |
|---|---|---|
| records | teradata_d_records | id PK · custom fields → native nested documents |
| events | teradata_d_events | BSON Date events |
| configuration objects | teradata_d_configuration_objects | id PK · linked to teradata_d_records |
FAQ
How does Datrise handle Teradata D's custom fields in MongoDB?
Flexible values are stored as native nested documents, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MongoDB types.
How does the Teradata D to MongoDB sync stay up to date?
It runs incrementally — Datrise uses upserts by stable id with updateOne(upsert) on the source primary key.
Related pipelines
More destinations for Teradata D
Early access
Connect Teradata D to MongoDB the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.