SPSync
SPSync replicates SharePoint Online lists and document libraries (metadata only) into SQL Server or Postgres, then keeps them in sync on a schedule. It runs as a CLI, a desktop app, or a managed application in your own Azure subscription.
Guides
Section titled “Guides”- Setup: install the CLI, sign in, connect a site, and run your first replication.
- Admin permissions: what a SharePoint/Entra admin needs to grant, and why, for both delegated and app-only auth.
- Connect to SharePoint: register your own app, create a
certificate, grant consent and
Sites.Selected, and use it from the CLI, desktop or MCP. - Schema reference: how SharePoint columns map to destination tables and types, so you know what to expect in SQL Server or Postgres before you connect a BI tool to it.
- Destination setup guides: create the database and a least-privilege user, open the firewall, encrypt the connection and connect SPSync to SQL Server, Azure SQL, PostgreSQL, MySQL and MariaDB, Oracle, SQLite, DuckDB, BigQuery, Databricks, ClickHouse, Azure Data Lake, Delta Lake, Iceberg, Dataverse, Elasticsearch, OpenSearch, Azure AI Search, pgvector, Qdrant, Weaviate and LanceDB.
- Troubleshooting: fixes for the errors people hit most often: throttling, expired tokens, missing site grants, and schema drift.
- What the trial does to your data: we are not taking self-serve trial downloads yet, but this explains the one data rule that will apply once we are.
- Getting support: when troubleshooting does not get you there, export a redacted bundle of logs, config and run history and attach it to your email to us, so we can help faster.
Who SPSync is for
Section titled “Who SPSync is for”SPSync is for anyone who needs SharePoint list and library data available as relational tables, for reporting, for a BI tool, or as a read model for another application, without hand-rolling a Graph API integration. See the setup guide to get started.