CRM migration

Migrate from Legal Workspace to Nutshell

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

Legal Workspace logo

Legal Workspace

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between Legal Workspace and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Legal Workspace organizes legal practice data around matters, clients, contacts, and billing — a structure optimized for law firm workflow tracking. Nutshell is a CRM built around people, companies, leads, and deals with pipeline stages tied to sales cycles. FlitStack AI migrates Legal Workspace client records as Nutshell Companies, individual contacts as Nutshell People, and matters as Nutshell Deals with a custom matter-type field preserving the original matter classification. Time entries map to Nutshell Tasks; document file content cannot transfer but file name, type, and URL references migrate as custom fields. We do not migrate Legal Workspace workflows, document templates, billing templates, or matter-type automation rules — those must be rebuilt in Nutshell's automation tools. We extract from Legal Workspace via its REST export endpoints and load into Nutshell via the JSON-RPC API using Nutshell's field-type schema so custom fields land as the correct data type on the correct entity.

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

Legal Workspace logo

Legal Workspace

What's pushing teams away

  • Single-tier pricing means small firms with junior fee-earners or part-time staff pay full price per seat with no entry tier.
  • UK-centric — features and compliance posture target UK firms; multi-jurisdiction firms may need a more international product.
  • Cannysoft is a smaller vendor — partner/consultant ecosystem is narrower than mainstream legal CRMs (Clio, LEAP, Actionstep).
  • No public API documentation — custom integrations require Cannysoft engagement.
  • Customers needing trust accounting at scale typically combine Legal Workspace with a separate ledger tool, since the platform's billing module focuses on time and fees rather than client account compliance.

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 Legal Workspace objects map to Nutshell

Each row shows how a Legal Workspace 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.

Legal Workspace

Client

maps to

Nutshell

Company

1:1
Fully supported

Legal Workspace client records map 1:1 to Nutshell Company records. Client name becomes Company name, and client address fields map to Nutshell's corresponding address fields. Parent-client hierarchies in Legal Workspace are preserved using Nutshell's parent-company reference field, maintaining organizational structure across the migration.

Legal Workspace

Contact

maps to

Nutshell

Person

1:1
Fully supported

Individual contacts in Legal Workspace map directly to Nutshell Person records. Email, phone, title, and address fields carry over without transformation. Nutshell associates each Person with the corresponding Company record automatically by matching email domain or through explicit company assignment during migration.

Legal Workspace

Matter

maps to

Nutshell

Deal

1:1
Fully supported

Legal Workspace matters map to Nutshell Deals. The matter name becomes the deal name. The linked client becomes the deal's associated Company. Matter type, status, responsible attorney, and billing rate are stored as Nutshell custom fields on the deal. Nutshell deal stage maps to a custom matter-status picklist so the original workflow state is preserved.

Legal Workspace

Time Entry

maps to

Nutshell

Task

1:1
Fully supported

Nutshell has no native billing or time-tracking object, so Legal Workspace time entries migrate as Nutshell Tasks with a custom duration field (hours), a custom billing rate field, and a flag for billable or non-billable. Each Task is linked to the corresponding Deal (mattery) and the Person (attorney or staff) who logged the time.

Legal Workspace

Document metadata

maps to

Nutshell

Custom field (Deal)

1:1
Fully supported

Legal Workspace document attachments include file name, MIME type, upload date, and uploader. The file binary cannot be stored in Nutshell. We migrate the document metadata as a custom text field on the deal (Matter_Documents__c) containing a newline-separated list of file names and upload timestamps. The source URLs are preserved for manual re-upload if needed.

Legal Workspace

User / Attorney

maps to

Nutshell

User

1:1
Fully supported

Legal Workspace users (attorneys, paralegals, billing staff) are matched to Nutshell Users by email address. Nutshell's single-owner model means each matter-role (responsible attorney, lead attorney, billing attorney, paralegal) is stored in a separate custom field on the deal rather than as a native role assignment.

Legal Workspace

Matter Custom Fields

maps to

