Where SPSync reads SharePoint data from

SPSync reads from SharePoint Online through the Microsoft Graph API. That covers the lists on any site you can reach, including the ones people create in Microsoft Lists, and the metadata of document libraries.

What SPSync reads

A list becomes a table with a column for each list column. Lookups arrive as key columns and multi-value columns as child tables, so two lists join in SQL the way any two tables do. A document library is copied as metadata: the item id, the content type, the dates and every custom column. The first run reads the whole list. After that SPSync asks Graph only for what changed, so a list past the 5,000-item view threshold replicates like a small one.

What stays in SharePoint

File contents and attachments are not copied. A pipeline that needs a file fetches it from Graph using the site, list and item ids on the row. Item permissions are not copied either, so the access you grant on the database decides who can read the copy. SPSync never writes to SharePoint. SharePoint Server on-premises is on the roadmap and is not supported today.

Connecting a site

You can sign in with your own Microsoft account and replicate the sites you can already open. For runs with nobody signed in, an admin grants the app access to chosen sites with Sites.Selected. The admin permissions guide lists every permission SPSync asks for. To see where the data goes, browse the destinations.