Lofty to Microsoft SQL Server Integration

How Datrise loads Lofty into Microsoft SQL Server

Datrise syncs Lofty's leads, contacts, listings, property searches, smart plans, and tour requests into Microsoft SQL Server as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses a watermark on updated-at, applied with a MERGE statement, so re-runs update only what changed. Optional partitioned tables on a date partition function. SQL Server defaults to a case-insensitive collation, so Datrise preserves original casing in a metadata column to avoid silent key collisions.

Ideal for Microsoft-stack analytics and Power BI Import models.

Endpoints

Lofty: Real estate CRM with IDX search and AI lead nurture.

Microsoft SQL Server: Microsoft relational DB with enterprise features.

How Lofty entities map to Microsoft SQL Server

Lofty entity	Microsoft SQL Server object	Notes
leads	`lofty_leads`	id PK · custom fields → NVARCHAR(MAX) JSON columns
contacts	`lofty_contacts`	id PK · linked to lofty_leads
listings	`lofty_listings`	id PK · linked to lofty_leads
property searches	`lofty_property_searches`	id PK · linked to lofty_leads

FAQ

How does Datrise handle Lofty's custom fields in Microsoft SQL Server?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Microsoft SQL Server types.

How does the Lofty to Microsoft SQL Server sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with a MERGE statement.

Related pipelines

Early access

Connect Lofty to Microsoft SQL Server 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.