Skip to content
ERP ⇄ Storage

Microsoft Dynamics GP to Sharepoint integration — real-time, two-way sync

Keep Microsoft Dynamics GP 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 Microsoft Dynamics GP and Sharepoint

Move the documents and data that Microsoft Dynamics GP produces into Sharepoint as files, and let files stored in Sharepoint update the records they belong to in Microsoft Dynamics GP, continuously and without exports or manual filing.

Microsoft Dynamics GP runs the business on structured records: Receivables & Payables Transactions, Company Databases, Customers, Vendors. Sharepoint holds files and the metadata that describes them: Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Microsoft Dynamics GP 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 Microsoft Dynamics GP 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 Receivables & Payables Transactions, Company Databases, Customers, Vendors in Microsoft Dynamics GP and Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages 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 Microsoft Dynamics GP. 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 Microsoft Dynamics GP and the file in Sharepoint never describe two different versions of the same document.

Common use cases

  • 01 Replicate GP company databases into a warehouse for financial and operational reporting.
  • 02 Sync customers and invoices between GP and a CRM so sales sees balances and billing history.
  • 03 Sync list columns and content types so database fields map onto SharePoint list fields and schema stays aligned as either side changes.
  • 04 Provision site and item permissions and sharing links from an IdP or access-management system so SharePoint access follows onboarding and offboarding.

Common sync patterns

Metadata that files itself

Record fields from Microsoft Dynamics GP, 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.

Where Sharepoint captures inbound files: details reach the record

A contract, vendor bill, or receipt added to Sharepoint with its details can create or update the matching record in Microsoft Dynamics GP, so a document captured outside the finance system still reaches the books.

An archive that stays current

As records change in Microsoft Dynamics GP, 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.

What you can sync between Microsoft Dynamics GP 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.

Microsoft Dynamics GP objects Sharepoint objects How this pairing syncs
Company Databases Per-company SQL databases that define the scope of any sync. 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. Company Databases is specific to Microsoft Dynamics GP and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side.
Customers Receivables master records (RM tables) synced with CRMs and billing tools. Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. Customers is specific to Microsoft Dynamics GP and Site pages to Sharepoint — each maps to any object or custom field on the other side.
Vendors Payables master records aligned with procurement and AP automation. 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. Vendors is specific to Microsoft Dynamics GP and Sites to Sharepoint — each maps to any object or custom field on the other side.
Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. 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 Documents (SOP) is specific to Microsoft Dynamics GP and Lists to Sharepoint — each maps to any object or custom field on the other side.
Purchase Orders (POP) Procurement documents reconciled with receiving and vendor 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. Purchase Orders (POP) is specific to Microsoft Dynamics GP and List items to Sharepoint — each maps to any object or custom field on the other side.
Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. 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. Inventory Items (IV) is specific to Microsoft Dynamics GP and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics GP 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.

Microsoft Dynamics GP Sharepoint Sub-second propagation

DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.

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

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

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.
What ships with Microsoft Dynamics GP ⇄ Sharepoint

Connect Microsoft Dynamics GP and Sharepoint for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP and Sharepoint.

How the Microsoft Dynamics GP and Sharepoint connectors work

Microsoft Dynamics GP

Integration surface
SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
Authentication
SQL Server credentials or Windows authentication
Change detection
SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
Capabilities
read · write · CDC

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 Microsoft Dynamics GP 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 Microsoft Dynamics GP 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
    Microsoft Dynamics GP connected
    Sharepoint connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Microsoft Dynamics GP 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 496 integrations available for Microsoft Dynamics GP and Sharepoint.

Popular · 7 of 496
All Microsoft Dynamics GP 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