Google Directory to MongoDB Integration

How Datrise loads Google Directory into MongoDB

Datrise syncs Google Directory's users, groups, group members, organizational units, devices, and roles 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

Google Directory: Workspace user, group, and device directory.

MongoDB: Document database for flexible schemas.

How Google Directory entities map to MongoDB

Google Directory entity	MongoDB object	Notes
users	`google_directory_users`	id PK · custom fields → native nested documents
groups	`google_directory_groups`	id PK · linked to google_directory_users
group members	`google_directory_group_members`	id PK · linked to google_directory_users
organizational units	`google_directory_organizational_units`	id PK · linked to google_directory_users

FAQ

How does Datrise handle Google Directory'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 Google Directory 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 Google Directory 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.