Two-way sync
Changes in Scaleway Postgres or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Scaleway Postgres 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.
A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in Scaleway Postgres says a file exists and carries its name, location, and status, while Sharepoint holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.
Stacksync syncs Tables, Views, Materialized views, Schemas in Scaleway Postgres with Drive items (document libraries), Columns and content types, Permissions and sharing, Site pages in Sharepoint bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.
Files that arrive in a folder or bucket in Sharepoint become rows in Scaleway Postgres as they land, so a database-driven process can pick them up without polling the storage system's API.
Rows from Scaleway Postgres are written out to Sharepoint as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.
Every file or object in Sharepoint shows up as a row in Scaleway Postgres, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.
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.
| Scaleway Postgres objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Tables Primary sync unit; each table maps to an object or table on the other side of the sync. | 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. | Tables is specific to Scaleway Postgres and List items to Sharepoint — each maps to any object or custom field on the other side. | |
| Views Read-only sources for shaping data before it leaves the database. | 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. | Views is specific to Scaleway Postgres and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed result sets that can be read on a schedule for downstream 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. | Materialized views is specific to Scaleway Postgres and Columns and content types to Sharepoint — each maps to any object or custom field on the other side. | |
| Schemas Namespace tables so multiple applications or environments can be synced selectively. | 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. | Schemas is specific to Scaleway Postgres and Permissions and sharing to Sharepoint — each maps to any object or custom field on the other side. | |
| Sequences Generate primary keys; sync tooling must respect them when writing rows. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Sequences is specific to Scaleway Postgres and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | 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. | Columns is specific to Scaleway Postgres and Sites 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.
DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.
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 applied to Scaleway Postgres as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Scaleway Postgres–Sharepoint connection.
Changes in Scaleway Postgres or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Scaleway Postgres 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 Scaleway Postgres or Sharepoint record.
Track your Scaleway Postgres ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Scaleway Postgres 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 Scaleway Postgres 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 Scaleway Postgres 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 434 integrations available for Scaleway Postgres and Sharepoint.