Azure Table Storage to Neon Integration

How Datrise loads Azure Table Storage into Neon

Datrise syncs Azure Table Storage's tables, entities, partition keys, row keys, properties, and timestamps 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

Azure Table Storage: Key-value NoSQL store on Azure.

Neon: Serverless Postgres destination with branching and autoscaling.

How Azure Table Storage entities map to Neon

Azure Table Storage entity	Neon object	Notes
tables	`azure_table_storage_tables`	id PK · custom fields → jsonb columns
entities	`azure_table_storage_entities`	id PK · linked to azure_table_storage_tables
partition keys	`azure_table_storage_partition_keys`	id PK · linked to azure_table_storage_tables
row keys	`azure_table_storage_row_keys`	id PK · linked to azure_table_storage_tables

FAQ

How does Datrise handle Azure Table Storage'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 Azure Table Storage 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 Azure Table Storage 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.