How long does a PCLaw to Nutshell migration take?

Most PCLaw to Nutshell migrations complete in 3–5 business days for firms with under 10,000 client and matter records. Firms with 10,000–50,000 records or complex matter hierarchies typically need 2–4 weeks. The longest phase is data profiling and mapping-plan construction — the actual data load into Nutshell runs in hours. The PCLaw export process (run manually by a firm admin) adds 1–3 days depending on the number of export batches required.

Will my PCLaw billing and trust-accounting data migrate to Nutshell automatically?

No. PCLaw's integrated billing engine and trust-accounting ledgers have no native equivalent in Nutshell's CRM model. FlitStack AI exports all billing transactions, invoice history, and trust balances as structured CSV rows linked to the migrated matter IDs. These files are handed off for import into a dedicated billing tool (LeanLaw, CosmoLex, QuickBooks). The financial data is preserved completely, but Nutshell itself does not replace PCLaw's billing functionality.

What happens to PCLaw matters in Nutshell after migration?

Each PCLaw matter becomes a Nutshell Deal. The matter name maps to the Deal name; matter status (Open, Closed, Pending) maps to Nutshell pipeline stage values. Practice area, responsible attorney, billing type, and billing rate are preserved as custom fields on the Deal. Sub-matters are converted to separate Deals with a custom Sub_Matter_Of__c field linking to the parent Deal. Time-entry totals and original open dates are preserved as custom fields since Nutshell has no native time-tracking object.

Can I migrate PCLaw custom fields and custom report data to Nutshell?

Yes. PCLaw custom fields defined in the Custom Reports builder are exported as name-value pairs per client and matter. We create matching Nutshell custom fields on the Person, Company, and Deal objects with the same field type (text, date, picklist). Picklist values require a value-by-value mapping when the source and destination picklist options differ. We validate the field creation in the test migration phase before the full run.

Will my PCLaw documents and files transfer to Nutshell?

PCLaw documents are stored in a file-system path, not embedded in the database. We export a document index (filename, matter association, file type, last-modified date) as a CSV linked to the migrated matter IDs. The actual files must be migrated separately to SharePoint, OneDrive, or a document management system. After the DMS migration is complete, the document index CSV allows your team to re-link files to the corresponding Nutshell Deals.

Does the migration affect my PCLaw account during the cutover?

No. PCLaw remains fully operational throughout the migration. We require only scoped read access to the exported CSV files — there is no direct database connection to PCLaw. Your team continues billing, entering time, and managing matters in PCLaw during the migration window. A 24–48 hour delta pickup at the end captures any records modified in the final hours before go-live so Nutshell reflects PCLaw's final state.

What happens to PCLaw workflows, automations, and templates after migration?

PCLaw workflows, billing templates, document templates, and automated docketing rules do not have an equivalent in Nutshell and cannot be migrated. These must be rebuilt manually in Nutshell or replaced with third-party tools. We provide a structured export of your PCLaw workflow definitions and template layouts so your Nutshell admin has a rebuild reference. Firms using PCLaw's trust-accounting automation should plan to replicate those rules in their chosen billing tool.

How are PCLaw client-to-company associations handled in Nutshell?

PCLaw allows multiple contacts per client and multiple addresses per contact. We split PCLaw clients into Nutshell Persons (individuals) and Companies (organizations). When a PCLaw client record contains both a company name and an individual contact, we create a Nutshell Company record linked to a Nutshell Person record. Multiple addresses are preserved as custom address fields or handled as separate address records if Nutshell's data model allows. The firm reviews the client-split logic during the test migration.

PCLaw(r) to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

PCLaw is an on-premise legal-practice-management and billing platform built around a Client-Matter model — firms track clients, matters, trust accounts, billing ledgers, time entries, and documents under one roof. The underlying C-tree database is exportable only via PCLaw's built-in CSV/XLSX dump; there is no public REST API. Nutshell is a cloud CRM that organizes data around People, Companies, Leads, and Deals (pipelines with stage-based tracks). The two platforms share a contacts/companies conceptual layer but diverge sharply on financial accounting and matter hierarchy. We extract PCLaw data through structured exports, clean and deduplicate client and matter records, map them to Nutshell's People and Deals objects, handle owner resolution by email match against Nutshell users, preserve original create and modification timestamps, and surface billing and trust-accounting fields for manual reconfiguration in Nutshell. Workflows, automations, document templates, and trust-ledger logic do not migrate and must be rebuilt or re-entered. During the migration, a delta window captures any changes made in PCLaw during cutover.

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

PCLaw(r)

What's pushing teams away

