CRM migration

Migrate from The Attorney Case File to Twenty CRM

Field-level mapping, validation, and rollback between The Attorney Case File and Twenty CRM. We move data and schema; workflows are rebuilt natively in Twenty CRM.

The Attorney Case File logo

The Attorney Case File

Source

Twenty CRM

Destination

Twenty CRM logo

Compatibility

92%

11 of 12

objects map 1:1 between The Attorney Case File and Twenty CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

The Attorney Case File organizes legal work around Cases and Client Workbooks — a structure that prioritizes matter-centric billing and court-date tracking over the contact-opportunity model that Twenty CRM uses. This migration translates that model: clients become Twenty's People objects, cases map to Opportunities or custom objects depending on your pipeline complexity, and billable hours become custom number fields on the case record. We map documents to Twenty Notes, tasks to Twenty Tasks, and surface The Attorney Case File's custom fields as Twenty custom fields so case context carries across. The migration runs via Twenty's REST and GraphQL API at 100–200 calls per minute depending on your tier. We sequence the load so Companies land before People (Twenty's import order requirement) and we resolve attorney and paralegal users by email match against Twenty workspace members. Workflows, email templates, and document templates in The Attorney Case File do not migrate — we export them as a reference package for your team to rebuild in Twenty. A 24–48 hour delta pickup window captures any case updates made 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

The Attorney Case File logo

The Attorney Case File

What's pushing teams away

  • Users handling multi-party or high-complexity litigation report the system reaches its limits and lacks the structural depth required for matters with numerous interrelated parties and documents.
  • The document management component draws consistent criticism for being underpowered — attorneys working with large document volumes find it inadequate for their needs.
  • At least one review flags platform stability concerns and lack of clear development roadmap, leaving practitioners uncertain about long-term viability and feature evolution.

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 The Attorney Case File objects map to Twenty CRM

Each row shows how a The Attorney Case File 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.

The Attorney Case File

Client / Contact

maps to

Twenty CRM

People

1:1
Fully supported

The Attorney Case File clients map directly to Twenty People records. Email, phone, address, and job title fields transfer as-is. The primary attorney assignment in The Attorney Case File becomes a relation field pointing to the attorney user in Twenty's workspace.

The Attorney Case File

Client Organization

maps to

Twenty CRM

Company

1:1
Fully supported

Corporate clients and law firm organizations map cleanly to Twenty Companies. Company name, domain, industry classification, and employee count fields migrate directly without transformation. Multi-contact relationships that exist in The Attorney Case File collapse to the primary contact link in Twenty's standard data model, requiring manual linking for secondary contacts.

The Attorney Case File

Case / Matter

maps to

Twenty CRM

Opportunity

1:1
Fully supported

Cases translate to Twenty Opportunities using a practice-area or matter-type field as the pipeline stage source. Case number becomes a custom text field (Case_Number__c) on the Opportunity record for reference. Closed-won and closed-lost statuses from The Attorney Case File map appropriately to Twenty's resolved stage values to maintain workflow continuity.

The Attorney Case File

Case Status

maps to

Twenty CRM

Opportunity Stage

1:1
Fully supported

The Attorney Case File's status values including Active, Pending, Closed, and On Hold map one-to-one to corresponding Twenty Opportunity stage values. We carefully preserve the original status-changed timestamp as a custom datetime field on the record for reporting continuity and historical tracking purposes.

The Attorney Case File

Billable Hours / Time Entries

maps to

Twenty CRM

Custom Object: Time_Entry__c

1:1
Fully supported

Billable hours do not have a native Twenty equivalent. We create a custom object (Time_Entry__c) linked to the Case Opportunity with fields for date, hours, rate, description, and billing status. Invoice generation requires rebuilding in Twenty or a connected accounting tool.

The Attorney Case File

Court Dates / Deadlines

maps to

Twenty CRM

Task

1:1
Fully supported

Court dates and filing deadlines migrate as Twenty Tasks with the original due date preserved and the case Opportunity linked as the parent record. Reminder settings reset to Twenty defaults — The Attorney Case File's custom reminder triggers do not carry over.

The Attorney Case File

Documents / Attachments

