Two-way sync
Changes in Sharepoint or Syspro instantly reflect in both systems. No stale data, no manual imports.
Keep Sharepoint and Syspro in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Syspro runs the business on structured records: Sales orders, Purchase orders, Jobs (work orders), Bills of materials. Sharepoint holds files and the metadata that describes them: Sites, Lists, List items, Drive items (document libraries). The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Syspro touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Sharepoint, from signed contracts to vendor bills to receipts, describe a transaction Syspro needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.
Stacksync keeps Sales orders, Purchase orders, Jobs (work orders), Bills of materials in Syspro and Sites, Lists, List items, Drive items (document libraries) in Sharepoint in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Sharepoint already labeled and filed, and metadata captured against a stored file can create or update the matching record in Syspro. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.
The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Syspro and the file in Sharepoint never describe two different versions of the same document.
As records change in Syspro, the corresponding files and metadata in Sharepoint are kept in step, so a stored document reflects the latest version rather than a stale one-time export.
Every transaction's supporting file lives in Sharepoint beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Syspro.
Files that Syspro produces land in Sharepoint labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.
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 | Syspro objects | How this pairing 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. | Sales orders Orders written in from storefronts and CRMs, with status read back out. | Lists is specific to Sharepoint and Sales orders to Syspro — 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. | Purchase orders Procurement documents synced with supplier portals and receiving. | List items is specific to Sharepoint and Purchase orders to Syspro — 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. | Jobs (work orders) Manufacturing jobs and WIP tracked for production reporting. | Drive items (document libraries) is specific to Sharepoint and Jobs (work orders) to Syspro — 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. | Bills of materials Product structures referenced when syncing manufacturing data. | Columns and content types is specific to Sharepoint and Bills of materials to Syspro — 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. | AR invoices Billing documents surfaced to CRMs and finance reporting. | Permissions and sharing is specific to Sharepoint and AR invoices to Syspro — 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. | GL journals Financial postings extracted for consolidation and analytics. | Site pages is specific to Sharepoint and GL journals to Syspro — 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 written to Syspro through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Syspro for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
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–Syspro connection.
Changes in Sharepoint or Syspro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Sharepoint or Syspro 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 Syspro record.
Track your Sharepoint ⇄ Syspro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Sharepoint and Syspro.
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 Syspro 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 Syspro 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 497 integrations available for Sharepoint and Syspro.