CRM migration

Migrate from PCLaw(r) to Twenty CRM

Field-level mapping, validation, and rollback between PCLaw(r) and Twenty CRM. We move data and schema; workflows are rebuilt natively in Twenty CRM.

PCLaw(r) logo

PCLaw(r)

Source

Twenty CRM

Destination

Twenty CRM logo

Compatibility

100%

10 of 10

objects map 1:1 between PCLaw(r) and Twenty CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Teams migrate from PCLaw to Twenty CRM when they need cloud access, open-source flexibility, and modern API capability to replace a Windows-only desktop platform. PCLaw structures data around Matters with client billing, trust accounting, and time tracking built in. Twenty CRM uses a standard People–Companies–Opportunities relational model with custom objects available on paid tiers. The migration carries everything PCLaw stores natively — clients, contacts, matters, time entries, billing history, trust ledgers, and custom fields — into Twenty's entity structure. The harder problems are mapping PCLaw's matter-centric model (where one client has N matters, each with its own financial ledger) into Twenty's Company-centric schema, preserving trust account balances and regulatory references in custom fields, and deciding whether to create a Matter custom object or collapse matter data onto Company or People records. Workflows, billing rules, and trust-accounting validation logic are destination-side configuration — we export the configuration definitions as reference for your rebuild.

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) logo

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

Twenty CRM logo

Twenty CRM

What's pulling them in

  • Top open-source CRM on GitHub with 40.6K stars, giving teams full source code access and infrastructure ownership without per-feature licensing surprises.
  • Free self-hosting under AGPL-3.0 means unlimited users and custom objects for the cost of cloud infrastructure alone, typically $20–100/month.
  • Pricing page explicitly mocks competitors for charging add-on fees for API access, webhooks, and workflows — transparency that resonates with RevOps teams burned by Salesforce.
  • Unlimited custom objects and fields with no price impact, letting teams shape the data model to their business rather than forcing business into rigid schemas.
  • Modern TypeScript/React/PostgreSQL stack means developer-led teams can extend, self-host, or integrate without fighting legacy architecture.

Object mapping

How PCLaw(r) objects map to Twenty CRM

Each row shows how a PCLaw(r) object lands in Twenty CRM, 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

Twenty CRM

People

1:1
Fully supported

PCLaw clients map directly to Twenty People records. The primary contact name, email, phone, address, and job title transfer as standard Twenty People fields. Original client IDs are preserved as a custom field (pclaw_client_id__c) for delta-run deduplication and audit reference.

PCLaw(r)

Client

maps to

Twenty CRM

Companies

1:1
Fully supported

PCLaw clients that represent organizations (as opposed to individual matters) map to Twenty Companies records. Company name, address, phone, and industry fields transfer directly. For solo practitioners, the attorney's name may be stored as both a People record and a Company record representing the firm.

PCLaw(r)

Matter

maps to

Twenty CRM

Custom Object: Matter

1:1
Fully supported

PCLaw matters require a custom Matter object in Twenty since Twenty's standard Opportunity object is sales-pipeline-specific and not suited for legal case management. The custom Matter object includes fields for matter number, case type, status, responsible attorney, open date, and a relation to the client People record. This custom object must be created in Settings → Data Model before import.

PCLaw(r)

Time Entry

maps to

Twenty CRM

Task / Custom Object: TimeEntry

1:1
Fully supported

PCLaw time entries map to Twenty Tasks linked to the associated Matter record when a custom Matter object is used. Each Task captures the work description, date, duration (hours), billing rate, and billable status. Non-billable administrative time maps to Tasks with a non-billable flag field. Original time entry IDs preserved as a custom field.

PCLaw(r)

Billing Record / Invoice

maps to

Twenty CRM

Custom Object: BillingRecord

1:1
Fully supported

PCLaw billing records (invoices, payments, adjustments) migrate as a custom BillingRecord object linked to the Matter. Fields include invoice number, date, amount, status (sent/paid/adjusted), payment date, and payment method. Detailed line items from invoices map to a related BillingLineItem child object if the source data supports it.

PCLaw(r)

Trust Account / IOLTA Ledger

maps to

Twenty CRM

Custom Object: TrustAccount

1:1
Fully supported

PCLaw trust account transactions (deposits, withdrawals, transfers, retainers) migrate as a custom TrustAccount object linked to the Matter and Client. Each transaction captures the trust account identifier, transaction type, amount, date, balance after transaction, and regulatory reference (IOLTA compliance notes). Balance-forward reconciliation is validated against the source trial balance before and after migration.

PCLaw(r)

