Migrate your Legl data
Client onboarding and matter management CRM built for law firms, unifying client intake, AML compliance, payments, and risk assessment into one workflow layer above practice management systems.
In its favor
Why people choose Legl
The signal that keeps Legl on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
UK-specific compliance focus — KYC, AML, identity and biometric confirmation, financial and watchlist screening, and ongoing monitoring are built into a single platform that maps to SRA expectations.
Legl Pay accelerates client payment times and replaces multiple ad-hoc payment-link tools with a single digital-first payment flow tied to client and matter records.
Modular platform with no-code workflows lets firms digitise both client-facing and internal compliance processes without engineering time.
Customer base of 170+ mid-market UK law firms gives the product proven scale in the specific regulatory environment it targets.
Free trial without credit card lowers evaluation friction for firms comparing against Lawyer Checker, SmartSearch, or in-house manual compliance workflows.
UK-centric — international firms outside the SRA/AML UK framework don't get the same out-of-the-box compliance fit.
Pricing is published as 'from $50/user/month' (small firms) scaling to $20–30/user/month at enterprise scale per third-party listings, but exact rates require a sales conversation, so smaller firms cannot self-serve.
Compliance-tool focus means firms eventually needing full practice management (time, billing, matter management) still need a separate system — Legl is not a full PM replacement.
Integration footprint to general legal practice management systems (Clio, Actionstep, Leap) is partner-led rather than published as packaged connectors, requiring API work in some cases.
Mid-market positioning leaves both very small (1–5 fee earner) and very large (1,000+ fee earner) firms underserved relative to dedicated alternatives.
Reasons to switch
Why people leave Legl
The recurring reasons buyers give for replacing Legl. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Legl 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
Legl pricing overview
Legl publishes a tiered per-user model that scales by firm size. Small businesses see pricing 'starting at $50 per user per month,' mid-sized firms (~100 users) average around $30 per user per month, and large enterprises (1,000+ users) drop as low as $20 per user per month per third-party listings. Global enterprise pricing is custom-quoted. A free trial without credit card details is available. Legl Pay payment fees are separate from subscription cost.
Small firm
Tier 1 of 3
From $50/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Legl's schedule — see our quote-based pricing →
What gets migrated
Legl object support
Object-by-object support for Legl migrations. Per-pair details surface during scoping.
Businesses
Fully supportedBusinesses represent law firm clients and map directly as the primary entity. The API supports list, create, retrieve, and sanctions/company report generation. We perform a 1:1 map of Business records including address, status, and linked contacts.
EngageRequests
Fully supportedEngageRequests track client engagement and onboarding workflows. Each request has a status lifecycle (pending, in-progress, completed) and is linked to a Business. We pull all EngageRequest records and preserve their status and reviewer assignment at migration time.
RiskAssessments
Mapping requiredRiskAssessments are beta-API objects that unify client, matter, and financial data. The schema includes templates and individual assessment records. We map assessment status, scoring data, and PDF output references, but PDF binary content requires separate file export handling.
Payments
Fully supportedPayments are linked to Businesses and tracked via checkout_url fields. The API supports list, create, retrieve, and partial update. We preserve payment status, amount, and Stripe checkout references during migration.
BankAccounts
Fully supportedBankAccounts are listed and retrieved per Business. The API exposes account identifiers and statuses. We map account references and current balances as of migration date.
Workflows
Mapping requiredWorkflows are referenced by ID and linked to EngageRequests. The Legl platform stores workflow definitions and reviewer assignments. We preserve workflow IDs and step completion status but note that the full workflow definition schema may require export via the browsable API UI.
BusinessReports
Mapping requiredBusinessReports are generated on-demand and include sanctions checks and company reports. We map report metadata and status but note that report generation is asynchronous — the PDF or content must be polled or retrieved separately.
Reviewers
Fully supportedReviewers are users assigned to approve EngageRequests and manual CDD steps. We map reviewer IDs and names as a reference table linked to Workflow and EngageRequest records.
Organisation
Fully supportedOrganisation is the top-level entity representing the law firm itself. The API exposes a single Organisation record per instance. We map firm-level settings and configuration references at migration scoping.
| Object | Support | Notes |
|---|---|---|
| Businesses | Fully supported | Businesses represent law firm clients and map directly as the primary entity. The API supports list, create, retrieve, and sanctions/company report generation. We perform a 1:1 map of Business records including address, status, and linked contacts. |
| EngageRequests | Fully supported | EngageRequests track client engagement and onboarding workflows. Each request has a status lifecycle (pending, in-progress, completed) and is linked to a Business. We pull all EngageRequest records and preserve their status and reviewer assignment at migration time. |
| RiskAssessments | Mapping required | RiskAssessments are beta-API objects that unify client, matter, and financial data. The schema includes templates and individual assessment records. We map assessment status, scoring data, and PDF output references, but PDF binary content requires separate file export handling. |
| Payments | Fully supported | Payments are linked to Businesses and tracked via checkout_url fields. The API supports list, create, retrieve, and partial update. We preserve payment status, amount, and Stripe checkout references during migration. |
| BankAccounts | Fully supported | BankAccounts are listed and retrieved per Business. The API exposes account identifiers and statuses. We map account references and current balances as of migration date. |
| Workflows | Mapping required | Workflows are referenced by ID and linked to EngageRequests. The Legl platform stores workflow definitions and reviewer assignments. We preserve workflow IDs and step completion status but note that the full workflow definition schema may require export via the browsable API UI. |
| BusinessReports | Mapping required | BusinessReports are generated on-demand and include sanctions checks and company reports. We map report metadata and status but note that report generation is asynchronous — the PDF or content must be polled or retrieved separately. |
| Reviewers | Fully supported | Reviewers are users assigned to approve EngageRequests and manual CDD steps. We map reviewer IDs and names as a reference table linked to Workflow and EngageRequest records. |
| Organisation | Fully supported | Organisation is the top-level entity representing the law firm itself. The API exposes a single Organisation record per instance. We map firm-level settings and configuration references at migration scoping. |
Gotchas
What to watch for in Legl migrations
Issues we've hit on past Legl migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Beta API endpoints carry schema stability risk
Sandbox access requires direct support contact
Payment checkout URLs reference external Stripe sessions
AML audit dashboards require real-time data from connected PMS
| Severity | Issue |
|---|---|
| Medium | Beta API endpoints carry schema stability risk |
| Medium | Sandbox access requires direct support contact |
| Low | Payment checkout URLs reference external Stripe sessions |
| Low | AML audit dashboards require real-time data from connected PMS |
Leaving Legl?
Where Legl customers move next
12 destinations Legl can migrate to.
How a Legl migration works
Four steps, Legl-specific
Connect
API key (Bearer token) into Legl. Scopes limited to read-only on the data we move.
Map
We translate Legl-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Legl quirks before production.
Migrate
Full migration with Legl rate-limit handling. Rollback available throughout.
FAQ
Legl migration FAQ
Answers to the questions buyers ask most during Legl migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Legl migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Legl.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Legl setup and destination — written quote back within a business day.