Skip to content
Storage ⇄ Data warehouse

Sharepoint to Snowflake integration — real-time, two-way sync

Keep Sharepoint and Snowflake 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 Snowflake

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

Snowflake 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 Snowflake, or a result in Snowflake 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 Schemas, Tables, Views, Materialized Views in Snowflake with Columns and content types, Permissions and sharing, Site pages, Sites 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 Land CRM and ERP records in Snowflake continuously so BI reflects business systems without nightly batch ETL
  • 02 Activate modeled Snowflake tables by syncing scores and attributes back into CRM fields sales can act on
  • 03 Two-way sync SharePoint List items with a database table so internal apps read and write structured records in SQL without calling the SharePoint API directly.
  • 04 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.

Common sync patterns

One dataset, kept consistent both ways

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

Where Sharepoint holds the file inventory: make it queryable

The catalog of documents, owners, and folders in Sharepoint appears as Schemas, Tables, Views, Materialized Views in Snowflake, so file metadata can be joined against the rest of your data and reported on.

Where Snowflake computes the labels: push them onto the files

Classifications, scores, or status derived in Snowflake are written back onto the matching Columns and content types, Permissions and sharing, Site pages, Sites in Sharepoint as metadata or tags, so the file store reflects what analytics decided.

What you can sync between Sharepoint and Snowflake

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 Snowflake objects How this pairing syncs
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. Virtual Warehouses The compute a sync's queries run on, sized independently of storage. List items is specific to Sharepoint and Virtual Warehouses to Snowflake — 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. Databases Top-level containers that scope which data a sync can touch. Drive items (document libraries) is specific to Sharepoint and Databases to Snowflake — 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. Schemas Namespaces within a database used to organize synced tables. Columns and content types is specific to Sharepoint and Schemas to Snowflake — 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 The main landing and activation target for synced records. Permissions and sharing is specific to Sharepoint and Tables to Snowflake — 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 Modeled projections used as the source side of outbound syncs. Site pages is specific to Sharepoint and Views to Snowflake — 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 synced outward for low-latency reads. Sites is specific to Sharepoint and Materialized Views to Snowflake — each maps to any object or custom field on the other side.

How changes propagate between Sharepoint and Snowflake

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

Snowflake Sharepoint Sub-second propagation

DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.

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.
  • Snowflake: No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time.
What ships with Sharepoint ⇄ Snowflake

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Sharepoint ⇄ Snowflake 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 Snowflake.

How the Sharepoint and Snowflake 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.

Snowflake

Integration surface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism
Capabilities
read · write · CDC
Rate limits
No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time
Snowflake setup guide
How it works

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

    Choose tables

    Pick the Sharepoint and Snowflake 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 ⇄ Snowflake
    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 Snowflake
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Sharepoint and Snowflake 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 7 of 538
All Sharepoint integrations All Snowflake integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own