CRM migration

Migrate from NextChapter to Twenty CRM

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

NextChapter logo

NextChapter

Source

Twenty CRM

Destination

Twenty CRM logo

Compatibility

100%

10 of 10

objects map 1:1 between NextChapter and Twenty CRM.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

NextChapter is practice management software purpose-built for bankruptcy law firms — it tracks Chapter 7, 11, and 13 cases, debtor and creditor records, court schedules, Pacer noticing, and document automation. Twenty CRM is an open-source CRM built around People, Companies, Opportunities, Notes, and Tasks with a REST/GraphQL API and CSV import capability. The two platforms share no native object equivalents for legal-specific constructs like court dockets, case status tracks, or document-generation templates. FlitStack AI migrates what CRM-style data exists in NextChapter — debtor contact details, creditor company records, case notes, deadline tasks, and any custom fields your firm has added — into the corresponding Twenty objects. Legal workflows, Pacer integrations, and document automation templates do not transfer and must be rebuilt in Twenty or a complementary legal workflow tool. We sequence the migration: export from NextChapter via their CSV export and API, transform field types (dates, phone numbers, pick-list values), load into Twenty using their import CSV with column mapping, then validate relationships (People linked to Companies, Tasks linked to People).

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

NextChapter logo

NextChapter

What's pushing teams away

  • Limited customization of dashboard modules and case home page layouts frustrates attorneys who want more control over their workspace organization.
  • Firms on lower tiers lack access to custom fields, the debtor portal, and client texting features, creating pressure to upgrade for basic workflow needs.
  • Lack of a public API means integrations with other firm systems require workarounds or third-party middleware that NextChapter does not officially support.

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 NextChapter objects map to Twenty CRM

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

NextChapter

Case / Debtor

maps to

Twenty CRM

People

1:1
Fully supported

NextChapter debtor records (client name, email, phone, address, case role) map directly to Twenty People records. Each debtor becomes one People record. If the debtor has multiple open cases in NextChapter, all case associations are preserved as a custom field on the People record for reference.

NextChapter

Creditor

maps to

Twenty CRM

Company

1:1
Fully supported

NextChapter creditor entities are mapped to Twenty Companies because creditors are organizations, not individuals. Creditor name becomes the Company name field, while creditor address, phone, and email map to standard Company address and contact fields. This direct mapping preserves all organizational creditor data in the correct CRM object type, distinguishing them from debtor (People) records in Twenty.

NextChapter

Case

maps to

Twenty CRM

Opportunity

1:1
Fully supported

NextChapter bankruptcy Cases do not have a direct CRM equivalent in Twenty. We map them as Opportunities with a custom field Case_Type__c storing the chapter (Ch7, Ch11, Ch13). Case status (open/closed/discharged) maps to Opportunity stage via a value-mapping table. Filing date becomes the Opportunity create date; discharge date becomes a custom date field.

NextChapter

Custom Fields on Case

maps to

Twenty CRM

Custom Fields on People / Company / Opportunity

1:1
Fully supported

NextChapter allows Pro+ firms to create custom fields on Cases using SALI-standard fields or custom definitions. Each custom field is re-created as a custom field in Twenty on the target object (People for debtor fields, Company for creditor fields, Opportunity for case-level fields). Field type mapping: text→text, number→number, date→date, select→select, multi-select→multi-select.

NextChapter

Case Note / Document Note

maps to

Twenty CRM

Note

1:1
Fully supported

Free-text notes attached to a Case in NextChapter migrate as Twenty Notes linked to the corresponding Opportunity record. Original note timestamps and author attribution are preserved in Twenty's note metadata. If notes contain file attachments, the files are re-uploaded as Twenty attachments.

NextChapter

Task / Deadline

maps to

Twenty CRM

Task

1:1
Fully supported

NextChapter calendar tasks and court deadlines map to Twenty Tasks linked to the relevant Opportunity (Case). Task name, due date, assignee, and completion status transfer. Court-specific task labels (e.g., '341 Meeting', 'Discharge Date') are preserved as Task names with a custom pick-list field for deadline_type.

NextChapter

Client Portal Submission (MyChapter)

maps to

Twenty CRM

People (custom field)

1:1
Fully supported