Nutshell

Custom fields on Deal

1:1
Fully supported

Legal Workspace allows custom fields on matters. We create matching custom fields in Nutshell per the field type — picklist values become Nutshell picklist options, date fields become Nutshell date fields, and text fields become Nutshell text fields. The field label and help text are preserved.

Legal Workspace

Client Custom Fields

maps to

Nutshell

Custom fields on Company

1:1
Fully supported

Client-level custom fields in Legal Workspace, such as client tier, intake source, or billing arrangement, are translated to Nutshell Company custom fields. The field type from Legal Workspace determines the target field type in Nutshell, with picklist values migrated verbatim to preserve data integrity across all client records.

Legal Workspace

Contact Custom Fields

maps to

Nutshell

Custom fields on Person

1:1
Fully supported

Contact-level custom fields in Legal Workspace, such as bar number, practice area, or LinkedIn URL, are mapped to Nutshell Person custom fields. The field type from Legal Workspace determines the target field type in Nutshell, ensuring accurate data representation across the migrated contact records.

Legal Workspace

Workflow / Automation

maps to

Nutshell

None

1:1
Fully supported

Legal Workspace workflows, matter automation rules, and notification triggers have no Nutshell equivalent. These must be rebuilt using Nutshell's automation features, including Tasks, email sequences, and platform integrations. We export workflow definitions as a structured reference document to support your rebuild, including rule names and trigger conditions.

Legal Workspace

Billing Templates / Rates

maps to

Nutshell

Custom fields on Deal

1:1
Fully supported

Legal Workspace billing rate schedules and matter-specific rate overrides are stored as custom fields on the deal. Nutshell has no native billing engine, so these financial values are preserved as reference fields for your finance team to reconcile billing data outside Nutshell as needed.

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.

Legal Workspace logo

Legal Workspace gotchas

Medium

Document templates and custom fields are configuration data, not matter data

Medium

Integrated timer entries and manual time records use different storage paths

High

No public API or developer portal

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

  • Matter-to-deal 1:1 flattening collapses parent-child matter hierarchies

    Legal Workspace supports nested matter structures where a parent matter can contain sub-matters. Nutshell Deals have no native parent-deal hierarchy. We flatten each Legal Workspace matter — including sub-matters — into a separate Nutshell Deal. The parent matter's ID is preserved in a custom field (Parent_Matter_ID__c) so you can reconstruct the hierarchy manually in Nutshell or via a reporting tool. This is a structural limitation of Nutshell's CRM model, not a data loss event; all sub-matter records are migrated.

  • Nutshell's single-owner model loses multi-role attorney assignments per matter

    Legal Workspace assigns multiple attorneys and staff to a single matter (responsible attorney, lead attorney, billing attorney, paralegal, and review attorney each have distinct roles). Nutshell assigns exactly one Owner to a deal. We store all Legal Workspace role assignments as custom text fields on the deal (Responsible_Attorney__c, Billing_Attorney__c, Paralegal__c) resolved by email match to Nutshell Users. The role labels are preserved; the native Nutshell owner field is set to the responsible attorney by default.

  • Document file binaries do not transfer to Nutshell

    Legal Workspace documents attached to matters are binary files stored in the platform's document management layer. Nutshell has no native document storage — files cannot be re-hosted inside the CRM. We migrate document metadata (file name, MIME type, upload date, uploader, and file size) as a structured custom field on the deal. You receive a companion export package of original file URLs for manual re-upload to a linked storage system such as Google Drive, SharePoint, or a document management platform.

  • Legal Workspace time entries cannot produce billable records in Nutshell

    Nutshell has no native time-tracking or billing engine — Tasks are the closest CRM analogue but they are not billable records. Legal Workspace time entries with hours, rates, and billable flags migrate as Nutshell Tasks with custom fields for duration, billing rate, and billable flag. Finance teams using Nutshell for practice management must reconcile time data outside the CRM or connect Nutshell to a billing integration. The financial totals from Legal Workspace are preserved as custom fields on the migrated deals for reference.

  • Matter-type automation and workflow rules must be rebuilt in Nutshell

    Legal Workspace workflow automation rules (matter-stage triggers, automated notifications, assignment rules based on matter type or value) have no Nutshell equivalent. Nutshell's automation is limited to Tasks and email sequences on deals. We export Legal Workspace workflow definitions as a structured reference document that your Nutshell administrator can use to rebuild equivalent automation. The exported definition includes rule name, trigger conditions, and action types extracted from your Legal Workspace configuration.

