Skip to content
Database ⇄ Storage

MongoDB to Sharepoint integration — real-time, two-way sync

Keep MongoDB and Sharepoint in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect MongoDB and Sharepoint

Keep MongoDB and Sharepoint in step: a row in MongoDB for every file in Sharepoint, with names, paths, metadata, and status staying consistent in real time, in both directions.

A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in MongoDB says a file exists and carries its name, location, and status, while Sharepoint holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.

Stacksync syncs Views, Change streams, GridFS files, Databases in MongoDB with Columns and content types, Permissions and sharing, Site pages, Sites in Sharepoint bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.

Common use cases

  • 01 Sync MongoDB collections with a CRM so customer documents written by the application appear as CRM records, and CRM edits flow back as document updates.
  • 02 Replicate operational MongoDB data into a relational database, flattening nested documents into normalized tables for SQL reporting.
  • 03 Two-way sync SharePoint List items with a database table so internal apps read and write structured records in SQL without calling the SharePoint API directly.
  • 04 Mirror document-library drive items and their metadata into a store to index files for search and governance, and push generated documents back into the right library.

Common sync patterns

File metadata kept in step

Tags, custom properties, owner, or status columns edited on a row in MongoDB write back to the matching file's metadata in Sharepoint, and metadata changed in Sharepoint updates the row, so the two never disagree about a file.

Records that point at documents

Where a record in MongoDB references a file in Sharepoint, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.

A landing zone for incoming files

Files that arrive in a folder or bucket in Sharepoint become rows in MongoDB as they land, so a database-driven process can pick them up without polling the storage system's API.

What you can sync between MongoDB and Sharepoint

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

MongoDB objects Sharepoint objects How this pairing syncs
Documents BSON records created, updated, and deleted during syncs, keyed by _id. List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. Documents is specific to MongoDB and List items to Sharepoint — each maps to any object or custom field on the other side.
Embedded documents and arrays Nested structures that syncs flatten or map to related records in relational targets. Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. Embedded documents and arrays is specific to MongoDB and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Indexes Keep lookups by sync key fast on large collections. Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. Indexes is specific to MongoDB and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.
Views Read-only aggregation-defined sources for filtered sync datasets. Permissions and sharing Role assignments and sharing links on sites, list items, and drive items; read and written to manage access, requiring Sites.Manage.All or Sites.FullControl.All scopes. Views is specific to MongoDB and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
Change streams The oplog-backed event feed that powers real-time change capture. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Change streams is specific to MongoDB and Site pages to Sharepoint — each maps to any object or custom field on the other side.
GridFS files Chunked file storage whose metadata can be referenced by synced documents. Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. GridFS files is specific to MongoDB and Sites to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between MongoDB and Sharepoint

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

MongoDB Sharepoint Sub-second propagation

DetectionChanges in MongoDB are captured at the source via change data capture — no polling loop against its API. MongoDB oplog and change streams (requires the database to run as a replica set — even single-node).

DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.

Sharepoint MongoDB Sub-second propagation

DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.

DeliveryEach detected change is applied to MongoDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Sharepoint: SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
What ships with MongoDB ⇄ Sharepoint

Connect MongoDB and Sharepoint for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MongoDB–Sharepoint connection.

Real-time

Two-way sync

Changes in MongoDB or Sharepoint instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MongoDB or Sharepoint data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single MongoDB or Sharepoint record.

Observability

Monitoring

Track your MongoDB ⇄ Sharepoint sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MongoDB and Sharepoint.

How the MongoDB and Sharepoint connectors work

MongoDB

Integration surface
MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management
Authentication
Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required
Change detection
MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time
Capabilities
read · write · CDC
MongoDB setup guide

Sharepoint

Integration surface
Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call).
Authentication
OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent.
Change detection
Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available.
Capabilities
read · write · webhooks
Rate limits
SharePoint Online throttles per app, returning HTTP 429 (or 503) with a Retry-After header in seconds and IETF RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers; throttled requests still count toward limits, so clients honor the greater of Retry-After and RateLimit-Reset with exponential backoff.
How it works

How to connect MongoDB to Sharepoint — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate MongoDB and Sharepoint with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    MongoDB connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the MongoDB and Sharepoint objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · MongoDB ⇄ Sharepoint
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    MongoDB Sharepoint
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

MongoDB and Sharepoint integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 531 integrations available for MongoDB and Sharepoint.

Popular · 7 of 531
All MongoDB integrations All Sharepoint integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own