Excel File to MongoDB Integration

How Datrise loads Excel File into MongoDB

Datrise syncs Excel File's worksheets, rows, columns, headers, cell ranges, and workbooks 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

Excel File: Spreadsheet workbooks from exports and shared drives.

MongoDB: Document database for flexible schemas.

How Excel File entities map to MongoDB

Excel File entity	MongoDB object	Notes
worksheets	`excel_file_worksheets`	id PK · custom fields → native nested documents
rows	`excel_file_rows`	id PK · linked to excel_file_worksheets
columns	`excel_file_columns`	id PK · linked to excel_file_worksheets
headers	`excel_file_headers`	id PK · linked to excel_file_worksheets

FAQ

How does Datrise handle Excel File'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 Excel File 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 Excel File 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.