How clients, matters, timekeepers and billing results in Elite 3E (formerly Thomson Reuters Elite), in the cloud or on premises, 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 3E.
Elite 3E is a financial and practice management system for law firms: intake and conflicts, clients and matters, time, billing, collections and the general ledger. Business development and marketing teams need a slice of that data to do their work, and HubSpot is where they do it.
Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.
Open with conditions. The 3E REST and OData APIs are documented. For 3E Cloud the firm registers an app in its own Entra ID, and Elite Support issues the subscription key.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Elite publishes 3E REST and OData APIs, so HubSpot can see every client relationship the firm has without holding a single privileged detail.
Campaign Creators assessment
Elite's developer portal documents the 3E API (REST), which can retrieve, add and modify records such as clients and matters, and the 3E OData API, which documents Client, Matter, Timekeeper, Payor and Time Entry. Both serve 3E Cloud and on-premises firms. In the cloud, the firm enables the APIs through an app registration in its own Microsoft Entra ID, and calls use OAuth 2.0 tokens. Two things set the pace. 3E Cloud publishes call limits that suit summary syncs, not bulk extracts. And the firm's general counsel or risk team decides which client and matter fields may leave 3E at all, before any build starts.
Ratings are CC judgments from Elite's public developer portal. Some samples and knowledge base articles need an Elite customer login, so attribute names are confirmed against the firm's 3E metadata in discovery.
The same 3E API covers cloud and on-premises firms. On premises it installs with 3E and authenticates with Windows Authentication; in the cloud it uses OAuth 2.0 client credentials from the firm's Entra ID.
Matter descriptions, time narratives and conflicts results stay in 3E. 3E Cloud allows 60 OData calls and 30 REST calls a minute, so the design syncs changes and summaries, not full history on every run.
The firm's general counsel or risk team signs off the field list, and the firm creates the app registration and requests a subscription key from Elite Support, before the build begins.
Seven 3E areas are relevant to HubSpot. Four carry the integration, one handles volume, one stays inside 3E, and one is a scope decision to make early.
The firm's clients and every matter opened for them, with practice area, office, status and the 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 into the firm's 3E intake and conflicts workflow.
Elite positions its OData and REST APIs for lower-volume integrations and points larger extracts to 3E Change Stream, which registers a webhook for data changes.
Time entry narratives, matter descriptions, documents, trust receipts and conflicts search results stay in 3E. 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 3E never talk directly. A CC-built integration layer reads 3E through its APIs, applies the approved field list, matches each record, and writes to HubSpot in batches. It also carries intake requests from HubSpot into 3E.
HubSpot owns marketing, contacts, pitches and events. 3E 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 3E.
Reads filter on Timestamp and page through results, so routine syncs fit 3E Cloud's call limits. Larger volumes move to Change Stream.
Each phase ends on a gate the firm signs off before the next begins. Read-only flows go live first, so business development sees 3E 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 3E. CC describes options; the firm makes the decision.
3E Cloud: the firm creates the Entra ID app registration, shares the client ID, secret and scope, and requests a subscription key from Elite Support. On premises: the firm's IT team grants a service account and network path.
Agree which system owns each record, how clients match HubSpot companies, how timekeepers map to HubSpot users, and how practice areas map to HubSpot values.
Create the e3_ properties, the Matter custom object, the pitch pipeline, and field-level permissions for financial fields in a HubSpot sandbox.
Build the client, matter, timekeeper and billing summary sync modules with Timestamp-filtered reads, paging, idempotent writes and an error replay queue.
Build the won-pitch intake request into the firm's 3E intake and conflicts workflow, and the matter number return. Test against the Preview instance first.
Load clients, open matters and an agreed history window within the call limits, compute summaries once, run two weeks in parallel, then switch on intake requests.
Object names (Client, Matter, Timekeeper, Payor, Time Entry) and the Timestamp attribute follow Elite's OData documentation. Other attributes are described plainly and confirmed against the firm's 3E metadata, which the OData API exposes, in discovery.
| Elite 3E field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Client | ||||
| Client number | e3_client_number | Company | ↔ Both | Primary match key. Written to HubSpot when 3E opens the client. |
| Client name | name | Company | 3E → HS | 3E name wins once the client exists. |
| Client address | address, city, state, zip, country | Company | 3E → HS | Main address. Confirm attribute in discovery. |
| Industry | e3_industry | Company | 3E → HS | Firm's industry codes mapped to a HubSpot dropdown. |
| Client status | e3_client_status | Company | 3E → HS | Active or inactive. |
| Relationship timekeeper | e3_relationship_partner, hubspot_owner_id | Company | 3E → HS | Owner set when the attorney is a HubSpot user. |
| Payor and billing contact | firstname, lastname, email | Contact | 3E → HS | From the Payor object. Fill blanks only. |
| Matter | ||||
| Matter number | e3_matter_number | Matter (custom object) | 3E → HS | Primary match key for matters. Unique. |
| Matter name | e3_matter_name | Matter (custom object) | 3E → HS | Only if the risk team approves; otherwise a neutral label. |
| Practice area / department | e3_practice_area | Matter (custom object) | 3E → HS | Mapped to a HubSpot dropdown. |
| Office | e3_office | Matter (custom object) | 3E → HS | Matter office. |
| Matter status | e3_matter_status | Matter (custom object) | 3E → HS | Open, closed or pending. |
| Open date and close date | e3_open_date, e3_close_date | Matter (custom object) | 3E → HS | Close date can start a feedback survey. |
| Originating timekeeper | e3_originating_attorney | Matter (custom object) | 3E → HS | Confirm role attributes in discovery. |
| Responsible timekeeper | e3_responsible_attorney | Matter (custom object) | 3E → HS | Lead attorney on the matter. |
| Timestamp | e3_last_changed | Matter (custom object) | 3E → HS | Last change in 3E. Also the change filter for reads. |
| Client on matter | Matter ↔ Company association | Matter (custom object) | 3E → HS | Matched on client number. |
| Timekeeper | ||||
| Timekeeper number | e3_timekeeper_id | Contact | 3E → HS | For attorneys tracked as contacts, such as alumni. |
| Timekeeper name and email | HubSpot user | User | 3E → HS | Matched to HubSpot users by email for ownership. |
| Department, section and office | e3_practice_area, e3_office | Contact | 3E → HS | Used for routing and event invitations. |
| Departed status | e3_alumni | Contact | 3E → HS | Only if the firm approves an alumni program. |
| Client-level billing summaries | ||||
| Fees billed, trailing 12 months | e3_fees_billed_ttm | Company | 3E → HS | Calculated in the integration layer. Restricted view. |
| Fees collected, trailing 12 months | e3_fees_collected_ttm | Company | 3E → HS | Restricted view. |
| Realization rate | e3_realization_rate | Company | 3E → HS | Collected as a share of standard value. Formula agreed with finance. |
| Open receivable balance | e3_ar_balance | Company | 3E → HS | Sum of open bills. Restricted view. |
| Practice areas with matters | e3_practice_areas_served | Company | 3E → HS | Multi-select. Drives cross-sell lists. |
| Intake requests | ||||
| Prospective client and contact | Company, Contact | Company | HS → 3E | Sent from the won pitch. |
| Proposed matter details | dealname, e3_practice_area | Deal | HS → 3E | Neutral description only; the intake team completes the rest in 3E. |
| Intake status | e3_intake_status | Deal | 3E → HS | Submitted, approved or not opened. No conflicts detail. |
| New matter number | e3_matter_number | Deal | 3E → HS | Links the deal to the Matter record. |
Values below come from Elite's developer portal. Items Elite leaves to the firm or to its knowledge base are marked for confirmation.
| Topic | Elite 3E | HubSpot |
|---|---|---|
| Access model | 3E Cloud: the firm enables the APIs through an app registration in its Microsoft Entra ID and shares the credentials with its integrator. Elite Support issues the subscription key. On premises: the API installs with the 3E user interface packages. | Self-serve in the client portal. Custom objects and field-level permissions need an Enterprise hub. |
| Interfaces | 3E API (REST) for retrieving, adding and modifying records; 3E OData API for querying, creating and updating (no DELETE). Base URL pattern api.elite.com/[environment]/3e/odata. | REST APIs: CRM objects, custom objects, associations, imports. |
| Authentication | 3E Cloud: OAuth 2.0 client credentials from the firm's Entra ID tenant, with separate Live and Preview scopes. Calls carry a bearer token, the X-3E-InstanceId header and the x-subscription-key header. On premises: Windows Authentication. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Change detection | OData filters on Timestamp, sorted and paged. 3E Change Stream registers a webhook for data changes; confirm setup with Elite. | Webhooks for HubSpot changes such as a deal moving to won. |
| Rate limits | 3E Cloud: 60 calls a minute for OData, 30 for REST, 5,000 rows per OData page or call with a next-page link. On premises: set by the firm. | Per-10-second burst and daily limits by subscription tier. |
| Environments | Live and Preview instances in 3E Cloud, each with its own scope and instance ID. Build and test against Preview. | HubSpot sandbox for the data model and test syncs. |
| Confidential data | Narratives, documents, trust receipts and conflicts results are excluded. Only fields on the signed list leave 3E. | 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 3E or is replaced with a neutral label.
In 3E Cloud the firm creates the app registration and requests the subscription key. Make both a firm-owned dependency in the SOW, with a date for the Preview instance first.
60 OData and 30 REST calls a minute shape the backfill. Plan the history load in pages over several runs, or use Change Stream where the firm has it.
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.
3E is highly configurable, and firms add their own attributes and workflows. Read the firm's 3E metadata through the OData API and map field by field in discovery.
Revenue and realization are sensitive inside a partnership. Restrict them with field-level permissions and agree who sees them before backfill.
Each client shows the practice areas 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 3E can add the agreed client contact to a HubSpot feedback survey list.
Departed timekeepers, 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; 3E runs intake and conflicts, the matter and the bill, and reports back a summary.
All custom properties use the e3_ prefix in an Elite 3E 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 |
|---|---|---|---|---|
| e3_client_number | 3E Client Number | Company | Single-line text | Client number; unique |
| e3_industry | Industry (3E) | Company | Dropdown | Firm industry codes |
| e3_relationship_partner | Relationship Partner | Company | Single-line text | Relationship timekeeper on the client |
| e3_practice_areas_served | Practice Areas Served | Company | Multiple checkboxes | Practice areas with open or recent matters |
| e3_fees_billed_ttm | Fees Billed (12 months) | Company | Number (currency) | Sum of bills, trailing 12 months; restricted |
| e3_realization_rate | Realization Rate | Company | Number (percent) | Formula agreed with finance; restricted |
| e3_ar_balance | Open Receivable Balance | Company | Number (currency) | Sum of open bills; restricted |
| e3_matter_number | 3E Matter Number | Matter / Deal | Single-line text | Matter number; unique on Matter |
| e3_practice_area | Practice Area | Matter / Deal | Dropdown | 3E department or practice area |
| e3_matter_status | Matter Status | Matter | Dropdown | Open, closed, pending |
| e3_originating_attorney | Originating Attorney | Matter | Single-line text | Originating timekeeper on the matter |
| e3_intake_status | Intake Status | Deal | Dropdown | Submitted, approved, not opened |
Choose the 3E 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 Elite and HubSpot. Each item marked for confirmation is verified with Elite 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. Elite publishes 3E REST and OData APIs covering clients, matters, timekeepers, payors and time entries, for both 3E Cloud and on-premises firms. Campaign Creators builds a custom integration layer on these APIs once the firm grants API credentials and the risk team approves the field list.
Clients, matters, timekeepers and client-level billing summaries such as fees billed, fees collected, realization and open balance sync from 3E to HubSpot companies, contacts and a Matter custom object. A won HubSpot pitch sends a pre-filled intake request into 3E's intake and conflicts workflow, and 3E returns only the intake status and new matter number.
Each record has one owner: HubSpot owns marketing, contacts, pitches and events, while 3E owns clients, matters, conflicts, time, billing and the general ledger. HubSpot holds matter summaries and client-level totals only; narratives, documents, conflicts results and trust data never leave 3E.
Seven phases, each closed by a firm sign-off: a risk and confidentiality review of every candidate field, API access through an Entra ID app registration and subscription key for 3E Cloud, ownership and match rules, the HubSpot data model, building the read-sync modules, the intake request flow, and a two-week parallel run before intake requests go live.
Timeline and cost depend on the firm's 3E deployment, the fields the risk team approves and the call limits in scope. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.