Two-way sync
Changes in Sharepoint or StarRocks instantly reflect in both systems. No stale data, no manual imports.
Keep Sharepoint and StarRocks in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
StarRocks 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 StarRocks, or a result in StarRocks 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 Tables, Materialized views, Views, Partitions in StarRocks with Lists, List items, Drive items (document libraries), Columns and content types 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.
Curated tables and query results from StarRocks are written to Sharepoint as files the rest of the business can open, keeping the shared copy current without a hand-run export.
Where the same dataset lives as a file in Sharepoint and a table in StarRocks, 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 Tables, Materialized views, Views, Partitions in StarRocks, so file metadata can be joined against the rest of your data and reported on.
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 | StarRocks objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Databases Top-level namespaces addressed exactly as in MySQL clients. | Sites is specific to Sharepoint and Databases to StarRocks — 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. | Tables Defined with a table model (Primary Key, Unique Key, Aggregate, Duplicate Key) that determines update behavior. | Lists is specific to Sharepoint and Tables to StarRocks — 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. | Materialized views Automatically maintained rollups used to accelerate queries on synced data. | List items is specific to Sharepoint and Materialized views to StarRocks — each maps to any object or custom field on the other side. | |
| 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. | Views Logical views for shaping analytical reads. | Drive items (document libraries) is specific to Sharepoint and Views to StarRocks — each maps to any object or custom field on the other side. | |
| 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. | Partitions Time or range partitions that scope loads and retention. | Columns and content types is specific to Sharepoint and Partitions to StarRocks — 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. | Columns Columnar storage with types mapped from source systems during sync. | Permissions and sharing is specific to Sharepoint and Columns to StarRocks — 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 StarRocks as a row-level write, with types converted between the two schemas.
DetectionStacksync polls StarRocks for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling when reading.
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–StarRocks connection.
Changes in Sharepoint or StarRocks instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Sharepoint or StarRocks 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 StarRocks record.
Track your Sharepoint ⇄ StarRocks sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Sharepoint and StarRocks.
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 StarRocks 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 StarRocks 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 425 integrations available for Sharepoint and StarRocks.