CRM

Migrate your Case Status data

Client engagement and communication portal for law firms. Bridges the gap between case management systems and clients via a branded portal, automated updates, and AI-powered message triage. Firms buy it to stop the phone-tag treadmill.

Encrypted end-to-end with one-click rollback
Talk to a real migration engineer in minutes
Case Status logo

In its favor

Why people choose Case Status

The signal that keeps Case Status on the shortlist. Sourced from G2, Capterra, and customer scoping calls.

Clients receive automated case status updates without staff manually drafting emails, dramatically reducing inbound client check-in calls for firms running lean staffing.

The branded client portal and mobile app give small and mid-size firms a polished client experience comparable to large firm portals without custom development costs.

AI-powered message triage filters surface urgent or emotionally charged client communications in real time, helping attorneys prioritize responses before problems escalate.

The platform integrates with popular case management systems like Clio, PracticePanther, and MyCase, allowing firms to add client-facing functionality without abandoning existing workflows.

G2 ratings for ease of use and ease of admin indicate that non-technical paralegals and office managers can configure automations and portal settings without developer involvement.

Firms report that Case Status is a portal layer rather than a full case management system, so they end up paying for both Case Status AND a separate practice management tool, creating double-licensing costs.

Some customers cite frustration that automation options feel limited compared to what they can build in their primary CRM, requiring workarounds or third-party integrations for complex client communication sequences.

Pricing is not transparently published on the website, and firms report surprise costs when adding the API access tier, premium support, or migration assistance as separate line items.

Reasons to switch

Why people leave Case Status

The recurring reasons buyers give for replacing Case Status. Presented as facts, not knocks.

Platform scorecard

Strengths, weaknesses, and where Case Status 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

Highly-rated mobile app and client portal that requires no custom development to deployBuilt-in AI for message triage and client intelligence that surfaces urgent communications proactivelySeamless integration ecosystem with Clio, PracticePanther, MyCase, and other leading legal case management platformsClient satisfaction tracking via NPS with automated review request workflows that drive referral growthG2-recognized ease of use for admins and AI assistant categories, indicating low learning curve for firm staff

Weaknesses

Platform is a client-facing layer rather than a full practice management system, requiring firms to maintain a separate case management licenseNo publicly documented API — full API access requires a paid tier, limiting programmatic data extraction optionsAutomation builder lacks the depth of enterprise CRM workflow engines, limiting complex client communication sequencesPricing lacks public transparency, with many features billed as add-ons rather than included in published tiersSmall company footprint (~$4.5M revenue, ~77 employees) raises long-term viability and support capacity questions for large firm deployments

Where it works

Mid-size law firms with 5–50 attorneys running Clio, PracticePanther, or MyCase as their primary case management system, seeking a client-facing portal layer without replacing existing infrastructure.Solo and small firm practices (1–5 attorneys) without developer resources, needing a branded client portal and mobile app that non-technical office managers can configure independently.Lean-staffed firms where reducing inbound client check-in calls directly impacts operational capacity and attorney billable time, especially in personal injury and family law practices.Growing firms in the $2,000–$5,000/month tier seeking scalable client communication automation, NPS tracking, and automated review-request workflows as part of a structured growth strategy.Non-technical administrative staff and paralegals responsible for portal configuration, automations, and client communication setup without involvement from IT or external developers.

Where it struggles

Large firms and AmLaw 200 organizations requiring unified practice management, full API access, and long-term vendor stability from a company with ~77 employees and $4.5M revenue.Firms with complex communication needs requiring sophisticated multi-step sequences, conditional branching logic, and CRM-grade automation depth beyond the platform's builder capabilities.Organizations evaluating platform exit or data portability, given that full API access requires a paid add-on tier and document migration involves JSON-level field mapping complexity.Firms operating with strict budget governance requiring transparent published pricing without surprise line items for API access, premium support, or migration assistance.Multi-office or multi-jurisdiction practices requiring unified client views across disconnected case management instances, where Case Status serves only the portal layer without consolidating underlying data.

Pricing tiers

Case Status pricing overview

Case Status uses a per-user tiered pricing model starting around $50/user/month for base access, with growth and enterprise tiers for larger firms. Key features like API access, migration assistance, and premium support are add-ons rather than included, which can result in a significantly higher total cost than the headline per-user rate suggests.

