Matter handoff
Matter handoff is the transition at which a signed prospective client stops being an intake record and becomes an opened matter in the firm's case management system, passing from the intake function to a case manager and crossing the boundary between two pieces of software.
It is the last step of the six-step path this research maps from first contact to an opened matter, and it is the step with the thinnest evidence behind it. Every description of it held here was written by a software vendor. Two of the five describe that vendor's own two products talking to each other; the other three describe a crossing into another company's system, and two of those three are the receiving company describing what arrives.
What the captured evidence actually describes
Four vendors describe moving a completed intake into a matter, in five separate statements. Two of the statements describe a path inside one company's own stack. The other three describe the same cross-vendor crossing: one from the sending side, and two from receiving vendors saying what arrives at their end.
Clio states that once client intake is complete, documents, notes, events, intake form details and related contacts can be transferred into Clio Manage. Both ends of that transfer are Clio products.
Lead Docket states that as soon as a new case is signed, case files and other information are automatically pulled into Filevine as a new project, and that any custom field created in Lead Docket can be mapped to Filevine. The product registry behind this research records Lead Docket's company as Filevine, so this is again one vendor describing its own two products talking to each other.
The two described above are the same-vendor pair: in each, the intake product and the destination belong to one company. The remaining three statements are not. Lawmatics states that matter data syncs on lead conversion to nine named case-management products made by other companies, and two of those nine publish the receiving half on their own domains. Clio states that on conversion the matter syncs to Clio Manage together with custom fields, documents, notes and relationships, and MyCase states that when a lead converts to a client a new case is automatically created in MyCase. That is the configuration a firm lands in whenever it buys the best intake tool and the best case system separately, and it is documented, by both parties to it. What is still undocumented anywhere here is which fields survive the crossing.
What is captured instead: connection, not behaviour
The MyCase statement above is worth separating from what follows, because it names the same trigger and the same outcome the sending vendor names, published by the other party. It was on disk here from 2026-08-16 while an earlier version of this page said the only cross-vendor material was integration availability. Beyond those two receiving-side descriptions, the remaining cross-vendor material in this research is integration availability and nothing more. Gavel names Docusign, Zapier and Clio Manage among the systems its workflows connect to, which is a genuine statement about another company's product. Law Ruler states that it integrates with dozens of legal vendor tools so that firms are not entering data twice, which names the exact failure this step exists to prevent.
Both are statements that a connection is offered. Neither describes what survives the crossing: which field maps to which, what happens to a field with no counterpart on the other side, how duplicates are resolved, or how a firm finds out that a transfer failed. A listing proves a connection exists. It says nothing about what arrives.
One capture makes that distinction unusually clear. Perspective AI states that every completed conversation arrives as a structured summary routed to the customer's inbox, CRM or Slack. A summary delivered to an inbox or a chat channel is a delivery of information. It is not a matter opening, it names no case management destination, and it describes no field mapping.
The failure mode, and its one first-hand witness
The failure modes this research attaches to the step are that data does not arrive, arrives partially, or arrives duplicated, after which work restarts from the client, who has already answered those questions once. That is this project's model of the step, built from the systems it crosses. It is not a measured finding, and no source captured here measures how often the step actually fails.
The nearest first-hand account sits one boundary upstream. A firm that used two answering services reports that one delivered messages by email only, with no integrations, and still got them wrong sometimes. That is a handoff between an outside service and the firm rather than between an intake tool and a case system, and it is one pseudonymous account of one firm. It is recorded here because it exhibits the shape of the failure this step is named for: intake information that arrives, in a form that does not reach the record it was meant to reach.
How to test it at your own firm
Take a sample of recently opened matters and compare each field in the matter against the original intake record. Count the fields that had to be collected from the client a second time. That count is a number about your firm, which is the only kind available here, because no benchmark for it exists in this research or in any source it has captured.
The same test is the one to put to a vendor. Ask for a demonstration of a full intake moving into the case system you actually run, with your own fields, then compare the resulting matter against the intake record field by field. If your intake tool and your case system come from different companies, that demonstration is asking about something no source in this research has documented for you.
What this evidence does not establish
Every description of a handoff held here is published by the vendor selling it, and describes availability rather than reliability. No independent test of any handoff exists in this research. Nothing measures how often the step fails, what a failure costs, or what share of firms run intake and case management from different vendors. Field mapping availability is not mapping depth: no capture describes transformation handling, duplicate resolution, or what happens when a mapping fails. The cross-vendor path is described by both parties to it and by neither independently.
Related: the six-step path this term sits at the end of, and the products that describe it, are set out in the legal intake software comparison. The standards this page is held to are at methodology.