circa logic
Integrations

Connect the systems you already trust.

We build two-way connections between the legal applications your firm runs, so matter data stays consistent and staff stop re-keying it. Below are the platforms we work with most and sample flows from patterns we've already delivered.

Every firm's stack is different, and every vendor's API is different. We map what each system can read, write and announce through webhooks, then design the flow around your process. If your system isn't listed, ask: if it has an API, a database or a reliable export, we can usually work with it.

Practice & firm management

The system of record for clients, matters, time and billing. We treat it as the hub and make everything else agree with it.

Clio

Matters, contacts, custom fields, calendar entries, tasks, notes, time entries and documents through the Clio API, with webhooks so changes push instead of being polled.

ProfitSolv (Orion, TimeSolv, Tabs3, CosmoLex, Rocket Matter)

Each ProfitSolv product exposes something different. We map what each one can read and write, then fill the gaps, such as Orion having no calendar, with docketing and Microsoft 365.

Centerbase

Matter, contact and workflow data synced to your DMS, docketing and CRM so the matter list is the same everywhere.

Filevine

Projects, contacts, notes, tasks and your custom sections mapped field by field, with signed webhooks so case changes reach intake, documents and docketing.

MyCase, PracticePanther, Smokeball, Actionstep

Matter creation, status and responsible-attorney changes kept in step with the rest of your stack.

Docketing & court rules

Deadlines are the highest-risk data in a firm. They should be calculated once by a rules engine and then appear everywhere people actually look.

LawToolBox

Rules-based deadlines in Microsoft 365. We tie its matters to your PMS matter numbers, share them with the right team automatically, and carry deadlines back to the PMS calendar.

CompuLaw, CalendarRules and other rules-based calendaring

Wherever an API or export exists, we keep matter identity and assigned staff aligned with your practice management system.

Court data (PACER, CourtListener, Docket Alarm)

New docket entries matched to the right matter and routed to the responsible team for review.

Document management

Documents belong in the matter workspace, profiled correctly, without anyone dragging and dropping.

iManage Work

Workspaces created from your templates when a matter opens, with documents filed and profiled (client, matter, doc type, author) by rule.

NetDocuments

Workspace creation, profile attributes and filing into the correct folder, mapped to your cabinet structure.

SharePoint & OneDrive

Matter sites or libraries provisioned from a template, with metadata columns so documents can be found and governed.

CRM, intake & marketing

Business development data is only useful if it knows what happened after the client signed.

Salesforce (including Litify)

Leads, opportunities and accounts connected to matters, with billing and status rolled back up for relationship partners.

HubSpot

Contact and company records deduplicated against your PMS, and lifecycle stage driven by real matter events.

Lawmatics & Clio Grow

Intake that converts into a fully opened matter in every downstream system, not just the PMS.

Calls, email & calendars

Most matter knowledge starts as a conversation. We capture it, file it, and turn it into tasks people actually see.

Microsoft Teams & Teams Phone

Call records, recordings and transcripts through Microsoft Graph, processed inside your own tenant.

RingCentral, Zoom Phone & others

Call logs and recordings matched to clients and matters by phone number and contact rules.

Outlook & Exchange

Matter email filed by rule, and follow-ups placed on the right person's calendar with reminders.

Microsoft 365 platform

Your tenant is where the automation runs, so your data stays in your environment under your security policies.

Entra ID

Single sign-on, least-privilege service identities, and access you can revoke in one step.

Groups, Planner & To Do

Matter teams and assigned follow-ups that show up where staff already work.

Power BI & custom dashboards

A partner view of every matter with a timeline of dates, deadlines, activity and financials.

Sample flows

What bi-directional actually looks like

These are starting points based on work we've already delivered: CRM data, matter migrations, system-to-system sync and call capture. Your version is designed with your team during the analysis, field by field and rule by rule.

Client call → transcript in the DMS → summary, follow-ups and calendar

  • Teams Phone / RingCentral
  • iManage · NetDocuments · SharePoint
  • Clio · ProfitSolv · Centerbase
  • Outlook · LawToolBox
The problem todayAfter a client call, someone has to type up notes, find the matter, file them and remember to calendar what was promised. Usually some of that doesn't happen.
  1. Call endsThe recording or transcript is picked up from your phone system inside your Microsoft tenant.
  2. Matched to a matterCaller number, contact and matter number rules find the client and matter. If more than one matter could match, the call goes to a short review queue. The system never guesses.
  3. Transcript filedThe full transcript is saved to the matter workspace in iManage, NetDocuments or SharePoint, profiled as a call record with date, participants and duration.
  4. Summary postedA structured summary goes onto the matter as a note: topics discussed, decisions made, and each follow-up with an owner and due date.
  5. Follow-ups calendaredEach follow-up becomes a calendar event or task for the responsible person, with reminders before it is due. Court-related items can go to docketing for review.