The interface is widely described as confusing and subpar compared to modern cloud legal software; Capterra reviewers consistently cite poor ease of use as a primary complaint.
PCLaw runs on-premises and requires Windows desktop installation, making remote work and multi-location collaboration difficult without additional RDP or terminal server infrastructure.
LexisNexis has been actively pushing existing PCLaw customers toward LEAP, its cloud-native successor, creating uncertainty about continued product support and roadmap direction.
Rival products like LeanLaw and Clio are reported to be significantly faster; one Capterra reviewer explicitly notes LeanLaw is 'mostly much faster than PCLaw.'
PCLaw lacks client portals, which modern clients increasingly expect for viewing invoices, matter status, and documents securely online.

Choosing

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 PCLaw(r) objects map to Nutshell

Each row shows how a PCLaw(r) 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.

PCLaw(r)

Client

maps to

Nutshell

Person + Company

1:many

Fully supported

PCLaw clients represent both individuals and organizations. We split on the client name and address structure: clients with a company name but no individual contact name map to Nutshell Companies; clients with an individual name map to Nutshell People. When a client has both (company + individual attorney), both records are created and linked.

PCLaw(r)

Matter

maps to

Nutshell

Deal

1:1

Fully supported

PCLaw matters map directly to Nutshell Deals. The matter name becomes the Deal name; matter status (open/closed/pending) maps to Nutshell pipeline stage values. One matter equals one deal in Nutshell's pipeline. Matter type (Practice Area) is preserved as a custom field on the Deal for filtering and reporting.

PCLaw(r)

Billing / Invoice

maps to

Nutshell

Custom Fields on Deal + External Billing Tool

1:1

Fully supported

PCLaw's billing records (invoices, payments, adjustments) have no native Nutshell equivalent. We export all billing history as structured CSV rows linked to the Matter. These are preserved for import into QuickBooks, Stripe, or another billing tool. The Matter-to-Deal link is maintained so financial history is traceable.

PCLaw(r)

Trust Account / Trust Ledger

maps to

Nutshell

Custom Fields on Deal + External Tool

1:1

Fully supported

PCLaw trust-accounting ledgers (three-way reconcile, client trust balances) have no equivalent in Nutshell CRM. We export trust balances and full transaction history as structured records linked to the matter ID. Firms must re-establish trust accounting in a dedicated tool such as LeanLaw, CosmoLex, or similar post-migration. The exported data preserves all trust activity for reconciliation.

PCLaw(r)

Time Entry

maps to

Nutshell

Custom Fields on Deal

1:1

Fully supported

PCLaw time entries (date, hours, attorney, description, billing rate) are exported and aggregated per matter. They are stored as a JSON-encoded list in a custom field on the corresponding Nutshell Deal, preserving billable-hour totals and attorney attribution. Individual time entries cannot be displayed as native Nutshell activities.

PCLaw(r)

Document / File Attachment

maps to

Nutshell

External DMS

1:1

Fully supported

PCLaw documents are stored in a file-system path referenced by the matter record. We export the file list (names, types, matter associations) as a CSV index. The actual files must be migrated separately to SharePoint, OneDrive, or a document management system; they do not attach natively to Nutshell records.

PCLaw(r)

Calendar / Docketing

maps to

Nutshell

Nutshell Tasks + External Calendar

1:1

Fully supported

PCLaw docketing entries (hearing dates, filing deadlines, reminder dates) are exported with the matter ID and due date. They are mapped to Nutshell Tasks attached to the corresponding Deal, with the original due date preserved. All-day or multi-day events require manual entry in Google Calendar or Outlook post-migration.

PCLaw(r)

PCLaw User / Attorney

maps to

Nutshell

Nutshell User

1:1

Fully supported

PCLaw attorney and staff IDs are resolved by email address against Nutshell user accounts. PCLaw does not maintain email addresses natively, so firms must provide a mapping table (PCLaw ID → email). Unmatched users are flagged and assigned to a fallback Nutshell user for review before migration.

PCLaw(r)

Custom Fields (PCLaw Custom Reports)

maps to

Nutshell

Nutshell Custom Fields

1:1

Fully supported

PCLaw custom fields defined in the Custom Reports builder are exported as name-value pairs per client and matter. We create matching Nutshell custom fields on the Person, Company, and Deal objects using the same field type (text, date, picklist). Picklist values require value-by-value mapping if the Nutshell picklist options differ from the source.

PCLaw(r)

Contact / Address

maps to

Nutshell

Person Fields

1:1

Fully supported

PCLaw client contact information (name, address, phone, email) maps to Nutshell Person fields directly. Multiple addresses per client are handled as additional address custom fields since Nutshell Persons support a single primary address. Firms with multiple billing addresses per client must pre-define how to collapse or preserve these.

