Salesforce and Litify, connected to the rest of your firm
Whether Salesforce is your business development CRM or, through Litify, your practice management system, we make it agree with everything else your firm runs.
Salesforce & Litify integration, built around your firm
Firms use Salesforce in two ways. Some run it as the CRM for business development and intake, next to a separate practice management system. Others run Litify, a legal practice management package built on Salesforce, where every matter, intake and party is a Salesforce record. Either way, Salesforce holds data that other systems need, and it needs data that lives elsewhere.
When it isn't connected, the gaps show up quickly. A signed client is retyped into the PMS. Relationship partners can't see what happened after the engagement. Hearings and deadlines live in docketing and Outlook but not on the matter timeline in Litify. Staffing changes in one system never reach the others.
We connect Salesforce through its own APIs, using an integration user and an app your administrator controls. Changes in Salesforce trigger work in your other systems, and results are written back to the right record with an external ID, so a retry never creates a duplicate. Everything runs in your firm's Microsoft 365 and Azure tenant, and if a built-in integration already covers what you need, we'll tell you.
The Salesforce & Litify data we work with
Accounts, contacts and leads
Clients and other parties matched against your PMS by rule, with a review queue for anything that could be a duplicate.
Opportunities, intakes and matters
Stage changes such as Closed Won, or a Litify intake converting to a matter, start matter opening in your other systems.
Parties and matter teams
Who is on the matter and in what role, so access and sharing in docketing and Microsoft 365 follow the same team.
Events and tasks
Hearings, deadlines and follow-ups written as standard Salesforce events and tasks on the matter, so they appear on its timeline and in reports.
Files and notes
Documents in Salesforce Files and activity notes read or attached to the right record.
Your custom fields
Firms customize Salesforce heavily. We read your org's own objects and fields and map them during the analysis instead of assuming a standard layout.
How the Salesforce & Litify integration works
- An app your administrator owns. Your Salesforce administrator creates or installs an External Client App, the current replacement for Connected Apps, and assigns it to a dedicated integration user through a permission set. The integration authenticates with a certificate or secret held in your firm's Key Vault, and your administrator can revoke it at any time.
- Edition and permissions. API access depends on your Salesforce edition: Enterprise, Unlimited and Performance include it, and Professional needs the API add-on. Field-level security applies to the integration user, so a field it can't see is simply missing. We confirm permissions, including any Litify permission sets, before the build starts.
- Events, not constant polling. Salesforce can push changes through Change Data Capture and Platform Events over its Pub/Sub API, or through a record-triggered Flow that calls an endpoint in your tenant. Change Data Capture covers a limited number of objects unless your org has the add-on, and event delivery counts against an allocation set by edition, so we choose the mechanism per object and add a scheduled reconciliation as a safety net.
- Litify specifics. Litify records are reached through the standard Salesforce APIs, but Litify does not publish a public object reference, so we confirm object and field names in your org. Litify publishes an API Integration Agreement for commercial integrators, and its Docrio document store has a separate API with its own key issued by Litify. We settle with you and Litify which of these apply before work starts.
- Runs in your tenant. The integration is deployed into your firm's Azure subscription, with secrets in your Key Vault and every write logged in your own environment. Our own writes are tagged so they don't come back around as new changes.
Where Salesforce & Litify fits
Signed client → matter open everywhere at once
Matter opening goes from days of handoffs to minutes, and every system starts with the same data.
CRM that knows what happened after the client signed
Business development decisions based on what is actually happening in each matter.
Two-way matter sync: practice management ↔ docketing
One matter, identical in every system, without anyone keying it twice.
Often connected with
Questions about connecting Salesforce & Litify
We use Litify. Is that different from a Salesforce integration?
Technically it is the same platform: Litify matters, intakes and parties are Salesforce records reached through the same APIs. The differences are practical. Litify object names have to be confirmed in your org, its Docrio documents use a separate API, and Litify has its own integration agreement for commercial integrators, which we review with you before starting.
Will this use up our Salesforce API or event limits?
Every integration uses some of your org's allocation, so we size it during the analysis. We filter events at the source, batch writes where Salesforce allows it, and avoid polling where an event will do. You can see usage in Salesforce at any time.
What access does the integration need?
A dedicated integration user with a permission set limited to the objects and fields in the agreed design, plus an External Client App your administrator creates or approves. Nothing runs under a named person's login, so a staff change won't break it.
Can deadlines from our docketing system show up in Salesforce?
Yes. Deadlines and hearings can be written as events or tasks on the matter, keyed to an external ID so later changes update the same record instead of creating another. The deadlines are still calculated and owned by your docketing system.
Running Salesforce & Litify with other systems?
Tell us what you use and where your staff re-key data. We’ll tell you honestly what’s possible, and what your vendors already cover.