Migrate your Lawcus data
Legal practice management CRM for small to mid-size law firms with built-in automation, workflow stages, and per-user pricing. Lawcus competes on cost against Lawmatics and MyCase but carries a modest review volume on public platforms.
In its favor
Why people choose Lawcus
The signal that keeps Lawcus on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Lawcus offers per-user pricing starting around $34–$49/month, which is significantly lower than Clio or CosmoLex for small solo and boutique firms trying to control software spend.
The platform consolidates client notes, emails, tasks, and billing fees per Matter in one place, eliminating the need to switch between multiple tools during case work.
Built-in workflow automation with configurable stages lets law firms automate intake pipelines, deadline reminders, and task routing without third-party tools like Zapier.
Continuous product updates and responsive customer support are highlighted by reviewers as a reason they stay, particularly for a product at this price tier.
Migration guides for importing from Amicus, MyCase, PracticePanther, and Lawmatics are published directly in Lawcus Help Center, signaling that the vendor actively supports platform switching.
Some users report that product updates introduce interface changes and UI inconsistencies that do not improve workflow, creating unnecessary friction for established users.
Lawcus has a low public review volume on G2 and Capterra, making it difficult for prospective buyers to assess long-term reliability before committing, which also means fewer peer references during migration planning.
A reviewer noted the platform felt clunky during active use, particularly when navigating between multiple Matters, suggesting the UX has not caught up with the feature set.
No phone support and slow email response times are cited as pain points, which is critical when a law firm needs urgent data access during a migration emergency.
Reasons to switch
Why people leave Lawcus
The recurring reasons buyers give for replacing Lawcus. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Lawcus fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Lawcus pricing overview
Lawcus uses a per-user, per-month subscription model with four named tiers. The entry tier (Standard or Essential) is the most affordable legal practice management option at its price point, while Enterprise requires a direct sales conversation. Pricing discrepancies across published sources suggest promotional or billing-cycle variants exist.
Standard / Essential
Tier 1 of 4
$34–$49 per user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Lawcus's schedule — see our quote-based pricing →
What gets migrated
Lawcus object support
Object-by-object support for Lawcus migrations. Per-pair details surface during scoping.
Matters
Fully supportedMatters are the primary case container in Lawcus. We export all open and closed Matters via the Settings > Export & Import > Matters tab, including stage, practice area, assigned user, and dates. The export is delivered as a structured CSV we normalize to the destination schema.
Contacts (Clients)
Fully supportedContacts are exported as a separate Clients CSV from the Export & Import section. We map the contact's name, email, phone, address, and any associated Matter IDs to preserve the client-to-matter relationship in the destination platform.
Leads
Mapping requiredLawcus maintains a separate Leads object distinct from Contacts. Leads can be exported from the Leads section via the background-task Export feature. We map Lead source, status, and contact details to the destination's lead or contact object, noting that not all CRMs expose a separate lead concept.
Workflows
Mapping requiredWorkflows define multi-stage pipelines tied to Matters and Leads. Lawcus exposes workflow definitions via the API endpoint GET /workflows/with-stages. We capture stage names, order, and transition logic as structured data but re-create the workflow logic in the destination platform since automation rules do not export as executable configuration.
Tasks
Fully supportedTasks are associated with Matters and Contacts. The Full Backup ZIP includes task records with assignee, due date, status, and linked Matter ID. We map these into the destination's task or to-do structure preserving the Matter association.
Activities / Interactions
Fully supportedActivities represent time entries, logged calls, and meeting notes. We export Activities from the API endpoint and include them in the Matter-level timeline reconstruction at the destination.
Custom Fields
Mapping requiredLawcus supports Custom Fields on Matters and Contacts, exposed via GET /customfields in the API. We export CustomField definitions and values but map each custom field as a property on the target object rather than as a native custom-field definition, since destination platforms vary in how they handle custom field creation.
Practice Areas
Fully supportedPractice Areas are a classification taxonomy used to categorize Matters (e.g., Family Law, Criminal Defense). We map Practice Area as a property on the Matter record in the destination platform.
Users / Team Members
Mapping requiredLawcus exposes Users via GET /users/load and supports both default roles (Admin, Member) and custom roles. We map Users and their assigned role, but the role permission model is destination-dependent and may need to be re-established manually post-migration.
Invoices
Mapping requiredInvoices are accessible only by Admin role in Lawcus. We export invoice records (linked to Matters) from the Full Backup. Note that many law firms use separate billing software (e.g., LawPay) integrated with Lawcus, so invoice data should be verified against the integrated billing platform before migration.
| Object | Support | Notes |
|---|---|---|
| Matters | Fully supported | Matters are the primary case container in Lawcus. We export all open and closed Matters via the Settings > Export & Import > Matters tab, including stage, practice area, assigned user, and dates. The export is delivered as a structured CSV we normalize to the destination schema. |
| Contacts (Clients) | Fully supported | Contacts are exported as a separate Clients CSV from the Export & Import section. We map the contact's name, email, phone, address, and any associated Matter IDs to preserve the client-to-matter relationship in the destination platform. |
| Leads | Mapping required | Lawcus maintains a separate Leads object distinct from Contacts. Leads can be exported from the Leads section via the background-task Export feature. We map Lead source, status, and contact details to the destination's lead or contact object, noting that not all CRMs expose a separate lead concept. |
| Workflows | Mapping required | Workflows define multi-stage pipelines tied to Matters and Leads. Lawcus exposes workflow definitions via the API endpoint GET /workflows/with-stages. We capture stage names, order, and transition logic as structured data but re-create the workflow logic in the destination platform since automation rules do not export as executable configuration. |
| Tasks | Fully supported | Tasks are associated with Matters and Contacts. The Full Backup ZIP includes task records with assignee, due date, status, and linked Matter ID. We map these into the destination's task or to-do structure preserving the Matter association. |
| Activities / Interactions | Fully supported | Activities represent time entries, logged calls, and meeting notes. We export Activities from the API endpoint and include them in the Matter-level timeline reconstruction at the destination. |
| Custom Fields | Mapping required | Lawcus supports Custom Fields on Matters and Contacts, exposed via GET /customfields in the API. We export CustomField definitions and values but map each custom field as a property on the target object rather than as a native custom-field definition, since destination platforms vary in how they handle custom field creation. |
| Practice Areas | Fully supported | Practice Areas are a classification taxonomy used to categorize Matters (e.g., Family Law, Criminal Defense). We map Practice Area as a property on the Matter record in the destination platform. |
| Users / Team Members | Mapping required | Lawcus exposes Users via GET /users/load and supports both default roles (Admin, Member) and custom roles. We map Users and their assigned role, but the role permission model is destination-dependent and may need to be re-established manually post-migration. |
| Invoices | Mapping required | Invoices are accessible only by Admin role in Lawcus. We export invoice records (linked to Matters) from the Full Backup. Note that many law firms use separate billing software (e.g., LawPay) integrated with Lawcus, so invoice data should be verified against the integrated billing platform before migration. |
Gotchas
What to watch for in Lawcus migrations
Issues we've hit on past Lawcus migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Full Backup ZIP requires manual email delivery
Invoice and financial data gated to Admin role
Workflows do not export as executable automation rules
Multiple pricing sources show tier inconsistencies
| Severity | Issue |
|---|---|
| Medium | Full Backup ZIP requires manual email delivery |
| High | Invoice and financial data gated to Admin role |
| Medium | Workflows do not export as executable automation rules |
| Low | Multiple pricing sources show tier inconsistencies |
Leaving Lawcus?
Where Lawcus customers move next
12 destinations Lawcus can migrate to.
How a Lawcus migration works
Four steps, Lawcus-specific
Connect
Bearer token (API key) into Lawcus. Scopes limited to read-only on the data we move.
Map
We translate Lawcus-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Lawcus quirks before production.
Migrate
Full migration with Lawcus rate-limit handling. Rollback available throughout.
FAQ
Lawcus migration FAQ
Answers to the questions buyers ask most during Lawcus migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Lawcus migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Lawcus.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Lawcus setup and destination — written quote back within a business day.