PCLaw(r)	Nutshell	Compatibility
Client	Person + Company1:many	Fully supported
Matter	Deal1:1	Fully supported
Billing / Invoice	Custom Fields on Deal + External Billing Tool1:1	Fully supported
Trust Account / Trust Ledger	Custom Fields on Deal + External Tool1:1	Fully supported
Time Entry	Custom Fields on Deal1:1	Fully supported
Document / File Attachment	External DMS1:1	Fully supported
Calendar / Docketing	Nutshell Tasks + External Calendar1:1	Fully supported
PCLaw User / Attorney	Nutshell User1:1	Fully supported
Custom Fields (PCLaw Custom Reports)	Nutshell Custom Fields1:1	Fully supported
Contact / Address	Person Fields1:1	Fully supported

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.

PCLaw(r) gotchas

High

No public API forces reliance on manual CSV exports

High

Trust account data integrity requires post-migration balance validation

Medium

Billing arrangement settings are not exported by the standard export

Medium

Document binaries require a parallel file-system export

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

PCLaw(r) gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	No public API forces reliance on manual CSV exports	High	Contact tier limits enforced on import
High	Trust account data integrity requires post-migration balance validation	Medium	No bulk API endpoint requires paginated extraction
Medium	Billing arrangement settings are not exported by the standard export	Medium	Email sequences not exportable via API
Medium	Document binaries require a parallel file-system export	Medium	Foundation plan disables key sales features

Pair-specific challenges

PCLaw billing and trust-accounting records have no native Nutshell home

PCLaw's integrated billing engine — invoices, payments, trust ledgers, and three-way reconcile — is a core product feature that has no equivalent in Nutshell's CRM model. We export all billing transactions and trust balances as structured CSV rows linked to the matter ID. Nutshell does not have an invoicing, payment, or trust-accounting module; firms must connect a dedicated billing tool (LeanLaw, CosmoLex, QuickBooks) post-migration. The billing and trust data migration is a data-preservation step, not a functional replacement.
PCLaw has no public API — migration runs on CSV/XLSX exports

PCLaw exposes no REST or GraphQL API for programmatic data extraction. All migration runs on data exported through PCLaw's built-in File > Export function (clients, matters, time entries) and its Custom Reports builder (custom field data). The export process is manual and must be run by a user with full PCLaw administrative access. Large firms with thousands of matters may need to run multiple export batches. We provide a structured export checklist and validate the output before mapping begins.
PCLaw client-to-matter hierarchy does not map 1:1 to Nutshell's People-to-Deal model

PCLaw allows multiple matters per client, and matters can have sub-matters and parent-matter relationships. Nutshell Deals have a single primary Person link and no native sub-deal structure. We flatten the hierarchy: each matter becomes one Nutshell Deal linked to the primary client Person. Sub-matters are flagged and linked as separate Deals with a Sub_Matter_Of__c custom field pointing to the parent Deal. Firms with deep matter nesting must review the flattening output during the test migration phase.
PCLaw attorney and staff IDs require a manual email-mapping table before migration

PCLaw does not store email addresses for users — it uses internal numeric IDs tied to the C-tree database. To resolve PCLaw attorneys to Nutshell users, firms must provide a mapping table mapping each PCLaw ID to the corresponding email address in Nutshell. If the firm does not have this table, we work with the office manager or IT contact to reconstruct it from PCLaw's user administration report. Owner resolution is a prerequisite for the migration to proceed; unresolved records default to a fallback user.
Document files must be migrated separately from the CRM data

PCLaw documents are stored in a file-system path structure maintained by the PCLaw installation. These files (contracts, correspondence, pleadings) are not embedded in the C-tree database — they are referenced by path. We export a document index (filename, matter association, file type, last-modified date). The actual files must be migrated independently to SharePoint, OneDrive, or a document management system. The document index CSV is provided so firms can re-link files to the corresponding Nutshell Deals after the DMS migration is complete.

Migration approach

Six steps for a successful PCLaw(r) to Nutshell data migration

Run structured PCLaw exports and validate the data extract

We provide a step-by-step PCLaw export checklist covering client export, matter export, time-entry export, billing-history export, and custom-report export for custom fields. A user with full PCLaw admin access runs the exports and uploads the files to our secure intake portal. We validate the row counts, column headers, and data completeness against the firm's estimated record counts before mapping begins. Any missing fields or malformed records are flagged immediately.
Reconcile attorney IDs to Nutshell user email addresses

The firm's PCLaw administrator provides a mapping table of PCLaw user IDs to Nutshell email addresses. We load this into the migration engine and validate that every mapped email corresponds to an active Nutshell user. Any Nutshell users not on the map are flagged for the admin to resolve before migration. This step is required before owner assignment on any records can proceed.
Cleanse, deduplicate, and profile the exported data

