Skip to content
Storage ⇄ Data warehouse

Sharepoint to Starburst Enterprise integration — real-time, two-way sync

Keep Sharepoint and Starburst Enterprise 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 Sharepoint and Starburst Enterprise

Bridge query-ready tables and stored files: Starburst Enterprise and Sharepoint keep the same records in step, in real time, in both directions.

Starburst Enterprise 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 Starburst Enterprise, or a result in Starburst Enterprise 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 Columns, Catalogs, Schemas, Tables in Starburst Enterprise with List items, Drive items (document libraries), Columns and content types, Permissions and sharing 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.

Common use cases

  • 01 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • 02 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 03 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.
  • 04 Sync list columns and content types so database fields map onto SharePoint list fields and schema stays aligned as either side changes.

Common sync patterns

Where Sharepoint receives the raw files: land them as query-ready rows

Files and exports that arrive in Sharepoint are parsed into Columns, Catalogs, Schemas, Tables in Starburst Enterprise as they land, so analysts query current data instead of waiting on the next scheduled load.

Where Sharepoint is the shared drive: publish results back as files

Curated tables and query results from Starburst Enterprise are written to Sharepoint as files the rest of the business can open, keeping the shared copy current without a hand-run export.

One dataset, kept consistent both ways

Where the same dataset lives as a file in Sharepoint and a table in Starburst Enterprise, a change on either side propagates to the other, ending the drift between the file people read and the table people query.

What you can sync between Sharepoint and Starburst Enterprise

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 Starburst Enterprise 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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Columns and content types is specific to Sharepoint and Schemas to Starburst Enterprise — 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. Tables Queryable relations; writes pass through to sources whose connectors support them. Permissions and sharing is specific to Sharepoint and Tables to Starburst Enterprise — 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. Views Engine-level SQL views used to shape federated data before syncing it out. Site pages is specific to Sharepoint and Views to Starburst Enterprise — 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. Materialized views Precomputed results that make repeated sync reads cheaper. Sites is specific to Sharepoint and Materialized views to Starburst Enterprise — 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. Columns Typed per the Trino type system, mapped from each source's native types. Lists is specific to Sharepoint and Columns to Starburst Enterprise — 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. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. List items is specific to Sharepoint and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Sharepoint and Starburst Enterprise

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.

Sharepoint Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Sharepoint Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

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

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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Sharepoint ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Sharepoint or Starburst Enterprise 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 Sharepoint or Starburst Enterprise record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Sharepoint and Starburst Enterprise connectors work

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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Sharepoint to Starburst Enterprise — 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 Sharepoint and Starburst Enterprise 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
    Sharepoint connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Sharepoint and Starburst Enterprise 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 · Sharepoint ⇄ Starburst Enterprise
    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
    Sharepoint Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Sharepoint and Starburst Enterprise 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.

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:

Related integrations

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

Popular · 7 of 427
Coworkers laughing in front of a laptop in a casual office setting

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