Two-way sync
Changes in Rockset or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Rockset 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.
Rockset keeps the tables and query results a business reports on; Sharepoint keeps the raw files, documents, and objects that the same business produces and shares. The two overlap wherever a dataset lives as both — a file dropped in Sharepoint that has to become rows in Rockset, or a result in Rockset that people downstream need back as a file in Sharepoint. When that overlap is bridged by manual export and import or an overnight job, one side spends the day working from a stale copy.
Stacksync syncs Collections, Documents, Workspaces, Query Lambdas in Rockset with Permissions and sharing, Site pages, Sites, Lists in Sharepoint field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Where the same dataset lives as a file in Sharepoint and a table in Rockset, a change on either side propagates to the other, ending the drift between the file people read and the table people query.
The catalog of documents, owners, and folders in Sharepoint appears as Collections, Documents, Workspaces, Query Lambdas in Rockset, so file metadata can be joined against the rest of your data and reported on.
Classifications, scores, or status derived in Rockset are written back onto the matching Permissions and sharing, Site pages, Sites, Lists in Sharepoint as metadata or tags, so the file store reflects what analytics decided.
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.
| Rockset objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Documents JSON records addressable by _id, written via the Write API in sync pipelines. | 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. | Documents is specific to Rockset and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Workspaces Namespaces that group collections and query lambdas per team or environment. | 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. | Workspaces is specific to Rockset and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. | 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. | Query Lambdas is specific to Rockset and List items to Sharepoint — each maps to any object or custom field on the other side. | |
| Aliases Stable names that point at collections, used to swap datasets without changing queries. | 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. | Aliases is specific to Rockset and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side. | |
| Integrations Managed source connections (databases, streams, object storage) feeding 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. | Integrations is specific to Rockset and Columns and content types to Sharepoint — each maps to any object or custom field on the other side. | |
| Virtual Instances Isolated compute units that separate ingest from query workloads. | 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. | Virtual Instances is specific to Rockset and Permissions and sharing 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.
DetectionStacksync polls Rockset for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL queries on timestamp fields.
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 applied to Rockset as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rockset–Sharepoint connection.
Changes in Rockset or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Rockset 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 Rockset or Sharepoint record.
Track your Rockset ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Rockset 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 Rockset 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 Rockset 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 493 integrations available for Rockset and Sharepoint.