Keep Centerbase matters and the systems around them in agreement.
We connect Centerbase to your docketing, CRM, document management and Microsoft 365, so matters, teams and dates stay the same in every system your firm uses.
Centerbase integration, built around your firm
Centerbase combines practice management, billing and legal accounting in one system, so it is usually the firm's record for clients, matters, responsible attorneys, time and money. The systems around it, from docketing to the CRM to the document workspace, need that matter list to be complete and correct.
Centerbase already includes Microsoft 365 features such as Office 365 calendar sync. The gaps appear between Centerbase and everything else: a matter opened in Centerbase that never reaches the CRM, a responsible attorney change that docketing doesn't hear about, an intake record that has to be rekeyed as a matter. Relationship partners end up asking accounting for numbers Centerbase already has.
We fill those gaps with the Centerbase public API. Because Centerbase does not push changes, the integration checks for them on a schedule and reconciles regularly. It runs in your firm's Microsoft 365 / Azure tenant, follows rules your firm approves, and routes anything uncertain to a person for review. Your firm owns the code and can see every change it makes. If a built-in Centerbase integration covers what you need, we'll tell you.
The Centerbase data we work with
Matters
Create and update matters, including matter name and number, client, status, practice area, responsible attorney, billing partner and open and close dates.
Contacts and clients
Contacts, clients, addresses, phone numbers and email addresses, plus potential new clients from intake.
Appointments and tasks
Create and update calendar appointments and tasks linked to a matter, with dates, location and responsible attorney.
Time entries
Create billing entries with date, timekeeper, matter, hours and description, flagged for review before they are billed.
Notes and custom fields
Matter notes, and any custom field your firm has added to Centerbase records.
Financial data, read only
Bills, payments and trust transactions can be read for partner dashboards and CRM rollups. We don't write to them.
How the Centerbase integration works
- A dedicated Centerbase user. Centerbase's API signs in with a Centerbase user name and password, not OAuth. We use a dedicated user with only the security rights the integration needs, and its password is held in your Key Vault. If your firm signs in with Microsoft Entra, that user still needs its own Centerbase password.
- Polling, not push. Centerbase has no webhooks. The integration checks for new and changed records on a schedule, can use saved queries your administrator sets up in Centerbase, and reconciles the full matter list regularly to catch closures and removals.
- Field mapping at onboarding. Centerbase identifies every field by a number, and custom fields differ from firm to firm. We map your fields with your administrator before anything is written, and that mapping is part of the documentation you keep.
- Working with the built-in Office 365 sync. If your firm uses Centerbase's Office 365 calendar sync, we design around its settings so each date reaches Outlook and Centerbase once. The public API does not delete records or carry document files, so documents are handled in SharePoint or your DMS.
- Runs in your tenant. The integration runs in your firm's Azure subscription under its own identity, with every change logged. Disabling the Centerbase user or the Azure resources stops it immediately, without us.
Where Centerbase fits
Two-way matter sync: practice management ↔ docketing
One matter, identical in every system, without anyone keying it twice.
CRM that knows what happened after the client signed
Business development decisions based on what is actually happening in each matter.
Signed client → matter open everywhere at once
Matter opening goes from days of handoffs to minutes, and every system starts with the same data.
Often connected with
Questions about connecting Centerbase
Centerbase already works with Microsoft 365. What do you add?
Centerbase's own features connect Centerbase to Outlook and SharePoint. We connect it to the other systems your firm runs, such as the CRM, docketing and the DMS, and apply your firm's rules across all of them. If a built-in feature already does the job, we'll say so.
Why does the integration need a Centerbase password?
That is how Centerbase's public API signs in. We ask for a dedicated user created only for the integration, with the minimum rights it needs, and the password lives in your Key Vault rather than with us. Disabling that user cuts off access at once.
How quickly do changes in Centerbase reach other systems?
Centerbase doesn't send notifications, so changes are picked up on a schedule, typically every few minutes for matters and less often for slower-moving data. We agree the timing with you during the analysis.
Can relationship partners see billing data in the CRM?
Yes. Bills, payments and trust balances can be read through the API, so fees billed and collected can be rolled up to the client record in Salesforce or HubSpot. The integration reads that financial data only and never changes it.
Running Centerbase 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.