The call is documented, filed and on the calendar before the attorney has hung up the headset.

How this workflow works in detail →

Two-way matter sync: practice management ↔ docketing

  • Clio · ProfitSolv · Centerbase
  • LawToolBox · CompuLaw · CalendarRules
The problem todayMatters get opened twice, team changes in one system never reach the other, and closed matters keep generating deadline reminders.
  1. Field ownership agreedEach field gets one owner. For example, the PMS owns client, matter name and responsible attorney, and docketing owns court, case number and deadlines.
  2. Matter opens onceA new PMS matter creates the docketing matter with the same identifiers and shares it with the assigned team.
  3. Changes flow both waysStaffing, status and case details update in the other system within minutes, and every change is logged with before and after values.
  4. Deadlines come backCalculated deadlines appear on the PMS calendar and matter record, so billing and case staff see the same dates.
  5. Closing is cleanClosing a matter in the PMS closes it in docketing and stops future reminders, after checking for open deadlines first.
One matter, identical in every system, without anyone keying it twice.

How this workflow works in detail →

Signed client → matter open everywhere at once

  • Salesforce · HubSpot · Lawmatics
  • Clio · ProfitSolv · Centerbase
  • iManage · NetDocuments · SharePoint
  • Microsoft 365
The problem todayA new engagement means the same client and matter details typed into five systems by three people over several days.
  1. Engagement signedThe CRM or intake record moves to "retained".
  2. Client and matter createdCreated in the PMS with your numbering scheme, billing attorney and rate defaults applied.
  3. Workspace provisionedA DMS workspace or SharePoint library is built from the right practice-area template.
  4. Team assembledA Microsoft 365 group or Team, docketing matter and calendar sharing are set up for the assigned staff.
  5. Kickoff tasks assignedKickoff tasks are assigned with due dates, and the CRM record is linked back to the new matter.
Matter opening goes from days of handoffs to minutes, and every system starts with the same data.

How this workflow works in detail →

Matter migrations that don't break everything around them

  • Legacy PMS / DMS
  • New PMS / DMS
  • Everything integrated with them
The problem todayVendor migration tools move the data but drop custom fields, history and the links other systems relied on.
  1. Mapping workbookEvery field, picklist and custom value is mapped, including the ones the vendor's tool ignores.
  2. Repeatable dry runsScripted loads into a test environment produce reconciliation reports (counts, totals, samples) that your staff sign off on.
  3. ID crosswalkOld and new IDs are stored together, so integrations, reports and document links keep working.
  4. Delta cutoverA final catch-up load covers anything that changed since the last full run, so downtime is short.
A migration you can verify, with your integrations still working on day one.

How this workflow works in detail →

CRM that knows what happened after the client signed

  • Salesforce · HubSpot
  • Clio · ProfitSolv · Centerbase
The problem todayRelationship partners can't see matters, billings or key dates without asking accounting.
  1. Contacts deduplicatedContacts and companies are matched by rule (email, domain, client number) with a merge review queue.
  2. Matter rollupsOpen matters, stage, fees billed and collected, and next key date are written to the account.
  3. Signals, not noiseAlerts go out when a key client has no activity in X days, or a matter crosses a budget threshold.
Business development decisions based on what is actually happening in each matter.

How this workflow works in detail →

Email and documents filed by rule

  • Outlook
  • iManage · NetDocuments · SharePoint
The problem todayMatter email lives in personal inboxes and attachments never reach the workspace.
  1. Rules matchMatter numbers in the subject, known client domains or a tag applied in Outlook identify the matter.
  2. Filed and profiledMessages and attachments are saved to the workspace with document type and author set.
  3. Unsure? AskAnything ambiguous is sent to the user for one-click confirmation, never silently guessed.
Complete matter files without anyone dragging and dropping.

How this workflow works in detail →

Built to last

Every integration ships with the same safeguards

  • Field-level ownership. Each value has one source of truth, so two systems never overwrite each other.
  • Review queue. Ambiguous matches go to a person instead of a guess.
  • Audit log. Every change is recorded with before and after values and the rule that made it.
  • Monitoring. Failures and vendor API changes raise alerts before staff notice.
  • One connector per vendor. Swapping a system later touches one component, not everything.
Two technologists with tablets in a server room

Running a combination that isn't shown here?

Tell us what you use and where your staff spend time re-keying. We'll tell you honestly what's possible.

Ask about your stack