Two-way sync
Changes in Close or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Close 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.
Close 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 Smart Views, Leads, Contacts, Opportunities in Close aligned with Lists, List items, Drive items (document libraries), Columns and content types 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 Close; and records from Close 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.
Attachments that accumulate against a record in Close collect in that customer's folder in Sharepoint, so the full document history lives in one place and is reachable by anyone who needs it.
When an account or deal is created in Close, a matching folder or container opens in Sharepoint, named and organized the same way, so files have a home the moment they are needed.
A contract, proposal, or signed agreement filed in Sharepoint surfaces as a link on the matching record in Close, so the customer's paperwork sits with the relationship instead of a shared drive.
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.
| Close objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in 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. | Custom Fields is specific to Close and Columns and content types to Sharepoint — each maps to any object or custom field on the other side. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | 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. | Users is specific to Close and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Smart Views is specific to Close and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | 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. | Leads is specific to Close and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | 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. | Contacts is specific to Close and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | 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. | Opportunities is specific to Close and List items 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.
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
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 written to Close through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Sharepoint connection.
Changes in Close or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close 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 Close or Sharepoint record.
Track your Close ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close 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 Close 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 Close 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 520 integrations available for Close and Sharepoint.