A HubSpot Elite Solutions Partner built to help organizations unify strategy, systems, and execution. We design HubSpot systems that scale.

See how we've solved complex HubSpot challenges across migrations, integrations, CMS, automation, and optimization.

Join a team building smarter HubSpot systems. We value strategic thinkers who move proactively, care about quality, and want to do meaningful work.

Integration

HubSpot <> Elite 3E Integration

Powered by Commercient
Integration Assessment
Integration Assessment · Legal

Elite 3E × HubSpot

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.

3E Cloud and on premises3E REST API3E OData APIOAuth 2.0 client credentialsIntake and conflictsCustom build
Platform ownerElite (formerly Thomson Reuters Elite)
Integration typeCustom, on the 3E REST and OData APIs
Primary direction3E → HubSpot, intake requests back
FeasibilityBuildable, credentials granted by the firm
API accessOpen with conditions
01 — Summary

Does Elite 3E integrate with HubSpot?

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.

API access
Open APIOpen with conditionsGated API

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.

Scorecard
Data richnessHigh
API accessFirm-granted
Public docsPartial
Build complexityModerate

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.

Strength

Documented APIs for both deployments

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.

Plan for

Privilege and call limits

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.

Gate

Risk team approval and firm credentials

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.

02 — API modules

Which Elite 3E APIs does the integration use?

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.

Core

Clients & matters

OData Client and Matter · REST API

The firm's clients and every matter opened for them, with practice area, office, status and the attorneys on each matter.

  • Client and matter numbers become HubSpot match keys
  • Matters land on a custom object linked to the client
  • Timestamp filters return only changed records
Core

Timekeepers

OData Timekeeper

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.

  • Originating and responsible roles per matter
  • Department, section and office per timekeeper
  • Mapped to HubSpot users where attorneys log in
Core

Billing & collections

Payor · billing and receivables

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.

  • Rollups only, never bill or time detail
  • Visible to partners and business development only
  • 3E stays the ledger
Core

Intake & conflicts

Intake requests from HubSpot

When a pitch is won in HubSpot, the integration sends a pre-filled intake request into the firm's 3E intake and conflicts workflow.

  • Client, contact and matter details from the deal
  • Conflicts searching and approval stay in 3E
  • HubSpot receives the new matter number when opened
Volume

Change Stream & volume

Webhooks for data changes

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.

  • OData pages of up to 5,000 rows
  • Change Stream for larger change volumes
  • Confirm availability for the firm's 3E version
Stays in 3E

Narratives, documents & conflicts results

Privileged and confidential detail

Time entry narratives, matter descriptions, documents, trust receipts and conflicts search results stay in 3E. HubSpot never receives them.

  • No narratives or documents in HubSpot
  • Conflicts outcome shown only as intake status
  • Confirm the excluded list with the risk team
Scope decision

Who sees financial data

Scope decision

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.

  • Recommended: partners and business development only
  • HubSpot field-level permissions restrict viewing
  • Marketing sees segments, not dollar values
03 — Framework

How does the Elite 3E HubSpot integration work?

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.

Elite 3E
Clientsclient number, industry, office
Matterspractice area, status, timekeepers
Billing & collectionsbilled, collected, receivables
Intake & conflictsintake requests, new matters
CC integration layer
API clientOAuth 2.0 token, instance ID, subscription key
Change readerTimestamp filters or Change Stream
Identity resolverclient number · matter number · domain · email
Confidentiality filterpasses only approved fields
HubSpot writerbatch upserts, error replay
HubSpot
Companiesclients and prospects
Contactsclient contacts, alumni, referral sources
Matters (custom object)matter summaries linked to clients
Dealspitches and new business
Events, lists & feedbackseminars, segments, client surveys
3E → HubSpot (clients, matters, timekeepers, client-level billing summaries, intake status)HubSpot → 3E (intake requests for won pitches)
Principle

Each record has one owner

HubSpot owns marketing, contacts, pitches and events. 3E owns clients, matters, conflicts, time, billing and the ledger.

Principle

Summaries, not privileged detail

