Migrate from MyCase to GavelGrow
MyCase is case management software with intake bolted on. For firms running serious paid acquisition, the intake side of MyCase is not the strongest part of the product — and the marketing reporting is light. The right architecture for most firms is GavelGrow for the marketing funnel (click → lead → consultation → signed case) and MyCase staying as the case management tool for everything after sign-up. This page explains how that handoff works.
Why firms switch the marketing side
- Marketing reporting depth. MyCase reports on cases. GavelGrow reports on the marketing funnel that produces those cases — campaign-level CPL, signed-case attribution, Google Ads ROI, intake speed-to-lead, and 500-firm peer benchmarks.
- Native call tracking. MyCase does not include call tracking. Most firms run CallRail alongside, which means another subscription and another integration. GavelGrow includes native call tracking via Twilio.
- Intake automation depth. MyCase intake forms are basic. GavelGrow ships with practice-specific templates and automated SMS + email sequences with sub-60-second response.
- Same data, less duplication. Lead lives in GavelGrow until signed. Once signed, the case profile pushes to MyCase. No duplicate data entry, no two pipelines to keep in sync.
What stays in MyCase
- Case management lifecycle (open matter, deadlines, time tracking, billing)
- Document storage for case files
- Trust accounting / IOLTA
- Court calendaring + filings
- Client portal for active cases
- All historical case data — no migration of closed/active cases needed
What moves to GavelGrow
- Lead intake forms (re-built in GavelGrow with practice-area templates)
- Lead pipeline (pre-signed-case)
- Tracking numbers + call recording (CallRail replaced by GavelGrow native call tracking)
- Marketing automations (SMS + email sequences for intake, follow-up, consultation reminders, no-show recovery)
- Marketing reporting (CPL, ROI, signed-case attribution, benchmarks)
The handoff: lead → MyCase case
When a lead signs the engagement letter in GavelGrow, the case profile pushes to MyCase as a new matter — either via CSV export (today) or via direct API integration (Q3 2026 roadmap). The marketing attribution stays in GavelGrow so you can always trace a closed case back to the originating Google Ads keyword. The case lifecycle (deadlines, billing, documents) lives entirely in MyCase.
Migration timeline
- Day 1-3 — Lead history export. Export pre-signed-case leads from MyCase as CSV. Import to GavelGrow with field mapping. Active cases stay in MyCase untouched.
- Day 4-7 — Intake setup. Re-build intake forms in GavelGrow using practice-area templates. Test embed on existing website URLs.
- Day 8-10 — Call tracking + automation. Provision GavelGrow tracking numbers (or port existing CallRail numbers via Twilio). Configure intake SMS + email sequences from templates.
- Day 11-14 — Cutover. Point Google Ads + intake forms at GavelGrow. New leads flow into GavelGrow → sign engagement → push to MyCase as case. Existing active cases continue uninterrupted in MyCase.
Common questions
Will my active MyCase cases be affected?
No. Migration is marketing-funnel only. Every active case in MyCase stays exactly where it is, with no data export and no disruption to your case management workflow.
How do leads get into MyCase as cases after migration?
Today: CSV export from GavelGrow when a lead signs, import to MyCase using their standard contact import. Direct API integration to MyCase is on the 2027 roadmap.
Can I run both intake systems in parallel?
Yes. During the 1-2 week parallel period, leads can come into either system while you verify GavelGrow data quality. Most firms do a 5-7 day overlap before cutting MyCase intake fully off.
What about MyCase’s built-in client portal?
Stays in MyCase, used for active cases. GavelGrow has its own lightweight client communication via SMS / email / unified inbox during the lead phase. Once signed, communication moves to the MyCase portal.
See pricing · Request a MyCase migration plan · Book a 15-minute migration walkthrough · Other migrations