CRM migration

Migrate from Legl to Nutshell

Field-level mapping, validation, and rollback between Legl and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Legl logo

Legl

Source

Nutshell

Destination

Nutshell logo

Compatibility

83%

10 of 12

objects map 1:1 between Legl and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Legl is a legal-practice management platform centered on businesses, contacts, matters, documents, payments, and risk assessments — with a JSON-RPC API that returns structured data at endpoints like /listBusinesses, /listContacts, and /listMatters. Nutshell is an SMB CRM that organizes records into People, Companies, Leads, Deals, and Activities with custom fields available per entity type. The two platforms share no native equivalent for Legl's matter lifecycle stages, document repositories, payment ledgers, or risk-assessment objects. We map Legl's Business and Contact records to Nutshell's Company and Person objects respectively; Legl matters map to Nutshell Deals with a custom matter-type field; documents and payments are stored as custom fields and Activity notes; risk assessments are preserved as custom fields on the relevant Deal. Workflows, automations, and document templates in Legl do not migrate — they must be rebuilt in Nutshell or handled outside the CRM. Our migration engine reads from Legl's REST API under a scoped token and writes to Nutshell via its JSON-RPC API, respecting Legl's 3,600 requests-per-hour sustained rate limit by batching reads. A sample migration of 100–300 records runs first with field-level diff output before the full run commits.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Legl logo

Legl

What's pushing teams away

  • 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.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Legl objects map to Nutshell

Each row shows how a Legl object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Legl

Business

maps to

Nutshell

Company

1:1
Fully supported

Legl Business maps to Nutshell Company. The Legl /listBusinesses endpoint returns name, domain, address, and contact count. We map name to Nutshell's name field, domain to website, and the Legl business ID to a custom external_id field for traceability. Primary address components split into Nutshell's address fields.

Legl

Contact

maps to

Nutshell

Person

1:1
Fully supported

Legl Contact maps to Nutshell Person. First name, last name, email, phone, and job title transfer directly. Nutshell Persons link to the parent Company record via a company association field — we resolve this by matching on the Legl business_id that owns each contact. Unmatched contacts land as Leads in Nutshell pending resolution.

Legl

Matter

maps to

Nutshell

Deal

1:1
Fully supported

Legl Matters have no direct Nutshell equivalent — Nutshell Deals track sales opportunities, not legal matters. We map matters to Nutshell Deals, preserving the matter name as Deal name, the matter amount or estimated value as Deal amount, and the matter stage (open, in-progress, closed) as Deal stage. A custom pick-list field (Matter_Type__c) identifies which Nutshell Deals originated from Legl matters.

Legl

Matter Stage

maps to

Nutshell

Deal Stage

1:1
Fully supported

Legl matter lifecycle stages (Intake, Active, Awaiting-Info, Closed-Won, Closed-Lost) map value-by-value to Nutshell Deal stage names. We define the stage mapping at migration time based on the firm's current stage labels in Legl. Stage-transition timestamps from Legl are stored as custom datetime fields on the Nutshell Deal for audit continuity.

Legl

Document

maps to

Nutshell

Activity + Custom Field

many:1
Fully supported

Legl documents (metadata + binary URL) merge into two Nutshell destinations: document name and Legl storage URL go into a custom URL field (Document_Link__c) on the linked Deal; a Nutshell Activity of type Note records the document type, upload date, and uploader name. Large document archives are exported to a ZIP with folder structure matching the Legl matter tree and stored externally, with the archive link captured in Nutshell.

Legl

Payment

maps to

Nutshell

Activity

many:1
Fully supported

Legl payment records from /listPayments — amount, date, payment method, status — are written as Nutshell Activity notes on the related Deal. The note format is 'PAYMENT: [amount] [currency] on [date] via [method] — [status]'. Full payment history for a client is also aggregated into a custom text area field (Payment_Summary__c) on the parent Company record.

Legl

RiskAssessment

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

Legl RiskAssessments are legal-compliance records with templates, statuses, and PDF outputs. Nutshell has no native equivalent. We create a custom multi-select field (Risk_Assessment_Status__c) on the Deal and store the latest assessment date, template name, and status. The PDF is re-uploaded as a Nutshell file attachment and linked via a custom URL field (Risk_Assessment_PDF__c).

