The parallel-run posture
Many resolution shops run their pipeline and case management on IRS Logics, and it does that job well — your team knows it, your intake IDs live there, and your operational habits are built around it. RESO does not ask you to rip that out. The integration is built for a parallel run: IRS Logics keeps the CRM lane, and RESO runs the engagement — IRS evidence, financial intake, governed work product, portal, billing, and retention — on a case record linked back to the Logics matter.
What connects
- Import — bring a matter from IRS Logics into a RESO case through the firm API integration, so delivery work starts without rekeying the client.
- CRM snapshot sync — the RESO case carries a snapshot of the linked CRM record, giving operators the Logics context without switching windows.
- External case ID linking — the same client stays identifiable in both systems; the RESO case knows its Logics counterpart and vice versa.
- Case Bridge — a Chrome extension that recognizes Logics pages and lets you open or create the matching RESO matter in one click.
Division of labor
The clean way to think about it: IRS Logics answers “where is this lead or matter in our pipeline,” and RESO answers “what does the IRS evidence say, what is the plan, what did we deliver, and can we defend the fee.” Transcript intelligence, the Discovery and Strategy Reports, the client portal, e-sign, Stripe invoicing on the case, and Work Verification all live on the RESO record. Nothing in the integration tries to duplicate what Logics already does for your front office.
A typical workflow
- A matter reaches the delivery stage in IRS Logics.
- From the Logics page, Case Bridge opens (or creates) the linked RESO case.
- Intake, transcripts, Discovery, and Strategy run on the RESO case — the deliverables your firm bills for.
- Operators who live in Logics keep working there; the external case ID keeps both records pointing at the same client.
Adopting gradually
Firms that succeed with this integration standardize forward, not backward. New engagements start on RESO from week one. Active matters move when they next touch — a fresh transcript pull, a strategy revision, a fee question. Closed files stay in Logics unless a dispute or retention defense makes rebuilding the record worthwhile. There is no big-bang migration project; the parallel run is the steady state for as long as it serves you.
Setting it up
The Logics connection is configured per firm — you will need your IRS Logics API access, and enterprise rollouts can get hands-on help through support. Once connected, import and linking are available from the case workspace, and the Case Bridge extension installs in Chrome for anyone on the team who works across both systems. If you are planning a rollout for a multi-seat firm, the migration page outlines the 30/60/90-day pattern most teams follow.