SPSync vs Peliqan

Choose SPSync when you want every list replicated into a database you run, with lookups as keys and deletes recorded; choose Peliqan for a hosted warehouse with AI tools and Python on top.

Documentation reviewed 23 October 2026

Where Peliqan fits

• A hosted warehouse, SQL editor and BI connections in one subscription, with nothing to install
• an MCP server, text-to-SQL and RAG with built-in embeddings over the synced list, plus n8n and Make
• low-code Python scripts and reverse ETL that can add and update list items, on the Pro plan and above
• SOC 2 Type II and ISO 27001, with EU data kept in an EU region

Where it breaks

• the SharePoint List connector covers one specific list per connection
• its pages say incremental sync applies where the connector supports it, without saying how a SharePoint list is read or how deletes are handled
• the connector page does not say how lookup, person or multi-choice columns arrive
• the replica lives in Peliqan's warehouse unless you connect one of your own
• the entry plan is priced per data source, and Python apps and writeback need the Pro plan

Feature by feature

Your team wants an assistant that can answer “how many open change requests does each site have?” from SharePoint lists, and the search for “SharePoint list MCP server” or “text to SQL SharePoint list” keeps returning Peliqan. Its pages describe much the same idea SPSync is built on: copy the list once and let agents query the copy instead of SharePoint. The difference is where the copy lives and what else comes with it.

How does Peliqan sync a SharePoint list?

Peliqan offers two SharePoint connectors that matter here. The Sharepoint List connector works with one specific list and comes with an ETL pipeline into a warehouse. The Sharepoint Site connector is for low-code Python scripts that read lists and upload files. By default the list arrives in Peliqan’s built-in warehouse. Its guide says you can connect your own instead, naming SQL Server, Snowflake, Redshift and BigQuery (checked 2026-10-23).

Its connector page says incremental updates happen where the connector supports them, and that syncs can run as often as every 15 minutes on the Pro plan. It does not say whether the SharePoint list is read by delta query or in full, how deletes are handled, or how lookup, person and multi-choice columns are shaped. The connector page text also reads as a general template, describing the source as a project and task tool. Test it on a list with lookups and a few deleted items before you plan reports on it.

Peliqan’s AI tools over a cached copy

This is Peliqan’s strongest ground. Once a list is synced, Peliqan offers an MCP server for Claude, ChatGPT and other clients, text-to-SQL, RAG with embeddings it creates for you, and nodes for n8n and Make. Its AI page says agents query a read-only copy in its warehouse, so the live list is never touched, while the MCP server can be published with read and write capabilities (checked 2026-10-23). If you want a hosted place to try an agent over a list this week, that bundle is hard to match.

SPSync has no agent of its own. What it keeps is one SQL copy of your lists in a database you run, read from SharePoint by delta query and never written back. An agent reaches it through a database MCP server you choose, or through spsync mcp serve, SPSync’s own read-only MCP server over the replica, signing in with a read-only database login and no Microsoft Graph permission. SharePoint item permissions are not carried into the replica, so database roles and row-level security decide what each agent can see. Embeddings on sync, for semantic search over item text, are written to pgvector or Azure AI Search only. File contents stay in SharePoint; SPSync copies their metadata.

Your database or Peliqan’s warehouse

With Peliqan, the platform is the product: warehouse, SQL editor, spreadsheet view, Python apps, BI connections and the AI layer in one subscription, hosted by Peliqan with EU data kept in an EU region. Teams with no database of their own get a lot from that.

SPSync assumes you already have a database, or want one under your control. It runs as a desktop app on Windows or macOS, as a command-line tool on your server, or in your own Azure subscription, and writes to SQL Server, Azure SQL, PostgreSQL, Supabase, BigQuery and many other destinations. Sign-in can be app-only with Sites.Selected, granted read access to only the sites you pick. Lookups arrive as key columns, multi-value columns as child tables, and a deleted item keeps its row with sp_deleted_at set, so the schema is ready for joins without a modelling step.

Writing back to SharePoint

Peliqan can write to lists today. Its guide shows Python that adds and updates list items, and writeback is part of the Pro plan and above. SPSync cannot: it is one way, SharePoint to your database, and write-back is designed and on the roadmap. If an agent or app has to change list items this quarter, Peliqan or Layer2 Cloud Connector does that now.

Moving from Peliqan to SPSync

1. List the SharePoint List connections in Peliqan and the queries and dashboards that read them.
2. In SPSync, sign in to SharePoint and tick the same lists; one licence covers them all.
3. Choose the database, let the first full load run, and check row counts against each list.
4. Rewrite the queries against the SPSync tables, joining lookups on their key columns.
5. Point your MCP server or BI tool at the replica with a read-only login, then switch off the Peliqan connections.

SPSync as a Peliqan alternative for SharePoint lists

SPSync keeps the list data in your own database and does only that job. It reads changes by Graph delta query, keeps a row for each deleted item, and writes lookups as key columns and multi-value columns as child tables. AI tools reach the replica through a read-only database login, and embeddings on sync go to pgvector or Azure AI Search.

Other alternatives

• Coupler.io: scheduled Microsoft Lists refreshes into sheets, BI tools and warehouses, with its own AI integrations.
• Stacksync: AI agents with approval steps and an MCP server over two-way CRM and ERP syncs, though its SharePoint pages say support is not established.
• Fivetran: a managed Microsoft Lists connector that loads a warehouse you own and bills by Monthly Active Rows.
• Airbyte: an open-source platform you can host yourself, with a SharePoint Lists Enterprise connector.