Two-way sync
Changes in Microsoft 365 or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft 365 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.
Microsoft 365 and Sharepoint hold different kinds of data. Microsoft 365 carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Sharepoint holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Microsoft 365 produces has to be kept somewhere durable, and many of the files Sharepoint stores are the very documents Microsoft 365's records point to.
Stacksync syncs Groups, Mail Messages, Calendar Events, Contacts in Microsoft 365 with Lists, List items, Drive items (document libraries), Columns and content types in Sharepoint in real time. Records and attachments created in Microsoft 365 are written into Sharepoint as objects or files within seconds of being created. In the other direction, the metadata Sharepoint keeps about those files — name, location, owner, modified date — flows back onto the matching record in Microsoft 365, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.
A continuously synced copy in Sharepoint preserves records and documents even as they age out of Microsoft 365 or get changed inside it, so history stays intact and reachable.
Structured records from Microsoft 365 land in Sharepoint as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.
Records and events from Microsoft 365 — tickets, messages, orders, or issues — are written into Sharepoint as objects or files as they change, giving you a durable, addressable copy for retention and audit.
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.
| Microsoft 365 objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| SharePoint Sites & Lists List items read and written like lightweight database tables. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | SharePoint Sites & Lists is specific to Microsoft 365 and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Teams Team and membership data provisioned from upstream systems. | 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. | Teams is specific to Microsoft 365 and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Planner & To Do Tasks Task items synced with project and work-management tools. | Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. | Planner & To Do Tasks is specific to Microsoft 365 and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Users Entra ID user accounts synced with HR and identity systems. | 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. | Users is specific to Microsoft 365 and List items to Sharepoint — each maps to any object or custom field on the other side. | |
| Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | 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. | Groups is specific to Microsoft 365 and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side. | |
| Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | 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. | Mail Messages is specific to Microsoft 365 and Columns and content types to Sharepoint — each maps to any object or custom field on the other side. |
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.
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.
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 written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft 365–Sharepoint connection.
Changes in Microsoft 365 or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft 365 or Sharepoint data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Microsoft 365 or Sharepoint record.
Track your Microsoft 365 ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft 365 and Sharepoint.
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.
Authenticate Microsoft 365 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.
Pick the Microsoft 365 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 446 integrations available for Microsoft 365 and Sharepoint.