Sendwithus to MongoDB Integration

How Datrise loads Sendwithus into MongoDB

Datrise syncs Sendwithus's templates, sends, customers, delivery events, versions, and drip campaigns 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

Sendwithus: Templated transactional email and A/B testing.

MongoDB: Document database for flexible schemas.

How Sendwithus entities map to MongoDB

Sendwithus entity	MongoDB object	Notes
templates	`sendwithus_templates`	id PK · custom fields → native nested documents
sends	`sendwithus_sends`	id PK · linked to sendwithus_templates
customers	`sendwithus_customers`	id PK · linked to sendwithus_templates
delivery events	`sendwithus_delivery_events`	BSON Date events

FAQ

How does Datrise handle Sendwithus'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 Sendwithus 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

Early access

Connect Sendwithus 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.