We run data-quality profiling on the PCLaw export: identifying duplicate client records (same name and address), blank required fields, invalid date formats, and inconsistent address formatting. Duplicate clients are flagged for the firm to confirm before they are merged or kept as separate records. Matter hierarchies are flattened per the sub-matter handling rules. Billing and trust data is separated into a dedicated export package.
Map and migrate a test sample with field-level diff

We migrate a representative sample — typically 100–300 records spanning clients, matters, time entries, and custom fields — into the firm's Nutshell instance. We generate a field-level diff showing the source PCLaw value and the resulting Nutshell field for every mapped property. The firm reviews the diff, confirms practice-area mapping, verifies owner assignment, and approves the transformation logic before the full migration runs.
Run full migration with delta-pickup window

The full migration extracts the complete PCLaw dataset, applies the validated mappings, and loads records into Nutshell. A delta-pickup window of 24–48 hours captures any PCLaw records modified during the cutover window. Every operation is logged in our audit trail. If reconciliation reveals discrepancies, one-click rollback reverts the Nutshell instance to its pre-migration state. After validation, the firm receives the billing and trust-accounting CSV package for import into their chosen billing tool.

Platform deep dives

Context on both ends of the pair

PCLaw(r)

Source

Strengths

Mature, battle-tested trust accounting engine with a long record of passing bar association audits across US states.
All-in-one design combines matter management, billing, and law accounting without requiring separate accounting software.
Perpetual license model available, giving firms ownership without ongoing SaaS subscription commitments.
Comprehensive law-firm-specific billing workflows including contingency, flat-fee, and hourly arrangements per matter.
30+ years of market presence means large installed base with documented workflows and established training resources.

Weaknesses

Desktop-only architecture requires on-premises installation and lacks native cloud or mobile access without additional infrastructure.
No client portal — clients cannot view invoices, documents, or matter status online, a feature present in most modern competitors.
Outdated user interface consistently cited in reviews as confusing and difficult to navigate compared to cloud alternatives.
LexisNexis has been steering PCLaw customers toward its cloud product LEAP, raising long-term support and development concerns.
No public API means all data extraction relies on manual CSV/XLSX exports with no programmatic or automated migration path.

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

	PCLaw(r) Source	Nutshell Destination
Strengths	Mature, battle-tested trust accounting engine with a long record of passing bar association audits across US states. All-in-one design combines matter management, billing, and law accounting without requiring separate accounting software. Perpetual license model available, giving firms ownership without ongoing SaaS subscription commitments. Comprehensive law-firm-specific billing workflows including contingency, flat-fee, and hourly arrangements per matter. 30+ years of market presence means large installed base with documented workflows and established training resources.	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	Desktop-only architecture requires on-premises installation and lacks native cloud or mobile access without additional infrastructure. No client portal — clients cannot view invoices, documents, or matter status online, a feature present in most modern competitors. Outdated user interface consistently cited in reviews as confusing and difficult to navigate compared to cloud alternatives. LexisNexis has been steering PCLaw customers toward its cloud product LEAP, raising long-term support and development concerns. No public API means all data extraction relies on manual CSV/XLSX exports with no programmatic or automated migration path.	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

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from PCLaw(r) to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

PCLaw(r)

Nutshell

How PCLaw(r) objects map to Nutshell

What specifically takes care here

Six steps for a successful PCLaw(r) to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your PCLaw(r) to Nutshell migration cost

What are you migrating?

Frequently asked questions about PCLaw(r) to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from PCLaw(r).
Land in Nutshell, intact.

Migrate from PCLaw(r) to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

PCLaw(r)

Nutshell

How PCLaw(r) objects map to Nutshell

What specifically takes care here

Six steps for a successful PCLaw(r) to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your PCLaw(r) to Nutshell migration cost

Frequently asked questions about PCLaw(r) to Nutshell data migrations

Can't find your answer?

How long does a PCLaw to Nutshell migration take?

Will my PCLaw billing and trust-accounting data migrate to Nutshell automatically?

What happens to PCLaw matters in Nutshell after migration?

Can I migrate PCLaw custom fields and custom report data to Nutshell?

Will my PCLaw documents and files transfer to Nutshell?

Does the migration affect my PCLaw account during the cutover?

What happens to PCLaw workflows, automations, and templates after migration?

How are PCLaw client-to-company associations handled in Nutshell?

Related migrations to explore

Move from PCLaw(r). Land in Nutshell, intact.

Move from PCLaw(r).
Land in Nutshell, intact.