maps to

Twenty CRM

Note + Attachment

1:1
Fully supported

Documents attached to cases in The Attorney Case File are downloaded and re-uploaded to Twenty as file attachments on the associated Opportunity record. Inline document links are replaced with Twenty's native attachment references. Version control history is not preserved through this process — only the latest current version migrates over to Twenty's attachment system.

The Attorney Case File

Notes / Observations

maps to

Twenty CRM

Note

1:1
Fully supported

Free-form notes from case files migrate as Twenty Notes attached to the related People or Opportunity record. Original timestamps and author attributions are preserved in the Note record metadata. We maintain the full text content and associate each note with its parent record for complete case context accessibility.

The Attorney Case File

Custom Case Fields

maps to

Twenty CRM

Custom Field (Opportunity)

1:1
Fully supported

Any custom properties on cases in The Attorney Case File — practice area codes, referral source, conflict check status — migrate as Twenty custom fields on the Opportunity object. We create these before migration and map values by type (text, number, select, date).

The Attorney Case File

User / Attorney

maps to

Twenty CRM

Workspace Member

1:1
Fully supported

Attorneys and staff from The Attorney Case File resolve by email against Twenty workspace members. Unmatched users are flagged before migration — the team either creates their Twenty account or assigns records to a fallback user. Historical owner attribution is preserved on migrated records.

The Attorney Case File

Workflows / Automations

maps to

Twenty CRM

Not Migrated

1:1
Fully supported

The Attorney Case File's workflow rules for case status triggers, deadline reminders, and document generation templates are not transferable due to platform-specific logic. We export workflow definitions as a structured JSON reference file listing all triggers, conditions, actions, and field dependencies for manual recreation in Twenty's workflow builder by your administrator.

The Attorney Case File

Client Workbook

maps to

Twenty CRM

Note + Custom Fields

many:1
Fully supported

The client workbook aggregates case context, billing notes, and client preferences in The Attorney Case File. We strategically split this into a Note attached to the People record plus custom fields on the linked Opportunity records, preserving structured data that fits Twenty's relational model while maintaining accessibility to all historical client information.

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.

The Attorney Case File logo

The Attorney Case File gotchas

High

No public API — extraction requires vendor coordination

Medium

Export envelope is limited to workbook-level records

Medium

Trust accounting data is outside the export scope

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

  • Case-first model requires restructuring for CRM pipeline logic

    The Attorney Case File organizes all data around the case/matter as the primary record. Twenty CRM uses a contact-opportunity model where People and Companies are the anchor objects. Cases migrate as Opportunities, but The Attorney Case File's multi-party case structure — where one matter involves multiple clients, opposing counsel, and third parties — requires splitting into separate Opportunity records with linking custom fields. We flag these N-to-N cases during the sample migration and surface a mapping plan before the full run commits.

  • Billable hours have no native home in Twenty's data model

    The Attorney Case File stores time entries as first-class records with rate, date, description, and billing status. Twenty has no native time-tracking or billing object. We create a Time_Entry__c custom object linked to the Opportunity, but invoice generation, trust accounting, and LEDES billing code support require rebuilding in Twenty or connecting a legal-specific accounting tool. Firms using The Attorney Case File's billing features should plan for a 2–4 week rebuild of their billing workflow post-migration.

  • Workflow automations in The Attorney Case File do not transfer

    Case status change triggers, deadline reminder workflows, and document generation rules in The Attorney Case File are platform-specific automation logic. Twenty's workflow builder supports trigger-action sequences on People, Companies, Opportunities, and Tasks, but the migration does not convert The Attorney Case File's automation rules. We export a structured JSON reference of all workflow definitions with field names and conditions so your Twenty admin can recreate them in Twenty's workflow builder.

  • Document version history is lost in the translation

    The Attorney Case File maintains comprehensive version history for all documents attached to case files and client workbooks. When we download and re-upload documents to Twenty as file attachments, only the current or most recent version transfers successfully. If your firm relies on document version provenance for compliance, audit trails, or tracking draft-to-final contract revisions, that version history must be preserved manually or captured in the document naming convention before migration begins. We include a pre-migration checklist item specifically flagging this limitation for your team to address proactively.

  • Twenty's API rate limits vary by tier and affect bulk migration speed

    Twenty Pro tier allows 100 API calls per minute; Organization tier allows 200 per minute. For migrations exceeding 25,000 records with attachments, we batch and throttle API calls to avoid rate limit errors. The migration job includes retry logic for 429 responses and a re-queue mechanism so no records are dropped. Self-hosted Twenty instances have no API rate limit but depend on your server's capacity — we adjust batch sizes accordingly.