Data submitted through NextChapter's MyChapter debtor portal (client intake questionnaire) is stored as intake responses on the Case. We extract these as custom fields on the corresponding People record in Twenty. The portal submission date is stored as a custom datetime field.

NextChapter

Time Tracking Entry

maps to

Twenty CRM

Task (custom fields)

1:1
Fully supported

NextChapter time tracking entries (billable hours logged on a Case) map to a custom object or custom fields on the linked Opportunity. Each time entry becomes a record with: date, hours, description, billing status. This preserves billable-hour history for reporting in Twenty.

NextChapter

Document / File Attachment

maps to

Twenty CRM

Twenty attachment

1:1
Fully supported

Documents and files attached to Cases in NextChapter—including petitions, schedules, court filings, and correspondence—are downloaded and re-uploaded as Twenty attachments on the matching Opportunity record. We preserve original file names, upload dates, and file sizes throughout this process. Note that Twenty's storage limits apply to uploaded attachments, and any NextChapter-specific file integrations (such as Pacer links or e-filing connections) do not transfer and must be rebuilt in Twenty using compatible tools.

NextChapter

NextChapter User / Team Member

maps to

Twenty CRM

Workspace Member

1:1
Fully supported

NextChapter user accounts are resolved by matching email addresses to Twenty Workspace Members. Any users without a matching email in Twenty are flagged for review before migration completes. NextChapter role designations (Attorney, Paralegal, Admin, and others) are preserved as a custom pick-list field on the corresponding Twenty Workspace Member record, allowing firms to maintain organizational role information in the new CRM.

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.

NextChapter logo

NextChapter gotchas

High

No public API for automated data migration

Medium

Custom fields require Pro+ or Whoa tier

Low

PACER notices are auto-filed, not manually uploaded

Medium

Time tracking gated behind Pro+ and Whoa plans

Medium

Document automation merge fields reference case field IDs

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

  • Legal case structures have no direct CRM equivalent in Twenty

    NextChapter organizes data around bankruptcy Cases (Chapter 7, 11, 13) with debtor/creditor relationships, filing status tracks, and court deadlines. Twenty's Opportunities are deal records designed for sales pipelines — they do not natively understand case chapters, discharge timelines, or court schedules. We handle this by mapping Cases to Opportunities with a Chapter__c custom field, case_status to stage via a value table, and court deadlines as Tasks with a Deadline_Type__c pick-list. You will need to decide whether to collapse multiple case types into one Opportunity type or create separate Opportunity views per chapter. This is a schema decision that should be made before migration runs so the import targets the correct configuration.

  • Custom fields must be created in Twenty before the CSV import can reference them

    NextChapter's Pro+ tier lets firms create custom fields on Cases using SALI-standard field definitions or completely custom ones. Twenty requires custom fields to exist in the workspace before records can reference them — the CSV import creates records, not fields. If your firm uses 15+ custom fields on Cases (common for firms tracking SALI codes, trust account balances, or court-specific data), all of them must be pre-created in Settings > Data Model before migration. FlitStack delivers a custom-field creation plan based on the NextChapter custom field audit so your Twenty workspace is schema-ready before data lands.

  • Creditor-to-debtor relationships require import sequencing to resolve

    NextChapter stores creditor lists per Case, with each creditor potentially appearing in multiple cases. Twenty resolves People-to-Companies via a companyId foreign key on the People record. We must import Creditors as Companies first, then import Debtors as People with the resolved companyId pointing to the matching Creditor record. If the same creditor appears in multiple Cases, the Company record is created once and referenced across all related People records. Running imports out of order produces broken relationships — our approach sequences Companies → People → Opportunities to guarantee foreign keys resolve correctly.

  • Documents and file attachments are re-uploaded, not migrated as live links

    NextChapter stores documents (petitions, schedules, correspondence) attached to Cases. Twenty stores attachments on records as uploaded files. We download each file from NextChapter and re-upload it to the corresponding Opportunity record in Twenty. Original file names, upload dates, and file sizes are preserved. However, the documents are decoupled from any NextChapter-integrated signing or Pacer links — those integrations do not exist in Twenty and must be rebuilt separately (e.g., via DocuSign or a court e-filing integration).

  • Workflows, document automation, and Pacer integration do not migrate

    NextChapter's core value — automated document generation, Pacer noticing, court deadline triggers, and client portal workflows — is built into the NextChapter application layer and has no equivalent in Twenty's CRM data model. These are not data migration problems; they are product capability gaps. We document all active NextChapter workflows and automation rules as a rebuild reference for your team. Twenty's workflow builder can replicate some task-trigger logic, but complex document automation and court API integrations require either a legal workflow tool or custom development.