Legl

BankAccount

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

Legl /listBankAccounts exposes client or firm bank account records. Nutshell has no native banking field. Bank account references are stored as a custom text field (Bank_Account_Ref__c) on the Company record for reference — actual banking integrations are handled outside Nutshell.

Legl

EngageRequest

maps to

Nutshell

Activity

1:1
Fully supported

Legl EngageRequests from the /listEngageRequests endpoint represent compliance or onboarding workflow instances. These map to Nutshell Activities with type Note, capturing the request type, status, reviewer, and timestamps. The activity is linked to the parent Business or Matter Deal. This includes compliance approvals, client onboarding steps, and other workflow-driven requests from Legl.

Legl

Custom Fields on Business

maps to

Nutshell

Custom Fields on Company

1:1
Fully supported

Any Legl Business custom fields not covered by standard mappings require Nutshell custom fields created before migration. We generate a custom-field creation plan per Legl field type — text, number, date, pick-list — and map the field values during the migration run. Fields with pick-list values in Legl are recreated as pick-lists in Nutshell.

Legl

Custom Fields on Contact

maps to

Nutshell

Custom Fields on Person

1:1
Fully supported

Legl contact custom properties (beyond name, email, phone) map to Nutshell Person custom fields. Type-aware mapping applies: Legl text fields become Nutshell text fields, numeric properties become number fields, and date fields are preserved as date fields. Multi-select properties map to Nutshell multi-select where supported.

Legl

Owner / User

maps to

Nutshell

User

1:1
Fully supported

Legl stores an owner_id on matters and contacts. Owner resolution is by email match against Nutshell users. If a Legl owner email has no matching Nutshell user account, the record is assigned to a fallback Nutshell user designated by the firm, and the original owner ID is preserved in a custom text field (Original_Owner_ID__c).

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Legl logo

Legl gotchas

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Legl API rate limiting caps large archive reads to 3,600 req/hr sustained

    Legl's JSON-RPC API enforces a sustained rate limit of 3,600 requests per hour with a burst ceiling of 120 requests per minute before returning 429 errors. Large matter archives — especially firms with years of documents and payments — exceed this ceiling during a full data pull. FlitStack AI handles this by batching Legl reads in 500-record pages with exponential backoff between pages, and by caching previously fetched records between the sample and full runs. We surface any records that hit a 429 during the sample migration so you can decide whether to throttle the full run or request a temporary Legl API rate-limit increase.

  • Legal-matter attributes require custom fields with no native Nutshell equivalent

    Nutshell is a sales CRM with no built-in concept of legal matters, billing rates, matter types, or risk-assessment templates. Every Legl-specific attribute — matter_type, billing_rate, risk_assessment_status, document links, payment ledger summaries — must land in a Nutshell custom field. We generate a custom-field creation plan before migration and create those fields in Nutshell first, but the field-creation step requires a Nutshell admin with field-creation permissions. Firms with 20+ custom properties on matters will have a multi-step setup phase before data moves.

  • Legl no-code workflows and client-facing portals do not migrate to Nutshell

    Legl's no-code workflow engine (internal escalations, client onboarding funnels, department-specific processes) is a Legl-native construct with no equivalent in Nutshell. These must be rebuilt manually — Nutshell Pro offers email sequences and basic task automation, but client-facing onboarding portals and department-specific escalation rules are outside Nutshell's scope. We export the Legl workflow definitions as a structured JSON document that your team or a Nutshell consultant can use as a rebuild reference.

  • Nutshell's reporting is basic compared to Legl's compliance dashboards

    Legl provides department-level activity views, AML audit logs, and completion-rate insights that have no equivalent in Nutshell's native reporting. G2 reviewers consistently note that Nutshell reporting is sufficient for SMB sales pipeline management but often requires exporting to Excel for deeper analysis. Compliance and risk-reporting data from Legl (AML audit trails, matter completion rates, risk-assessment dates) will be present in Nutshell as custom fields and Activities, but the automated dashboards Legl provides must be rebuilt manually or via a BI tool connected to Nutshell's API.

  • Document binaries require re-upload to Nutshell or external storage

    Legl stores document metadata and binaries behind its own storage layer, accessible via URLs returned by the /retrieveDocument endpoint. Nutshell Activities support note attachments up to 25MB per file. For large document archives, we re-upload document binaries as Nutshell file attachments and link them to the correct Matter Deal. For archives exceeding Nutshell's file-size limits, we package the archive as a ZIP stored externally and record the archive URL in a custom Document_Archive_Link__c field on the Company record.