Migration approach

Six steps for a successful The Attorney Case File to Twenty CRM data migration

  1. Audit The Attorney Case File data and design Twenty schema

    We extract a full export of all clients, cases, documents, notes, time entries, and custom fields from The Attorney Case File. We identify record counts per object, flag multi-party cases, document custom field types and pick-list values, and assess attachment sizes. Simultaneously, we create the Twenty workspace schema: custom fields on Opportunity, the Time_Entry__c custom object, and any custom selects for practice area and billing status. We deliver a schema setup checklist so your Twenty admin can pre-create fields before the migration runs.

  2. Resolve users and attorneys by email match

    We build an email lookup table matching The Attorney Case File user accounts to Twenty workspace members. Unmatched attorneys and staff are flagged with a recommendation: invite them to Twenty first, or assign their records to a fallback owner. No case or client record lands in Twenty without an owner — we enforce this constraint throughout the migration to preserve accountability on every record.

  3. Run a sample migration with field-level diff on 100–500 records

    We run a representative sample migration covering clients, cases, time entries, documents, and notes. The field-level diff compares source values against destination field values, flags any transformation errors, and surfaces cases that require N-to-N splitting. You review the diff output and confirm case-to-Opportunity mapping, practice area values, and billing status translation before the full run commits. This step catches mapping errors before they affect your entire dataset.

  4. Execute full migration with delta-pickup window

    The full migration loads Companies first (Twenty's import order requirement), then People with company links, then Opportunities with case data and custom fields, then Time_Entry__c records linked to Opportunities, and finally documents and notes as attachments. A 24–48 hour delta pickup window runs concurrently, capturing any case updates or new clients created in The Attorney Case File during the cutover. The audit log records every insert, update, and skip so reconciliation is traceable.

  5. Reconcile, validate, and deliver rollback package

    Post-migration, we run record-count reconciliation against the source export, spot-check field values on 50 random records, and verify attachment presence on case Opportunities. If reconciliation reveals discrepancies, one-click rollback reverts the Twenty workspace to pre-migration state while The Attorney Case File remains untouched. We deliver the migration audit log, the exported workflow reference JSON, and a handoff document with field mapping decisions for your Twenty admin.

Platform deep dives

Context on both ends of the pair

The Attorney Case File logo

The Attorney Case File

Source

Strengths

  • One-time pricing with no per-user per-month recurring cost for solo practitioners
  • Intuitive interface requiring minimal training for basic case management tasks
  • Responsive customer support cited across multiple user reviews
  • Customizable workbook structure adaptable to different practice areas
  • Designed specifically for attorneys rather than repurposed from a generic CRM

Weaknesses

  • No publicly documented API for programmatic data export or integration
  • Limited document management capabilities不适合 handling large case document volumes
  • Reported instability or lack of clear development roadmap in at least one review
  • May not scale for multi-party or highly complex litigation matters
  • No dedicated trust accounting or full practice accounting module
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 The Attorney Case File 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

    The Attorney Case File: Not publicly documented.

  • Data volume sensitivity

    B

    The Attorney Case File doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your The Attorney Case File 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 The Attorney Case File to Twenty CRM data migrations

Answers to the questions buyers ask most during The Attorney Case File to Twenty CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your The Attorney Case File to Twenty CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 100,000+ records, custom case objects, or significant document attachment volume extend to 5–10 days. The schema design step (Step 1) and sample migration review (Step 3) are the longest planning components — the actual data load runs faster once those are confirmed. Timeline depends on how quickly your team reviews the sample migration diff.

Adjacent paths

Related migrations to explore

Ready when you are

Move from The Attorney Case File.
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