Key takeaways
- Map the journey from inquiry to open matter before connecting anything, and decide which system owns each field.
- Native connections exist between some intake tools and practice management systems; test which fields actually transfer[1][2][3].
- Forms must work on a phone: 16% of US adults are smartphone-dependent[4].
- Conflict-check names need the strictest rules, because a typo there weakens every future check.
Why re-entry is the real problem
Most small firms already have an intake form and a practice management system. The trouble is the gap between them. A prospect fills in a web form, a staff member reads the email notification, then types the same name, phone number, opposing party and matter description into the practice management system. Each retyped field is a chance for a misspelling, and the misspelled name is the one your conflict check will search for next year.
Connecting the two removes that step, but only if you decide first what should flow, where it should land and who checks it. A connection built without those decisions simply moves bad data faster. In firms where one or two people do everything, which describes most US law offices (71.8% had fewer than five employees in 2023[5]), getting this right saves time every single day.
Map the data flow before connecting anything
- Inquiry: a web form, chat, call note or referral email creates a prospect record.
- Conflict check: the names of the prospect, opposing parties and related people are searched against all contacts, including former prospects.
- Consultation: a booking is made and linked to the prospect record.
- Engagement: the engagement letter is generated from prospect data and signed.
- Matter: the prospect becomes a client, and a matter opens with the intake answers attached.
For each step, write down which system holds the record and which system is the source of truth for each field. A common pattern is that the intake tool owns everything until engagement, then the practice management system takes over. Write it down, because without a rule two systems will each think they own the client's phone number, and they will disagree.
Build a field map
| Form field | Destination | Owner | Validation rule |
|---|---|---|---|
| Full legal name | Contact: first, middle, last | Intake lead | Required; no nicknames; check spelling back with caller |
| Phone | Contact: mobile | Intake lead | Ten digits; confirm consent to text separately |
| Contact: email | Intake lead | Format check; confirm before sending documents | |
| Opposing party names | Matter: related contacts, role "adverse" | Intake lead | Required for conflict check; one name per field |
| Practice area | Matter: practice area | Intake lead | Pick list only, no free text |
| Incident or key date | Matter: custom date field | Responsible lawyer | Date picker; drives deadlines |
| How they heard of us | Contact or matter: source | Office manager | Pick list; kept after conversion |
| Description in their words | Matter: intake note | Responsible lawyer | Free text; not used in documents without review |
Two rules make the map work. Use pick lists wherever you can, because free text breaks reports and automations. And give every field one owner who decides what happens when data conflicts.
Ways to connect the systems
Connections come in four types, and many firms use more than one. Native integrations are built by one of the vendors: Clio describes approved intake information from Clio Grow carrying into the client and matter record[1], Lawmatics lists integrations with Clio, MyCase, Filevine, Smokeball and PracticePanther[2], and Lead Docket offers Filevine Sync[3]. Middleware automation services pass data between apps using triggers you configure. Direct API connections are built by a developer. Scheduled imports move a spreadsheet file on a timetable.
- Native integration: the easiest to maintain, but limited to the fields the vendor chose. Check custom fields in particular.
- Middleware automation: flexible and quick to set up, but every automation is something that can fail silently. Assign an owner to check it weekly.
- Direct API: the most control, but you need someone to maintain the code when either system changes.
- Scheduled import: crude but predictable. It can be enough for referrals that arrive in batches.
Build forms people finish on a phone
Most prospects will see your form on a phone. Pew data show 91% of US adults own a smartphone[6], and 16% are smartphone-dependent, with no home broadband[4]. A form that is easy on a laptop but painful on a small screen loses people at the third question. Keep the first screen to name, phone, email, practice area and a short description; ask for everything else after a staff member has made contact.
- Smartphone, no home broadband 16%
Source: Pew Research Center, 2026[4]
Show the data
| Item | Value |
|---|---|
| Smartphone, no home broadband | 16% |
Language matters too. More than one in five people aged five and older in the US spoke a language other than English at home in 2017 to 2021[7]. If you serve those communities, offer the form in the languages your staff can actually respond in, and record the preferred language as a field so it reaches the matter.
Connect in six steps
Inventory every entry point
List every place an inquiry can start: each web form, chat, phone line, directory listing and referral email address.
Agree the canonical fields
Finish the field map and get the responsible lawyer to sign off on the conflict-check fields.
Set duplicate rules
Decide how the system matches a returning person: email plus phone is a common rule. Decide who merges duplicates and when.
Choose triggers
Decide which event moves data: form submission, consultation booked, or engagement signed. Moving data only at engagement keeps practice management clean.
Test with fictional people
Run ten test inquiries covering odd cases: hyphenated names, two opposing parties, a returning client, a non-English submission.
Monitor after go-live
For the first month, compare every new matter with its original form submission. Fix mapping errors the same day.
Treat conflict-check data as special
Names for the conflict check are the most important data in intake, and the easiest to damage. A form that captures "John Smith (ex-husband)" in one free-text field will not match a later search for "Smith, John". Split names into separate fields, record each person's role, and keep declined prospects in the searchable contact list rather than deleting them. When a matter converts, check that adverse parties arrive as related contacts with the right role, not buried inside a note.
Failure modes to watch for
- Custom fields that do not transfer, so the incident date stays behind in the intake tool.
- Duplicate contacts created every time a returning client fills in a form.
- Automations that stop after a password change or an expired connection, with no alert.
- Marketing source overwritten at conversion.
- Notes copied into documents automatically, including details the client did not expect to appear.
- Sensitive details sent in plain email notifications to a shared inbox.
Example: a three-lawyer employment firm
Example (fictional): an employment firm receives about 25 web inquiries a week. Before connecting systems, the paralegal retyped each one and spent roughly four hours a week on it. The firm maps eleven fields, moves data only when the engagement is signed, and uses the intake tool's native integration for standard fields plus one middleware automation for the employer name, which it stores as an adverse party. In the first month, the monitoring check finds that employer names with "Inc." create duplicates; the firm adds a cleanup rule. Retyping drops to the occasional correction, and the paralegal's four hours go to calling prospects back faster.
Questions to ask about any connection
- Which standard and custom fields transfer, and in which direction?
- What triggers the transfer, and can we choose a different trigger?
- What happens when a record already exists: update, duplicate or skip?
- How are failed transfers reported, and to whom?
- Who maintains the connection when either product changes, and is that in the contract?
Ask both vendors, not just one. Each will tend to describe the connection from its own side, and the gaps usually appear in the middle.
Security and access
Intake forms collect sensitive facts from people who are not yet clients. Send notifications without the full form contents, so details do not sit in email inboxes, and restrict who can see prospect records. Review the access each connection has: a middleware account that can read and write every contact in your practice management system deserves the same protection as a staff login, including multi-factor sign-in and a named owner.
Keep it working
Connections break quietly when a vendor updates a field, a form is edited or a login expires. Schedule a monthly five-minute test: submit one fictional inquiry, follow it through to a test matter, and delete the test records afterwards. Keep the field map up to date whenever someone adds a question to a form. And when a staff member who built an automation leaves, transfer ownership before their account is closed.
Frequently asked questions
Do intake forms need to connect to practice management?
Not always, but if staff retype more than a handful of inquiries a week, a connection usually saves time and reduces errors in conflict-check names.
When should data move from intake to practice management?
Many firms move it at engagement, so practice management holds only clients and matters, while declined prospects stay searchable for conflicts.
What is the safest way to connect systems?
A native integration maintained by a vendor is usually easiest. Test custom fields, and monitor any middleware automation weekly.
How do I avoid duplicate contacts?
Set a matching rule, such as email plus phone, name one person to merge duplicates, and check new matters against intake for the first month.
References
Clio (2026). Clio Grow: client intake and CRM software (opens in a new tab) โ
Lawmatics (2026). Lawmatics: legal CRM and client intake (opens in a new tab) โ
Filevine (Lead Docket) (2026). Lead Docket: legal intake platform (opens in a new tab) โ
Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) โ
U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ
Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) โ
U.S. Census Bureau (2025). New Data on Detailed Languages Spoken at Home and the Ability to Speak English (opens in a new tab) โ