Migration approach

Six steps for a successful Legl to Nutshell data migration

  1. Audit Legl API data and design Nutshell custom fields

    FlitStack AI connects to Legl under a scoped read token and walks the API endpoints — /listBusinesses, /listContacts, /listMatters, /listDocuments, /listPayments, /listRiskAssessments — to build a data inventory. We count records per object type, identify custom fields on each entity, and assess document volume. Simultaneously, we design the Nutshell custom fields required to carry over legal-matter attributes: Matter_Type__c, Billing_Rate__c, Risk_Assessment_Status__c, Document_Link__c, Payment_Summary__c, and others. We deliver a custom-field creation plan for your Nutshell admin to execute before the migration run.

  2. Resolve Legl owners to Nutshell users by email

    Legl stores an owner_id on matters and contacts. We extract all unique owner emails from Legl and match them against Nutshell user accounts. Owners with no matching Nutshell email are flagged before migration — your team either creates Nutshell accounts for them or designates a fallback owner. No record migrates without a resolved Nutshell owner, and the original Legl owner ID is preserved in Original_Owner_ID__c for audit purposes.

  3. Run a sample migration with field-level diff

    A representative sample of 200–500 records — spanning Business, Contact, Matter, Payment, and RiskAssessment objects — migrates first. We generate a field-level diff showing the source value from Legl and the destination value written to Nutshell for every mapped field. You verify that matter stages map correctly to Nutshell Deal stages, document links resolve, and owner resolution is accurate before the full run commits. This is also when you confirm which Nutshell fallback owner receives unresolved records.

  4. Execute full migration with batched Legl API reads and delta window

    The full migration runs in phases: Businesses → Companies first (to satisfy Nutshell's parent-company dependency), then Contacts → Persons, then Matters → Deals with stage and matter-type mapping applied per value map. Document metadata migrates as Activity notes with Document_Link__c populated; document binaries re-upload as Nutshell file attachments. Payments write as Activity notes with payment-summary fields updated on the Deal. A 24–48 hour delta window follows the initial load, capturing any Legl records modified during cutover. All operations are logged in an audit trail, and one-click rollback is available if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Legl logo

Legl

Source

Strengths

  • Purpose-built for law firm client onboarding and AML compliance workflows
  • ISO 27001:2013 certified platform with documented information security controls
  • Well-structured REST API with OpenAPI spec and browsable HTML interface
  • Rate limits are generous at 3600 req/hour with a sandbox environment for integration testing
  • Connects natively with major legal PMS platforms including Clio, Actionstep, Proclaim, and P4W

Weaknesses

  • Legl functions as an overlay/orchestration layer rather than a full practice management system
  • No public pricing published — sales-led engagement required to obtain tier details
  • Zero reviews on G2 and no presence on Capterra makes independent evaluation difficult
  • Beta API endpoints for RiskAssessments may change schema without advance notice
  • Historical transaction journals and matter narrative content are not exposed via API — reside in connected PMS
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Legl and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Legl: 3600 requests per hour sustained, burst rate of 120 requests per minute.

  • Data volume sensitivity

    B

    Legl doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Legl to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Legl to Nutshell data migrations

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

Can't find your answer?

Walk through your Legl to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Legl-to-Nutshell migrations complete in 24–48 hours for setups under 10,000 records. Large matter archives — firms with years of documents, payments, and risk assessments — extend to 5–10 days, primarily due to Legl's 3,600 requests-per-hour API rate limit, which caps read throughput and requires throttled batch reads. Custom-field creation before the migration run adds 1–2 days if your Nutshell admin needs to set up Matter_Type__c, Billing_Rate__c, and similar legal-specific fields.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Legl.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day