HubSpot holds matter summaries and client-level totals. Narratives, documents, conflicts results and trust data never leave 3E.

Principle

Stay inside the published limits

Reads filter on Timestamp and page through results, so routine syncs fit 3E Cloud's call limits. Larger volumes move to Change Stream.

04 — Process

What does Elite 3E HubSpot integration setup involve?

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.

1

Risk & confidentiality review

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.

Gate to next phaseSigned field list and visibility rules
2

Access

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.

Gate to next phaseTest call to the Preview instance returns matters
3

Ownership & match rules

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.

Gate to next phaseSigned ownership map and match rules
4

HubSpot data model & permissions

Create the e3_ properties, the Matter custom object, the pitch pipeline, and field-level permissions for financial fields in a HubSpot sandbox.

Gate to next phaseSchema and permissions approved in sandbox
5

Build read sync modules

Build the client, matter, timekeeper and billing summary sync modules with Timestamp-filtered reads, paging, idempotent writes and an error replay queue.

Gate to next phaseSandbox records reconcile to 3E reports
6

Intake request flow

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.

Gate to next phaseTest intake requests accepted by the intake team
7

Backfill, parallel run & launch

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.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Elite 3E HubSpot integration sync?

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 fieldHubSpot propertyObjectDirectionNotes
Client
Client numbere3_client_numberCompany↔ BothPrimary match key. Written to HubSpot when 3E opens the client.
Client namenameCompany3E → HS3E name wins once the client exists.
Client addressaddress, city, state, zip, countryCompany3E → HSMain address. Confirm attribute in discovery.
Industrye3_industryCompany3E → HSFirm's industry codes mapped to a HubSpot dropdown.
Client statuse3_client_statusCompany3E → HSActive or inactive.
Relationship timekeepere3_relationship_partner, hubspot_owner_idCompany3E → HSOwner set when the attorney is a HubSpot user.
Payor and billing contactfirstname, lastname, emailContact3E → HSFrom the Payor object. Fill blanks only.
Matter
Matter numbere3_matter_numberMatter (custom object)3E → HSPrimary match key for matters. Unique.
Matter namee3_matter_nameMatter (custom object)3E → HSOnly if the risk team approves; otherwise a neutral label.
Practice area / departmente3_practice_areaMatter (custom object)3E → HSMapped to a HubSpot dropdown.
Officee3_officeMatter (custom object)3E → HSMatter office.
Matter statuse3_matter_statusMatter (custom object)3E → HSOpen, closed or pending.
Open date and close datee3_open_date, e3_close_dateMatter (custom object)3E → HSClose date can start a feedback survey.
Originating timekeepere3_originating_attorneyMatter (custom object)3E → HSConfirm role attributes in discovery.
Responsible timekeepere3_responsible_attorneyMatter (custom object)3E → HSLead attorney on the matter.
Timestampe3_last_changedMatter (custom object)3E → HSLast change in 3E. Also the change filter for reads.
Client on matterMatter ↔ Company associationMatter (custom object)3E → HSMatched on client number.
Timekeeper
Timekeeper numbere3_timekeeper_idContact3E → HSFor attorneys tracked as contacts, such as alumni.
Timekeeper name and emailHubSpot userUser3E → HSMatched to HubSpot users by email for ownership.
Department, section and officee3_practice_area, e3_officeContact3E → HSUsed for routing and event invitations.
Departed statuse3_alumniContact3E → HSOnly if the firm approves an alumni program.
Client-level billing summaries
Fees billed, trailing 12 monthse3_fees_billed_ttmCompany3E → HSCalculated in the integration layer. Restricted view.
Fees collected, trailing 12 monthse3_fees_collected_ttmCompany3E → HSRestricted view.
Realization ratee3_realization_rateCompany3E → HSCollected as a share of standard value. Formula agreed with finance.
Open receivable balancee3_ar_balanceCompany3E → HSSum of open bills. Restricted view.
Practice areas with matterse3_practice_areas_servedCompany3E → HSMulti-select. Drives cross-sell lists.
Intake requests
Prospective client and contactCompany, ContactCompanyHS → 3ESent from the won pitch.
Proposed matter detailsdealname, e3_practice_areaDealHS → 3ENeutral description only; the intake team completes the rest in 3E.
Intake statuse3_intake_statusDeal3E → HSSubmitted, approved or not opened. No conflicts detail.
New matter numbere3_matter_numberDeal3E → HSLinks the deal to the Matter record.
06 — Auth & API

