Skip to content
CRM ⇄ Storage

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

Keep Salesforce 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.

  • 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 Salesforce and Sharepoint

Keep the paperwork with the relationship: Salesforce and Sharepoint share every customer's records and files in real time, in both directions.

Salesforce holds the customer relationship as structured records; Sharepoint holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.

Stacksync keeps Cases, Campaigns, Tasks and Events, Products and Price Books in Salesforce aligned with Permissions and sharing, Site pages, Sites, Lists in Sharepoint, in real time. A new account or deal can open its own folder in Sharepoint; a document filed in Sharepoint can surface as a link and metadata on the matching record in Salesforce; and records from Salesforce can be written into Sharepoint as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.

Common use cases

  • 01 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 02 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 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

Documents linked back to the record

A contract, proposal, or signed agreement filed in Sharepoint surfaces as a link on the matching record in Salesforce, so the customer's paperwork sits with the relationship instead of a shared drive.

CRM records archived into storage

Records from Salesforce are written into Sharepoint as files or objects on the schedule you set, giving you a durable copy for backup, retention, and compliance without an export to run by hand.

Document status on the record

Metadata kept in Sharepoint, such as document type, review state, or whether an agreement is signed, updates a field on the matching record in Salesforce, so people working the account see where the paperwork stands without opening storage.

What you can sync between Salesforce and Sharepoint

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.

Salesforce objects Sharepoint objects How this pairing syncs
Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. 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. Accounts is specific to Salesforce and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.
Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. 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. Contacts is specific to Salesforce and Columns and content types to Sharepoint — each maps to any object or custom field on the other side.
Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. 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. Leads is specific to Salesforce and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Opportunities is specific to Salesforce and Site pages to Sharepoint — each maps to any object or custom field on the other side.
Cases Support records; synced with help desk tools or internal databases for escalation workflows. 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. Cases is specific to Salesforce and Sites to Sharepoint — each maps to any object or custom field on the other side.
Campaigns Marketing membership data; read out for attribution analysis in the warehouse. 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. Campaigns is specific to Salesforce and Lists to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Salesforce and Sharepoint

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.

Salesforce Sharepoint Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

Sharepoint Salesforce 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 written to Salesforce through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Salesforce: Daily API request allocations vary by edition and license count.
  • 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.
What ships with Salesforce ⇄ Sharepoint

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Salesforce and Sharepoint connectors work

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide

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.
How it works

How to connect Salesforce to Sharepoint — 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 Salesforce 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Salesforce connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Salesforce 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Salesforce ⇄ Sharepoint
    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
    Salesforce Sharepoint
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Salesforce and Sharepoint 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 528 integrations available for Salesforce and Sharepoint.

Popular · 7 of 528
All Salesforce integrations All Sharepoint 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