Two-way sync
Changes in Sharepoint or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
Keep Sharepoint and YugabyteDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 YugabyteDB 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 Sequences, CDC Streams, Databases and Keyspaces, Tables in YugabyteDB with Permissions and sharing, Site pages, Sites, Lists 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.
Where a record in YugabyteDB 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.
Files that arrive in a folder or bucket in Sharepoint become rows in YugabyteDB as they land, so a database-driven process can pick them up without polling the storage system's API.
Rows from YugabyteDB are written out to Sharepoint as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.
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.
| Sharepoint objects | YugabyteDB objects | How this pairing syncs | |
|---|---|---|---|
| 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 Global secondary indexes maintained transactionally alongside table writes. | Columns and content types is specific to Sharepoint and Indexes to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | Materialized Views Precomputed query results available in YSQL for read-side shaping. | Permissions and sharing is specific to Sharepoint and Materialized Views to YugabyteDB — each maps to any object or custom field on the other side. | |
| Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Schemas Postgres-style namespaces in YSQL used to organize synced data. | Site pages is specific to Sharepoint and Schemas to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | Sequences ID generation objects relevant when syncing writes into YSQL tables. | Sites is specific to Sharepoint and Sequences to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | CDC Streams Change streams over the storage-layer WAL consumed through logical replication or Debezium-compatible connectors. | Lists is specific to Sharepoint and CDC Streams to YugabyteDB — each maps to any object or custom field on the other side. | |
| 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. | Databases and Keyspaces Top-level containers for the YSQL (Postgres-style) and YCQL (Cassandra-style) APIs respectively. | List items is specific to Sharepoint and Databases and Keyspaces to YugabyteDB — 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.
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 YugabyteDB as a row-level write, with types converted between the two schemas.
DetectionChanges in YugabyteDB are captured at the source via change data capture — no polling loop against its API. Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors.
DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sharepoint–YugabyteDB connection.
Changes in Sharepoint or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Sharepoint or YugabyteDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Sharepoint or YugabyteDB record.
Track your Sharepoint ⇄ YugabyteDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Sharepoint and YugabyteDB.
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 Sharepoint and YugabyteDB 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 Sharepoint and YugabyteDB 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 420 integrations available for Sharepoint and YugabyteDB.