Follow Up Boss to Azure Synapse Integration

How Datrise loads Follow Up Boss into Azure Synapse

Datrise syncs Follow Up Boss's leads, people, deals, action plans, calls, and agent assignments into Azure Synapse 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 COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Follow Up Boss: Real estate lead routing and agent follow-up cadences.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Follow Up Boss entities map to Azure Synapse

Follow Up Boss entity	Azure Synapse object	Notes
leads	`follow_up_boss_leads`	id PK · custom fields → NVARCHAR(MAX) JSON columns
people	`follow_up_boss_people`	id PK · linked to follow_up_boss_leads
deals	`follow_up_boss_deals`	id PK · linked to follow_up_boss_leads
action plans	`follow_up_boss_action_plans`	id PK · linked to follow_up_boss_leads

FAQ

How does Datrise handle Follow Up Boss's custom fields in Azure Synapse?

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 Azure Synapse types.

How does the Follow Up Boss to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Follow Up Boss to Azure Synapse 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.