Document / File Attachment

maps to

Twenty CRM

Notes / External Reference

1:1
Fully supported

PCLaw documents and file attachments associated with matters migrate as Twenty Notes records with file references. Large files may be re-uploaded to the firm's chosen document storage (SharePoint, Google Drive) and referenced via URL in the Note body. The Note is linked to the corresponding Matter and Client records. Inline images and PDFs are preserved and re-hosted at the destination URL.

PCLaw(r)

Calendar / Appointment

maps to

Twenty CRM

Task

1:1
Fully supported

PCLaw calendar appointments map to Twenty Tasks with due dates, assignees, and the associated Matter or Client as the parent record. Meeting or hearing dates transfer with original timestamps preserved as a custom datetime field (original_event_date__c). Outlook or Google Calendar integration set up post-migration can replace the native PCLaw calendar.

PCLaw(r)

Custom Field (per matter type)

maps to

Twenty CRM

Custom Field (on relevant object)

1:1
Fully supported

PCLaw custom fields defined per matter type are mapped to Twenty custom fields on the Matter object or on People/Companies depending on scope. Each custom field type (text, number, date, pick-list) maps to the equivalent Twenty field type. Pick-list values require value-by-value mapping if the source and destination pick-list sets differ. All destination custom fields must be created before import runs.

PCLaw(r)

User / Staff Member

maps to

Twenty CRM

WorkspaceMember

1:1
Fully supported

PCLaw staff members (attorneys, paralegals, billing staff) map to Twenty Workspace Members. Resolution happens by email match — the staff member's email address in PCLaw is matched against invited Twenty users. Unmatched staff records are flagged before migration. Owner assignments on matters, time entries, and billing records are updated to the resolved Workspace Member.

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) logo

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

Twenty CRM logo

Twenty CRM gotchas

High

Import order is enforced and critical

High

Export limited to 20,000 records and visible columns only

Medium

Soft-deleted records count toward uniqueness and trigger restores

Medium

API rate limits cap at 200 req/min on Organization tier

Low

No native email sequences — follow-up cadences require external tools

Pair-specific challenges

  • Matter-to-entity structural mismatch requires a custom object

    PCLaw organizes all data around Matters — each matter has its own client, billing ledger, trust ledger, and time entries. Twenty CRM's standard objects (People, Companies, Opportunities) are entity-centric and do not include a native Matter object. FlitStack AI must create a custom Matter object in Twenty's Data Model before migration runs, with fields for matter number, case type, status, responsible attorney, open/close dates, and relations to People and TrustAccount custom objects. Without this custom object, matter history collapses onto People records and loses the client-to-matter one-to-many relationship that PCLaw preserves.

  • Trust account reconciliation requires manual validation after migration

    PCLaw's three-way reconciliation (trust ledger, client ledger, operating account) is a regulatory requirement for IOLTA accounts. Twenty CRM has no native trust accounting module — trust balance fields migrate as custom number fields on the TrustAccount custom object, and the three-way reconciliation logic must be rebuilt manually in Twenty's workflow builder or as a custom extension. FlitStack AI migrates the raw transaction data and the running balance at time of migration, but the reconciliation validation checks (ensuring the trust balance matches the sum of transactions) require post-migration verification against PCLaw's trial balance report.

  • Custom fields must be pre-created in Twenty before import runs

    Twenty's CSV import creates records but not fields — the platform requires all custom fields to exist in Settings → Data Model before the import step. PCLaw setups with more than 10 custom matter fields, multiple matter types with different field sets, or custom billing rate structures require pre-migration configuration work. FlitStack AI delivers a field-creation checklist as part of the migration plan, mapping each PCLaw custom field name and type to the equivalent Twenty custom field. If a custom field is missing at import time, the corresponding data column is skipped and flagged for manual backfill.

  • Import order dependency: Companies/People must exist before Matters link

    Twenty's import mechanism requires the 'one' side of a one-to-many relationship to exist before importing records that reference it. Specifically, People records must be imported before Matters can link to them via the client relation field, and TrustAccount records must link to existing Matters. FlitStack AI sequences the migration as: (1) People, (2) Companies, (3) Matter custom object, (4) TrustAccount custom object, (5) BillingRecord custom object, (6) Tasks/TimeEntries. If this sequence is violated, import errors occur because the parent record does not yet exist for the foreign key relationship.

  • Workspace members must be invited to Twenty before owner resolution

    PCLaw staff members (attorneys, paralegals, billing clerks) are resolved to Twenty Workspace Members by email matching. However, Twenty requires users to accept an invitation and appear in Settings → Members before their email can be used as a valid relation target in imported records. If a staff member in PCLaw does not have a corresponding invited Twenty user, their records (matters, time entries, billing) are assigned to a fallback owner and flagged in the migration report for manual reassignment post-migration.