Migration approach

Six steps for a successful Legal Workspace to Nutshell data migration

  1. Extract Legal Workspace data via admin export

    FlitStack AI authenticates against your Legal Workspace admin account using scoped read access to export all clients, contacts, matters, time entries, and document metadata. We pull the full schema first to capture custom field names, data types, and picklist values before the data extraction. The export runs in batches to avoid timeout errors and produces a structured JSON dataset organized by entity type. Your Legal Workspace account remains fully operational during this step — we use read-only endpoints only.

  2. Map schema and create Nutshell custom fields

    FlitStack AI analyzes the Legal Workspace export schema and maps each field to the appropriate Nutshell entity and field type. Custom fields that do not exist in Nutshell (matter_type, responsible_attorney, billing_rate, and others) are pre-created via the Nutshell API before the migration load begins. We configure picklist options, field labels, and help text to match Legal Workspace exactly. At this stage we also define the value-mapping table for matter status to Nutshell deal stage.

  3. Resolve users and establish attorney-role fields

    Legal Workspace user records are matched to Nutshell Users by email address. Any Legal Workspace user without a corresponding Nutshell account is flagged before migration so your team can provision accounts or assign a fallback owner. Multi-role attorney assignments are written to the custom fields on each deal (Responsible_Attorney__c, Billing_Attorney__c, Paralegal__c) rather than the Nutshell native owner field, which holds only one value per record.

  4. Run sample migration with field-level diff

    A representative sample — typically 100–500 records spanning clients, contacts, matters, and time entries — migrates into Nutshell first. FlitStack AI generates a field-level diff comparing source and destination values for every mapped field so you can verify that matter types, billing rates, and attorney assignments landed correctly before the full run. You review the sample in Nutshell and approve or request adjustments to the field mapping.

  5. Execute full migration with delta-pickup and rollback

    The full Legal Workspace dataset loads into Nutshell via the JSON-RPC API, sequenced so companies create before contacts, and contacts before matters. A delta-pickup window (24–48 hours) captures any new or modified records in Legal Workspace during cutover so Nutshell reflects your final state at go-live. FlitStack AI provides an audit log of every record operation and a one-click rollback that removes all migrated records if reconciliation fails. Document file metadata and workflow export are delivered as separate reference packages alongside the CRM migration.

Platform deep dives

Context on both ends of the pair

Legal Workspace logo

Legal Workspace

Source

Strengths

  • Predictable single-price model with all features included.
  • UK-specific GDPR posture and SRA-aligned workflows.
  • Customisable templates, fields, and user permissions out of the box.
  • Integrated time tracking and billing reduce tool sprawl for small firms.
  • Mobile app plus modern browser access for remote work.

Weaknesses

  • Single flat tier — no junior or part-time discount.
  • Smaller vendor; narrower consultant/partner ecosystem.
  • No public API documentation.
  • UK-centric — limited fit for cross-jurisdictional firms.
  • Trust accounting depth is limited versus dedicated legal accounting tools.
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 Legal Workspace 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

    Legal Workspace: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Legal Workspace 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 Legal Workspace to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Legal Workspace to Nutshell migrations complete in 24–72 hours of clock time for under 10,000 records. Complex setups with nested matter hierarchies, multiple custom fields per entity, or more than 100,000 records extend the timeline to 5–10 days. The longest planning step is schema mapping for matter-type custom fields and multi-role attorney assignments before the first test migration runs, followed by the sample migration review cycle.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Legal Workspace.
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