DatriseAI-first ETL

Microsoft SharePoint to Neon Integration

AI-first ETL from Microsoft SharePoint into Neon. Governed entities, incremental sync, typed landing tables.

How Datrise loads Microsoft SharePoint into Neon

Datrise syncs Microsoft SharePoint's sites, lists, list items, documents, libraries, and permissions into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

Microsoft SharePoint: Document libraries and team site content.

Neon: Serverless Postgres destination with branching and autoscaling.

How Microsoft SharePoint entities map to Neon

Microsoft SharePoint entityNeon objectNotes
sitesmicrosoft_sharepoint_sitesid PK · custom fields → jsonb columns
listsmicrosoft_sharepoint_listsid PK · linked to microsoft_sharepoint_sites
list itemsmicrosoft_sharepoint_list_itemsid PK · linked to microsoft_sharepoint_sites
documentsmicrosoft_sharepoint_documentsid PK · linked to microsoft_sharepoint_sites

FAQ

How does Datrise handle Microsoft SharePoint's custom fields in Neon?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

How does the Microsoft SharePoint to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Microsoft SharePoint to Neon the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.