Base Platform

Tier 1 of 4

Starts around $50/user/month

What's included

Client portal and mobile app accessAutomated case status updatesBasic integrations with case management systemsClient feedback tracking and NPS

Need help selecting your CRM?

Book a free 30 minute consultation

Pricing is informational. FlitStack AI does not bill on Case Status's schedule — see our quote-based pricing →

What gets migrated

Case Status object support

Object-by-object support for Case Status migrations. Per-pair details surface during scoping.

Clients

Fully supported

Clients are the primary contact records in Case Status. Each client record links to one or more matters and carries basic contact details, email, and phone. We migrate client records 1:1 with field preservation including any custom properties added at the client level.

Matters

Fully supported

Matters are the case-level records that form the backbone of the platform. Each matter links a client to a case type, status, and assigned attorney. We preserve matter associations, case numbers, and status history during migration, mapping them directly to the destination's equivalent case or matter object.

Documents

Mapping required

Case Status stores document metadata and client-accessible file links rather than the files themselves in many configurations. We migrate document references and association metadata; actual file assets require a separate file transfer step coordinated with the firm's document management system.

Client Portal Accounts

Fully supported

Client portal accounts are separate from the client contact records and include login state, notification preferences, and access permissions. We migrate portal account status and preferences, ensuring clients retain portal access credentials after cutover where the destination supports an equivalent portal.

Messages and Communications

Mapping required

Message threads between attorney and client are stored with timestamps, sender/recipient references, and content. Thread history transfers cleanly, but attachment references must be validated against the document migration step. AI triage flags on messages are not consistently exposed via the API and may require manual note creation.

Automation Rules

Mapping required

Firms build automation sequences for client updates, reminders, and status change notifications. These are structured as workflow rules in Case Status. We map the existence of automations to the destination CRM but do not auto-recreate the automation logic, as the triggering conditions and action types vary significantly between platforms.

Custom Properties

Mapping required

Both client records and matter records support custom properties defined by the firm. These store as key-value pairs that we capture and write to destination custom fields. We flag any custom properties that reference Case Status-specific picklist values requiring remapping.

NPS and Feedback Records

Mapping required

Case Status tracks Net Promoter Score and client feedback via the Client Feedback Tracker. These records include score, date, and optional comment text. We migrate the feedback scores and comments as a custom object or custom fields at the destination, depending on what the target CRM supports.

Billing and Time Records

Not in this platform

Case Status does not function as a billing or time tracking system. Firms that need billing data migrated must source that from their primary practice management platform (Clio, PracticePanther, MyCase). We do not migrate billing objects from Case Status because they do not exist there.

Tags and Labels

Mapping required

Matters and clients can be tagged for categorization. Tags map as flat label fields at the destination. We flag any tags that serve a functional role (e.g., triggering automations) because the tag-to-action linkage will not transfer automatically.

Gotchas

What to watch for in Case Status migrations

Issues we've hit on past Case Status migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.

High

No publicly documented public API for self-service exports

High

Portal data is partially decoupled from source case management

Medium

Add-on pricing model obscures true cost for migration assistance

Medium

Custom properties are stored as JSON key-value pairs with limited schema visibility

Low

Client app notifications and push token state does not transfer

How a Case Status migration works

Four steps, Case Status-specific

Connect

API key (per-firm token provisioned through sales or onboarding) into Case Status. Scopes limited to read-only on the data we move.

Map

We translate Case Status-specific structures (custom fields, objects, value lists) to the destination's model.

Sample

Test with a 50–200 record subset to validate Case Status quirks before production.

Migrate

Full migration with Case Status rate-limit handling. Rollback available throughout.

FAQ

Case Status migration FAQ

Answers to the questions buyers ask most during Case Status migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Case Status migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Case Status migrations under 1M records finish in 48–72 hours end-to-end. Larger orgs with custom objects or buyer-side security review typically take 5–7 days.

Ready when you are

Migrate Case Status.
Without the rebuild.

Free scoping call with a migration engineer. Tell us about your Case Status setup and destination — written quote back within a business day.

Free scoping call Quote in 1 business day 1,784 platforms supported