How are authentication and API limits handled?

Values below come from Elite's developer portal. Items Elite leaves to the firm or to its knowledge base are marked for confirmation.

TopicElite 3EHubSpot
Access model3E 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.
Interfaces3E 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.
Authentication3E 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 detectionOData 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 limits3E 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.
EnvironmentsLive 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 dataNarratives, 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.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Privileged and confidential informationHigh

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.

Credentials are owned by the firmHigh

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.

Published call limitsMedium

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.

Conflicts stay in 3EMedium

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.

Attributes vary by firmMedium

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.

Financial data visibilityLow

Revenue and realization are sensitive inside a partnership. Restrict them with field-level permissions and agree who sees them before backfill.

Opportunities in HubSpot

Cross-sell by practice areaHigh value

Each client shows the practice areas already serving it, so business development builds lists of clients missing a practice the firm offers.

Pitch to matter without rekeyingHigh value

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.

Client value for partnersHigh value

Partners see fees billed, collected and realization on the client record, next to every pitch, event and touchpoint.

Events that lead to workMedium value

Seminar and CLE attendees are linked to client companies, so the firm sees which events precede new matters.

Feedback at the right momentMedium value

A matter closing in 3E can add the agreed client contact to a HubSpot feedback survey list.

Alumni as a relationship channelMedium value

Departed timekeepers, if the firm approves, become an alumni list for newsletters, events and referrals.

Pitch-to-matter flow

Business development works in HubSpot. Intake, matters and billing run in 3E.

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.

  1. Clients, matters and timekeepers sync from 3E, so every pitch starts from the real client relationship.
  2. A won pitch sends a pre-filled intake request into the firm's 3E intake and conflicts workflow.
  3. The intake team clears conflicts in 3E; HubSpot receives only the status and the new matter number.
  4. Client-level billing summaries flow back to HubSpot for partners and business development.
08 — Property schema

Which HubSpot properties does the integration create?

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 nameLabelObjectTypeSource / logic
e3_client_number3E Client NumberCompanySingle-line textClient number; unique
e3_industryIndustry (3E)CompanyDropdownFirm industry codes
e3_relationship_partnerRelationship PartnerCompanySingle-line textRelationship timekeeper on the client
e3_practice_areas_servedPractice Areas ServedCompanyMultiple checkboxesPractice areas with open or recent matters
e3_fees_billed_ttmFees Billed (12 months)CompanyNumber (currency)Sum of bills, trailing 12 months; restricted
e3_realization_rateRealization RateCompanyNumber (percent)Formula agreed with finance; restricted
e3_ar_balanceOpen Receivable BalanceCompanyNumber (currency)Sum of open bills; restricted
e3_matter_number3E Matter NumberMatter / DealSingle-line textMatter number; unique on Matter
e3_practice_areaPractice AreaMatter / DealDropdown3E department or practice area
e3_matter_statusMatter StatusMatterDropdownOpen, closed, pending
e3_originating_attorneyOriginating AttorneyMatterSingle-line textOriginating timekeeper on the matter
e3_intake_statusIntake StatusDealDropdownSubmitted, approved, not opened
09 — Scope builder

Interactive scope builder

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.

Scope summary

0Fields
0Inbound
0Write-back
10 — Sources

Sources & verification

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.

Elite 3E × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Elite 3E HubSpot integration FAQ

Does Elite 3E integrate with HubSpot?

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.

What data syncs between Elite 3E and HubSpot?

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.

Which system owns which data?

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.

What does setting up the Elite 3E HubSpot integration involve?

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.

How long does the integration take and what does it cost?

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.

Ready to Get More From HubSpot?

Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.