Migration approach

Six steps for a successful NextChapter to Twenty CRM data migration

  1. Audit NextChapter data and design Twenty schema

    FlitStack extracts a full inventory of NextChapter objects: Cases (with chapter types), Debtors, Creditors, Documents, Custom Fields, Tasks, and Time Entries. We map each to a Twenty object and identify which custom fields need pre-creation. A schema design document is delivered showing: (a) the Twenty object each NextChapter entity maps to, (b) the custom fields to create with field types and pick-list values, and (c) the import order required to resolve foreign keys correctly.

  2. Pre-create custom fields in Twenty workspace

    Before any records are imported, your Twenty workspace administrator creates all custom fields identified during the audit. This includes Chapter__c as a select field, Case_Number__c as a text field, Discharge_Date__c as a date field, Deadline_Type__c as a select field, SSN_Last_Four__c as a text field, and any firm-specific custom fields on Cases. This step must complete before the CSV import runs because Twenty's import mechanism validates field existence during data load, preventing import failures caused by referencing non-existent fields.

  3. Export and transform NextChapter data

    We export NextChapter data via CSV export (for Cases, Debtors, Creditors) and API calls for documents and time entries. Each export is validated against the audit inventory. Field transformations applied during export: date formats aligned to Twenty's expected format (YYYY-MM-DD), phone numbers cleaned to standard format, case status values mapped to Opportunity stage values per chapter type, and multi-select custom fields expanded or concatenated as Twenty requires.

  4. Run sequenced import with field-level validation

    Imports run in this order: (1) Companies (Creditors), (2) People (Debtors linked to Companies), (3) Opportunities (Cases linked to People and Companies), (4) Tasks (deadlines linked to Opportunities), (5) Notes and attachments. After each batch, we generate a field-level diff comparing source values to destination values. We verify that foreign keys resolved (People have companyId, Opportunities have correct stage values), custom fields populated, and relationship counts match.

  5. Cut over with delta-pickup and post-migration verification

    A delta-pickup window (24–48 hours after initial import) captures any Cases, Debtors, or Creditors created or modified in NextChapter during the cutover. We verify record counts match between NextChapter and Twenty for all objects. Workspace Members are confirmed as active in Twenty. An audit log is delivered listing every record migrated, any records skipped due to validation failures, and recommended follow-up items for legal workflow rebuilding.

Platform deep dives

Context on both ends of the pair

NextChapter logo

NextChapter

Source

Strengths

  • PACER notice integration auto-files court notifications into client folders, cutting manual tracking effort and reducing fee exposure.
  • Cloud-native architecture requires no on-premise hardware and enables multi-device access for attorneys across office locations.
  • Document automation uses merge fields to autofill petitions and court forms, reducing manual data entry and errors.
  • Tiered pricing with a free trial lets small bankruptcy firms validate fit before committing to a paid plan.

Weaknesses

  • No public REST API documented for direct data migration; data export relies on the PIM export tool with limited field coverage.
  • Custom fields, debtor portal, client texting, and automated hearing scheduler are gated behind Pro+ or Whoa plan tiers.
  • Customization options for dashboard layouts and case home page modules are limited across all tiers.
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 NextChapter 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

    NextChapter: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your NextChapter 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 NextChapter to Twenty CRM data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most NextChapter-to-Twenty migrations complete in 48–72 hours of active migration time for firms with under 50,000 records across Cases, Debtors, Creditors, and Documents. The planning and schema-design phase takes 3–5 business days. Firms with extensive custom fields (15+), multiple Case types (Ch7, Ch11, Ch13 each with different field sets), or over 100,000 records extend to 7–14 days. The longest step is typically the custom-field pre-creation in Twenty and the import sequencing validation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from NextChapter.
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