How clients, matters, attorneys and billing results in Aderant Expert (on premises) or Expert Sierra (cloud) can give a law firm's business development and marketing team a full client picture in HubSpot, how a won pitch becomes an intake request, and how privileged matter detail stays inside Aderant.
Aderant Expert Sierra runs the business side of a law firm: conflicts checks and file opening, clients and matters, time, billing, rates, collections and the ledger. Business development and marketing teams need a slice of that data to do their work, and HubSpot is where they do it.
Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.
Gated API. API documentation and credentials are issued by Aderant under its API terms. SQL access is granted by the firm's IT team and Aderant.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Aderant supports API and database integration, so HubSpot can see every client relationship the firm has without holding a single privileged detail.
Campaign Creators assessment
Aderant states that Expert Sierra supports REST and SOAP APIs, with OAuth for the REST APIs, alongside its Generic Importer, secure file transfer, secure SQL access over VPN and data warehouse integrations. Firms on Expert in their own data center can also read the Expert database directly. That makes a HubSpot integration buildable on either deployment. Two things set the pace. Aderant's API documentation and credentials come through Aderant rather than a public developer portal. And the firm's general counsel or risk team decides which client and matter fields may leave Aderant at all, before any build starts.
Ratings are CC judgments from Aderant's public materials. Aderant does not publish its API reference, so endpoints, field names and limits are confirmed with Aderant and the firm's IT team in discovery.
Aderant already holds who the client is, which practice groups serve it, which attorneys originate and lead the work, and what the relationship is worth. HubSpot receives that picture instead of rebuilding it by hand.
Matter descriptions, time narratives, documents and conflicts results can reveal privileged or confidential information. The design keeps them in Aderant and sends HubSpot only approved summary fields.
The firm's general counsel or risk team signs off the field list, and Aderant issues the API credentials or the firm grants SQL access, before the build begins.
Seven Aderant areas are relevant to HubSpot. Four carry the integration, one is the build path, one stays inside Aderant, and one is a scope decision to make early.
The firm's clients and every matter opened for them, with the practice group, office, status and attorneys on each matter.
The attorneys who bring in and lead each client and matter. In HubSpot they become owners or relationship fields, so business development knows who to involve.
Billing, collections and receivables by client. The integration layer turns them into a few client-level summaries such as fees billed, fees collected, realization and open balance.
When a pitch is won in HubSpot, the integration sends a pre-filled intake request to the firm's conflicts check and file opening process in Aderant.
Aderant lists REST and SOAP APIs, its Generic Importer, secure file transfer and secure SQL access over VPN. The build uses the APIs where they cover the data and SQL reads where the firm allows them.
Time entry narratives, matter descriptions, documents, trust balances and conflicts search results stay in Aderant. HubSpot never receives them.
Client revenue and realization are sensitive inside the firm. Decide which teams and roles may see them in HubSpot, and whether they appear at all.
HubSpot and Aderant never talk directly. A CC-built integration layer reads Aderant on a schedule, applies the approved field list, matches each record, and writes to HubSpot in batches. It also carries intake requests from HubSpot into Aderant.
HubSpot owns marketing, contacts, pitches and events. Aderant owns clients, matters, conflicts, time, billing and the ledger.
HubSpot holds matter summaries and client-level totals. Narratives, documents, conflicts results and trust data never leave Aderant.
The confidentiality filter passes only fields the firm's general counsel or risk team approved. Changing the list is a signed change, not a setting.
Each phase ends on a gate the firm signs off before the next begins. Read-only flows go live first, so business development sees Aderant data in HubSpot before HubSpot sends anything back.
With the firm's general counsel or risk team, classify every candidate field and agree what HubSpot may hold, who may see it, and what stays in Aderant. CC describes options; the firm makes the decision.
Confirm the deployment (Expert on premises or Expert Sierra), request API credentials and documentation through Aderant, and set up SQL or VPN access where the firm approves it.
Agree which system owns each record, how clients match HubSpot companies, how attorneys map to HubSpot users, and how practice groups map to HubSpot values.
Create the adr_ properties, the Matter custom object, the pitch pipeline, and field-level permissions for financial fields in a HubSpot sandbox.
Build the client, matter, attorney and billing summary sync modules with modified-since reads, idempotent writes and an error replay queue.
Build the won-pitch intake request into the firm's conflicts check and file opening process, and the matter number return.
Load clients, open matters and an agreed history window, compute summaries once, run two weeks in parallel, then switch on intake requests.
Aderant does not publish its API reference, so Aderant fields are described plainly. Exact field names, tables and endpoints are confirmed with Aderant and the firm's IT team in discovery.
| Aderant field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Clients | ||||
| Client number | adr_client_number | Company | ↔ Both | Primary match key. Written to HubSpot when Aderant opens the client. |
| Client name | name | Company | ADR → HS | Aderant name wins once the client exists. |
| Client address | address, city, state, zip, country | Company | ADR → HS | Main address. Confirm field in discovery. |
| Industry | adr_industry | Company | ADR → HS | Firm's industry codes mapped to a HubSpot dropdown. |
| Client status | adr_client_status | Company | ADR → HS | Active or inactive. |
| Relationship partner | adr_relationship_partner, hubspot_owner_id | Company | ADR → HS | Owner set when the attorney is a HubSpot user. |
| Client contacts | firstname, lastname, email | Contact | ADR → HS | Billing and client contacts. Fill blanks only. |
| Matters | ||||
| Matter number | adr_matter_number | Matter (custom object) | ADR → HS | Primary match key for matters. Unique. |
| Matter name | adr_matter_name | Matter (custom object) | ADR → HS | Only if the risk team approves; otherwise a neutral label. |
| Practice group / department | adr_practice_group | Matter (custom object) | ADR → HS | Mapped to a HubSpot dropdown. |
| Office | adr_office | Matter (custom object) | ADR → HS | Matter office. |
| Matter status | adr_matter_status | Matter (custom object) | ADR → HS | Open, closed or pending. |
| Open date and close date | adr_open_date, adr_close_date | Matter (custom object) | ADR → HS | Close date can trigger a feedback survey. |
| Originating attorney | adr_originating_attorney | Matter (custom object) | ADR → HS | Confirm role names in discovery. |
| Responsible attorney | adr_responsible_attorney | Matter (custom object) | ADR → HS | Lead attorney on the matter. |
| Client on matter | Matter ↔ Company association | Matter (custom object) | ADR → HS | Matched on client number. |
| Attorneys | ||||
| Timekeeper ID | adr_timekeeper_id | Contact | ADR → HS | For attorneys tracked as contacts, such as alumni. |
| Attorney name and email | HubSpot user | User | ADR → HS | Matched to HubSpot users by email for ownership. |
| Attorney practice group and office | adr_practice_group, adr_office | Contact | ADR → HS | Used for routing and event invitations. |
| Departed status | adr_alumni | Contact | ADR → HS | Only if the firm approves an alumni program. |
| Client-level billing summaries | ||||
| Fees billed, trailing 12 months | adr_fees_billed_ttm | Company | ADR → HS | Calculated in the integration layer. Restricted view. |
| Fees collected, trailing 12 months | adr_fees_collected_ttm | Company | ADR → HS | Restricted view. |
| Realization rate | adr_realization_rate | Company | ADR → HS | Collected as a share of standard value. Formula agreed with finance. |
| Open receivable balance | adr_ar_balance | Company | ADR → HS | Sum of open bills. Restricted view. |
| Practice groups with matters | adr_practice_groups_served | Company | ADR → HS | Multi-select. Drives cross-sell lists. |
| Intake requests | ||||
| Prospective client and contact | Company, Contact | Company | HS → ADR | Sent from the won pitch. |
| Proposed matter details | dealname, adr_practice_group | Deal | HS → ADR | Neutral description only; the intake team completes the rest in Aderant. |
| Adverse and related parties | adr_related_parties | Deal | HS → ADR | Only if the risk team wants them collected in HubSpot. Off by default. |
| Intake status | adr_intake_status | Deal | ADR → HS | Submitted, approved or not opened. No conflicts detail. |
| New matter number | adr_matter_number | Deal | ADR → HS | Links the deal to the Matter record. |
Aderant issues API credentials and documentation to its customers. Values Aderant does not publish are marked for confirmation.
| Topic | Aderant | HubSpot |
|---|---|---|
| Access model | API credentials are assigned by Aderant under its API terms, which also govern use and limits. SQL or VPN access is granted by the firm's IT team and Aderant. | Self-serve in the client portal. Custom objects and field-level permissions need an Enterprise hub. |
| Interfaces | REST and SOAP APIs, Generic Importer, secure file transfer and secure SQL access. Confirm which data each API covers in discovery. | REST APIs: CRM objects, custom objects, associations, imports. |
| Authentication | OAuth for the REST APIs. SQL access over VPN for Expert Sierra; database credentials for Expert on premises. Confirm in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Change detection | Scheduled reads of changed records. Confirm the modified-date fields available in discovery. | Webhooks for HubSpot changes such as a deal moving to won. |
| Rate limits | Not published. Confirm with Aderant. | Per-10-second burst and daily limits by subscription tier. |
| Hosting & network | Expert Sierra is hosted by Aderant on AWS; Expert runs in the firm's data center. Confirm network paths and allowlisting. | Hosted by HubSpot; the integration layer calls HubSpot over HTTPS. |
| Confidential data | Narratives, documents, trust data and conflicts results are excluded. Only fields on the signed list leave Aderant. | Field-level permissions restrict who sees financial properties; sensitive data properties on Enterprise. |
Severity reflects impact on the SOW, not technical difficulty alone.
A matter name or description can reveal a client's legal problem. The risk team approves every field, and anything doubtful stays in Aderant or is replaced with a neutral label.
Aderant does not publish its API reference. Make API access and documentation a firm-owned dependency in the SOW, and budget a discovery spike to confirm coverage.
HubSpot sends an intake request and receives only a status and a matter number. It never stores conflicts search results or the reason a matter was not opened.
Revenue and realization are sensitive inside a partnership. Restrict them with field-level permissions and agree who sees them before backfill.
Originating, responsible and billing attorney roles are named and used differently from firm to firm. Map them field by field in discovery.
Expert on premises allows direct database reads; Expert Sierra uses APIs and SQL access over VPN. Confirm the deployment before estimating.
Each client shows the practice groups already serving it, so business development builds lists of clients missing a practice the firm offers.
A won pitch sends a pre-filled intake request, and the matter number comes back to the deal, so marketing can tie programs to new matters.
Partners see fees billed, collected and realization on the client record, next to every pitch, event and touchpoint.
Seminar and CLE attendees are linked to client companies, so the firm sees which events precede new matters.
A matter closing in Aderant can add the agreed client contact to a HubSpot feedback survey list.
Departed attorneys, if the firm approves, become an alumni list for newsletters, events and referrals.
Each step hands the record to the system that owns it. HubSpot runs relationships, pitches and events; Aderant runs the conflicts check, the matter and the bill, and reports back a summary.
All custom properties use the adr_ prefix in an Aderant property group. Billing summaries are calculated in the integration layer so every report agrees, and financial properties are restricted by field-level permissions.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| adr_client_number | Aderant Client Number | Company | Single-line text | Client number; unique |
| adr_industry | Industry (Aderant) | Company | Dropdown | Firm industry codes |
| adr_relationship_partner | Relationship Partner | Company | Single-line text | Attorney on the client |
| adr_practice_groups_served | Practice Groups Served | Company | Multiple checkboxes | Practice groups with open or recent matters |
| adr_fees_billed_ttm | Fees Billed (12 months) | Company | Number (currency) | Sum of bills, trailing 12 months; restricted |
| adr_realization_rate | Realization Rate | Company | Number (percent) | Formula agreed with finance; restricted |
| adr_ar_balance | Open Receivable Balance | Company | Number (currency) | Sum of open bills; restricted |
| adr_matter_number | Aderant Matter Number | Matter / Deal | Single-line text | Matter number; unique on Matter |
| adr_practice_group | Practice Group | Matter / Deal | Dropdown | Aderant practice group or department |
| adr_matter_status | Matter Status | Matter | Dropdown | Open, closed, pending |
| adr_originating_attorney | Originating Attorney | Matter | Single-line text | Attorney role on the matter |
| adr_intake_status | Intake Status | Deal | Dropdown | Submitted, approved, not opened |
Choose the Aderant areas and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the firm.
Based on public documentation from Aderant and HubSpot. Each item marked for confirmation is verified with Aderant and the firm's IT team during the access phase. Nothing here is legal advice; the firm's general counsel or risk team decides what client data HubSpot may hold.
Yes. Aderant states that Expert Sierra supports REST and SOAP APIs, with OAuth for the REST APIs, alongside secure SQL access and file imports, and firms running Expert in their own data center can read the database directly. Campaign Creators builds a custom integration layer on these, with API documentation and credentials issued through Aderant.
Clients sync to HubSpot companies and client contacts to contacts; matters sync to a Matter custom object with practice group, office, status and attorneys; and client-level billing summaries such as fees billed, fees collected, realization and open balance are written to the company. A won pitch sends an intake request to Aderant, and HubSpot receives the intake status and new matter number.
Each record has one owner. HubSpot owns marketing, contacts, pitches and events; Aderant owns clients, matters, conflicts, time, billing and the ledger. Time narratives, documents, trust data and conflicts results never leave Aderant, and the firm’s general counsel or risk team approves every field HubSpot holds.
Seven phases, each closed by a firm sign-off: a risk and confidentiality review, access through Aderant, ownership and match rules, the HubSpot data model and permissions, read sync modules, the intake request flow, and backfill with a two-week parallel run before intake requests are switched on.
Timeline and cost depend on the records, fields and Aderant features in scope (for example Expert on premises or Expert Sierra, the approved field list and the intake request flow). Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.