Two-way sync
Changes in Acumatica or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Acumatica 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.
Acumatica runs the business on structured records: Invoices, Purchase Orders, Stock Items, Shipments. Sharepoint holds files and the metadata that describes them: Columns and content types, Permissions and sharing, Site pages, Sites. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Acumatica 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 Acumatica 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 Invoices, Purchase Orders, Stock Items, Shipments in Acumatica and Columns and content types, Permissions and sharing, Site pages, Sites 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 Acumatica. 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 Acumatica and the file in Sharepoint never describe two different versions of the same document.
Files that Acumatica 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.
Record fields from Acumatica, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Sharepoint, so storage stays organized without anyone tagging by hand.
A contract, vendor bill, or receipt added to Sharepoint with its details can create or update the matching record in Acumatica, so a document captured outside the finance system still reaches the books.
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.
| Acumatica objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Projects Project cost and billing structures synced with delivery tools. | 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. | Projects is specific to Acumatica and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Opportunities and Cases is specific to Acumatica and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Customers AR master data synced with CRMs and billing tools. | 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. | Customers is specific to Acumatica and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Vendors Supplier records aligned with procurement and AP automation. | 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. | Vendors is specific to Acumatica and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | 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. | Sales Orders is specific to Acumatica and List items to Sharepoint — each maps to any object or custom field on the other side. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | 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. | Invoices is specific to Acumatica and Drive items (document libraries) 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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
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 Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Sharepoint connection.
Changes in Acumatica or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica 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 Acumatica or Sharepoint record.
Track your Acumatica ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica 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 Acumatica 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 Acumatica 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 507 integrations available for Acumatica and Sharepoint.