Source connector

Practifi connector

Practifi integration for databases, warehouses and BI tools

Salesforce-based platform for advisory firm operations. Datrise captures Practifi entities such as clients, households, entities, service requests, opportunities and review meetings, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Salesforce REST API + Bulk API + Pub/Sub API, against Practifi's custom objects on the customer's own Salesforce org authenticates with OAuth 2.0, JWT, username / password, incremental runs key on SystemModstamp, and Practifi caps calls at Not published by Practifi itself — API calls are metered against the customer's own Salesforce org's platform limits (e.g. 100,000 REST/SOAP/Bulk/Connect API calls per rolling 24 hours per org on Enterprise Edition, scaling with edition and purchased user licenses), so the effective ceiling depends on which Salesforce edition the client's Practifi org runs, not a number Practifi sets.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `practifi_clients`) with a schema derived from the Practifi API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Practifi pipeline page, and join the waitlist to get the Practifi connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Practifi data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
clients	practifi_clients	Upsert by primary key, incremental on updated-at
households	practifi_households	Upsert by primary key, incremental on updated-at
entities	practifi_entities	Upsert by primary key, incremental on updated-at
service requests	practifi_service_requests	Upsert by primary key, incremental on updated-at
opportunities	practifi_opportunities	Upsert by primary key, incremental on updated-at
review meetings	practifi_review_meetings	Upsert by primary key, incremental on updated-at

Practifi API: setup facts for the connector

Verified against the vendor documentation on 2026-09-21. Unknown values are left blank rather than guessed.

API	Salesforce REST API + Bulk API + Pub/Sub API, against Practifi's custom objects on the customer's own Salesforce org
Authentication	OAuth 2.0, JWT, username / password — Practifi's own API page names no auth flow of its own — it links straight to Salesforce's REST API Developer Guide, so a connector authenticates the same way any Salesforce integration does: a Connected App with OAuth 2.0 (JWT Bearer flow recommended for server-to-server, Username-Password flow discouraged) scoped to the customer's own Practifi/Salesforce org.
Pagination	token — SOQL `query`/`queryAll` against Practifi's objects pages the same way as any Salesforce query: up to 2,000 rows per page with `done`/`nextRecordsUrl`, per the REST API guide Practifi links to.
Rate limit	Not published by Practifi itself — API calls are metered against the customer's own Salesforce org's platform limits (e.g. 100,000 REST/SOAP/Bulk/Connect API calls per rolling 24 hours per org on Enterprise Edition, scaling with edition and purchased user licenses), so the effective ceiling depends on which Salesforce edition the client's Practifi org runs, not a number Practifi sets
Incremental cursor	SystemModstamp — SystemModstamp is a standard Salesforce system field present on every object, custom or standard, so it applies to Practifi's entity/household/opportunity objects the same way it does on core Salesforce objects; Practifi's own docs do not name it, this is inherited platform behavior.
Webhooks	Yes — Change Data Capture consumed via the Pub/Sub API
Bulk export	Yes — Salesforce Bulk API
Deletes detectable	Yes — `queryAll ... WHERE IsDeleted = true ALL ROWS` surfaces Recycle Bin records for the standard 15-day retention window, the same mechanism as any Salesforce org; Practifi does not document this itself.

Official API reference

What bites when replicating Practifi

Practifi publishes no rate-limit number of its own: the REST/Bulk/Pub-Sub call budget is whatever Salesforce edition the client's org runs (e.g. 100,000 calls/24h on Enterprise), so a connector has to ask the customer which Salesforce edition backs their Practifi instance rather than assume one Practifi-wide limit.
Practifi's own docs recommend the Bulk API specifically once a query would return more than 50,000 records, but bulk jobs still share the org-wide Salesforce Bulk API 2.0 ceilings (150,000,000 records and 15,000 batches per rolling 24 hours) with every other integration hitting that org.
Practifi recommends the Pub/Sub API (Change Data Capture events) to cut down on polling, but does not publish which of its own custom objects have CDC enabled by default — that has to be confirmed per org in Salesforce Setup before a connector can rely on it.
Because Practifi data lives as standard/custom Salesforce objects rather than a separate Practifi API surface, the usual Salesforce ID quirk applies: 15-character case-sensitive IDs in the UI vs. 18-character case-insensitive IDs from the API, which Practifi's docs never call out since it is generic platform behavior, not a Practifi-specific fact.

Compare this against every other documented API

Popular destinations for Practifi

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Practifi connector FAQ

What Practifi data does the connector extract?: 6 objects: clients, households, entities, service requests, opportunities and review meetings. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Practifi integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Practifi data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Practifi → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Practifi pipeline with guided onboarding

Join the waitlist to get priority access for Practifi integrations with guided setup, schema-aware mapping, and production-grade incremental sync.