Migration approach

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

  1. Audit PCLaw data and design Twenty custom object schema

    FlitStack AI exports a full data inventory from PCLaw — all clients, matters, time entries, billing records, trust transactions, documents, and custom fields. We then design the Twenty custom object schema (Matter, TrustAccount, BillingRecord) with field types matching the PCLaw data model, and deliver a pre-migration checklist so your Twenty admin creates all custom fields and invites all staff members before the import runs. This step takes 3–5 business days and produces a field-mapping document reviewed by your team.

  2. Invite staff members and create custom fields in Twenty

    Your Twenty admin (or our team acting as admin) creates the Matter, TrustAccount, and BillingRecord custom objects in Settings → Data Model, adds all custom fields with correct types and pick-list values, and invites all staff members via Settings → Members. Staff must accept invitations before migration so owner resolution works correctly. This is a prerequisite step — the migration pipeline will fail or skip records with unresolved owners if staff members are not present in Twenty.

  3. Run sample migration with field-level diff

    A representative slice of PCLaw data migrates to Twenty first — typically 200–500 records covering 10–20 clients, 20–50 matters across different case types, 100–200 time entries, and sample trust/billing records. FlitStack AI generates a field-level diff report showing every mapped field, the source value, the destination value, and any skipped or transformed fields. You verify matter-to-client linking, trust balance reconciliation, and billing status mapping before the full run commits. Sample migration typically completes in 4–8 hours.

  4. Execute full migration with sequenced import

    Full migration runs in the validated sequence: (1) People, (2) Companies, (3) Matter custom object, (4) TrustAccount custom object, (5) BillingRecord custom object, (6) Tasks/TimeEntries. Each stage waits for the previous stage's validation report to clear before proceeding. FlitStack AI handles the CSV formatting, column mapping, and API batch calls for each object. The full migration for a medium-sized firm (10,000–50,000 records) completes in 24–72 hours.

  5. Delta pickup and trust balance validation

    A delta-pickup window (24–48 hours) captures any PCLaw records created or modified during the cutover window — new time entries, billing payments, or trust transactions entered by staff working in PCLaw during migration. FlitStack AI also validates trust account reconciliation: the sum of migrated trust transactions must equal the PCLaw trial balance total within $0.01. If reconciliation fails, a rollback is available. The audit log captures every operation for post-migration compliance review.

Platform deep dives

Context on both ends of the pair

PCLaw(r) logo

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.
Twenty CRM logo

Twenty CRM

Destination

Strengths

  • AGPL-3.0 open-source license with full source code on GitHub — no vendor lock-in, no sunset risk.
  • Unlimited users and unlimited custom objects on self-hosted, with no feature gating based on headcount.
  • REST and GraphQL APIs available on all paid tiers, not locked behind an enterprise add-on fee.
  • MCP server and webhooks shipped as standard features, not premium upgrades.
  • Modern PostgreSQL-backed data model that developer teams can query, extend, and self-host.

Weaknesses

  • Recent v1.0 release means limited production hardening compared to CRMs with multi-year operational track records.
  • No native email sequencing or sales engagement tools — follow-up cadences require a separate platform.
  • No native two-way email sync or inbox integration, requiring third-party connectors for full activity logging.
  • Self-hosting 'free' pricing hides real infrastructure and DevOps costs that stack up over time.
  • Workflow automation is functional but lacks the complexity needed for sophisticated multi-step sales motions.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 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 PCLaw(r) and Twenty CRM.

  • Object compatibility

    B

    2 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

    PCLaw(r): Not applicable.

  • Data volume sensitivity

    B

    PCLaw(r) doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your PCLaw(r) to Twenty CRM 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 PCLaw(r) to Twenty CRM data migrations

Answers to the questions buyers ask most during PCLaw(r) to Twenty CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your PCLaw(r) to Twenty CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most PCLaw-to-Twenty migrations complete in 3–5 days for under 10,000 total records. Firms with 10,000–100,000 records including matters, time entries, and trust transactions typically need 1–2 weeks. The longest planning step is designing the custom Matter and TrustAccount object schema and getting all custom fields created in Twenty before import runs. Complex trust accounting reconciliation and multi-matter billing structures extend the timeline by 1–2 weeks for validation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from PCLaw(r).
Land in Twenty CRM, 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