CRM migration

Migrate from Best Case Bankruptcy to Twenty CRM

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

Best Case Bankruptcy logo

Best Case Bankruptcy

Source

Twenty CRM

Destination

Twenty CRM logo

Compatibility

100%

12 of 12

objects map 1:1 between Best Case Bankruptcy and Twenty CRM.

Complexity

BStandard

Timeline

5–10 business days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Best Case Bankruptcy is a purpose-built bankruptcy filing platform — its data model centers on debtors, creditors, schedules (A/B/C/D/E-F), Chapter 7/11/13 plan data, proof of claim filings, and OneTouch e-filing status. It does not function as a CRM; it has no opportunity pipeline, no activity timeline, and no concept of a person as a sales or relationship record. Twenty CRM is a general-purpose CRM built on PostgreSQL with standard People, Companies, and Opportunities objects plus unlimited custom objects and fields. FlitStack AI's Best Case to Twenty migration extracts every exportable record from Best Case — client contacts, creditor lists, case numbers and chapter types, filing and discharge dates, trustee assignments, means test results, and all custom schedules — and maps them into Twenty's schema. Bankruptcy case records become Opportunities; debtors and creditors become People or Company records; schedules and proof-of-claim data land as custom fields or custom objects. The migration uses Best Case's export APIs and CSV output; we handle reformatting date fields, splitting multi-line creditor addresses, and reconciling duplicate debtor records across cases. Workflows, e-filing templates, and court-noticing integrations are Best Case-specific and cannot migrate — we document them for manual rebuild in Twenty or via external automation.

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

Best Case Bankruptcy logo

Best Case Bankruptcy

What's pushing teams away

  • Compatibility issues between desktop and cloud versions cause lost documents and sync failures with court filing systems, leading to filing delays.
  • Support response times frustrate users trying to resolve urgent e-filing errors before court deadlines.
  • Best Case has changed ownership through successive acquisitions, raising concerns that cost-cutting will degrade the product quality long-term.
  • Newer feature add-ons — consumer loan management, legal noticing — are seen as unnecessary bloat by solo and small-firm practitioners.
  • Periodic form layout redesigns introduce confusion; the 2023 form updates introduced duplicate-question wording that Best Case did not clarify adequately.

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 Best Case Bankruptcy objects map to Twenty CRM

Each row shows how a Best Case Bankruptcy 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.

Best Case Bankruptcy

Debtor / Client

maps to

Twenty CRM

People

1:1
Fully supported

Best Case's debtor record maps directly to Twenty's People object. We map debtor name, email, phone, address, SSN (as a masked custom field), and employer info. Each debtor gets one People record even if they appear in multiple Chapter 7 and Chapter 13 cases — case history is linked via Opportunity records.

Best Case Bankruptcy

Creditor (individual)

maps to

Twenty CRM

People

1:1
Fully supported

Individual creditors with personal contact information map to Twenty People records. We preserve the creditor's name, mailing address, account number (as a custom field), and claim amount. Multi-case creditors may appear multiple times in Best Case; we deduplicate by name+address and surface duplicates for your review before loading.

Best Case Bankruptcy

Creditor (business)

maps to

Twenty CRM

Company

1:1
Fully supported

Business creditors with a company name and business address map to Twenty's Company object. We map company name, address, industry (where present), and any notes. The Company record then links to People records for individual contacts at that creditor entity.

Best Case Bankruptcy

Bankruptcy Case

maps to

Twenty CRM

Opportunity

1:1
Fully supported

Best Case's bankruptcy case record becomes a Twenty Opportunity. We map case number, chapter type (7/11/13), filing date, discharge date, and case status. The Opportunity StageName is derived from case status: Active Filing, Pending Trustee Review, Plan Confirmed, Discharged, or Closed. Chapter type lives as a custom Opportunity field.

Best Case Bankruptcy

Chapter 13 Plan

maps to

Twenty CRM

Custom Object (Plan)

1:1
Fully supported

Chapter 13 repayment plans have structured fields — monthly payment amount, plan length in months, trustee name, and confirmation date — that have no standard Twenty equivalent. We create a Plan custom object in Twenty and link it to the corresponding Opportunity (case record) via a lookup relationship. Your team configures the plan object fields in Twenty Settings before migration runs.

Best Case Bankruptcy

Schedule A (Real Property)

maps to

Twenty CRM

Custom Object (Real_Property)

1:1
Fully supported

Schedule A lists real property assets with property address, property type, estimated value, and exemption claim. We create a Real_Property custom object in Twenty linked to the debtor's People record and the case Opportunity. Multiple properties per case are stored as separate records with a shared case reference.

Best Case Bankruptcy

Schedule B (Personal Property)

maps to

Twenty CRM

Custom Object (Personal_Property)

1:1
Fully supported

Schedule B covers personal property assets — vehicles, bank accounts, jewelry, tools — with description and estimated value. We create a Personal_Property custom object. Each line item is a separate record linked to the debtor's People record and case Opportunity, preserving the item description and claimed exemption.

Best Case Bankruptcy

Schedule E-F (Unsecured Creditors)

maps to

Twenty CRM

Custom Object (Unsecured_Creditor_Claim)

1:1
Fully supported

Schedule E-F lists unsecured creditors and priority claims with creditor name, claim amount, and priority status. We create an Unsecured_Creditor_Claim custom object. The priority status (priority vs. general unsecured) maps to a select field. Each Schedule E-F entry is a separate record linked to the Opportunity.

Best Case Bankruptcy

Proof of Claim

maps to

Twenty CRM

Custom Object (Proof_of_Claim)

1:1
Fully supported

Proof of Claim filings include creditor name, claim amount, claim type (secured/unsecured/priority), and filing date. Best Case tracks these in a separate module. We create a Proof_of_Claim custom object in Twenty linked to the Opportunity and the creditor's People or Company record.

Best Case Bankruptcy

Means Test Result

maps to

Twenty CRM

Custom Fields on People

1:1
Fully supported

Best Case's Means Test Calculator generates a result used to determine Chapter 7 vs. Chapter 13 eligibility. We preserve the means test score, pass/fail indicator, and test date as custom fields on the debtor's People record. Original income and expense inputs are preserved in a notes field for auditor reference.

Best Case Bankruptcy

Calendar Event / Court Date

maps to

Twenty CRM

Task

1:1
Fully supported

Best Case court dates and filing deadlines become Twenty Tasks linked to the case Opportunity. We map the event title, due date, and assigned attorney. Recurring court dates (341 meeting, plan payment due dates) are created as separate Task records. PACER-synced events use the original PACER event description as the task title.

Best Case Bankruptcy

Case Note / Summary

maps to

Twenty CRM

Note

1:1
Fully supported

Best Case case summaries and internal notes map to Twenty Notes attached to the corresponding Opportunity. We preserve the note body text, author, and original create date. Notes are attached to the Opportunity record rather than the People record so the case context is primary.

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.

Best Case Bankruptcy logo

Best Case Bankruptcy gotchas

High

Software activation gate after renewal requires credit card entry

High

No public API — all exports are file-based or manual

Medium

Form version sensitivity means schedules filed in older editions may not re-file correctly

Medium

PACER calendar sync is a one-way pull, not a stored data object

Medium

e-filing authentication errors block court submissions without clear diagnostics

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

  • e-Filing status and court filing history have no native Twenty equivalent

    Best Case tracks OneTouch e-filing status, ECF submission receipts, and court docket entries as part of the case record. Twenty has no native e-filing, PACER integration, or court-docket tracking. We preserve e-filing status as a custom select field (Filed / Pending / Rejected) on the Opportunity and court docket entries as Notes attached to the Opportunity. Your team will need PACER access and a court e-filing tool (like NextChapter or direct ECF login) for ongoing filing after migration — this is not a CRM function and must be handled outside Twenty.

  • Best Case's per-case custom fields require Twenty custom object design before migration runs

    Best Case allows attorneys to create custom fields on cases beyond the standard schedules. Every such field needs a corresponding custom field or custom object in Twenty before data loads. The Twenty Data Model requires custom fields to be created in Settings before CSV import — the import process creates records, not fields. We deliver a custom object design document for your Twenty workspace based on your Best Case field inventory, and your admin creates the fields before we run the migration. Fields created mid-migration cause import errors and require a restart of the affected object.

  • Debtor-appears-in-multiple-cases collapses to one People record with linked Opportunities

    A debtor who files Chapter 7, receives a discharge, then later files Chapter 13 appears as two separate case records in Best Case. Twenty's People object does not natively store case history — the Opportunities object does. We create one People record for the debtor and link both Chapter 7 and Chapter 13 case Opportunities to it. Activity history from both cases attaches to the respective Opportunities. If Best Case stored notes or contacts on the case level that referenced prior case numbers, those cross-references are preserved as Note records on the People record.

  • Large firms exceed Twenty's 20,000-record export limit per operation

    Twenty's CSV export caps at 20,000 records per export run. A bankruptcy firm with 8,000 cases, 30,000 debtor and creditor contacts, and 50,000 schedule line items can exceed this limit in a single export pass. We handle this by chunking Best Case exports into date-range or case-type batches, mapping each batch separately, and reconciling relationship IDs across batches. The import order (Companies first, then People, then Opportunities, then custom objects) must be maintained across batches to preserve foreign key resolution.

  • Schedule attachments and court documents migrate as file references, not in-system documents

    Best Case stores PDF attachments — scanned schedules, court orders, correspondence — linked to case records. Twenty's Files feature supports file uploads but the migration pipeline moves file URLs and metadata; actual PDF re-upload to Twenty requires a separate file transfer step after the record migration. Court documents with specific naming conventions (ECF docket entry format) are preserved as Note records with the original filename and entry number so your team can locate them in the source system or re-upload them to Twenty Files manually after migration.

Migration approach

Six steps for a successful Best Case Bankruptcy to Twenty CRM data migration

  1. Audit Best Case data inventory and design Twenty schema

    FlitStack AI exports a full inventory of your Best Case records: debtors, creditors, cases by chapter type, schedules, proof-of-claim filings, and custom case fields. We cross-reference this against your active vs. closed case split and identify duplicate debtor records across cases. Simultaneously, we deliver a custom object design for your Twenty workspace — mapping every Best Case custom field to either a custom field on a standard Twenty object or a new custom object. Your admin creates the custom fields and objects in Twenty Settings → Data Model before we proceed to data export.

  2. Export and normalize Best Case data in dependency order

    We export Best Case records in the correct dependency sequence: Companies first (business creditors), then People (debtors and individual creditors), then Opportunities (cases), then custom objects (plans, schedules, proof-of-claim records). Best Case date fields are reformatted to ISO 8601. Multi-line creditor address strings are split into separate street/city/state/zip fields. Duplicate debtor records (same SSN or name across multiple cases) are flagged for your review — we apply your chosen dedup rule (most recent case by default) and create secondary Opportunity links for prior case history.

  3. Run sample migration with field-level diff

    A representative sample migrates first — typically 100–300 records spanning 3–5 active cases, including at least one Chapter 7, one Chapter 13, and one case with a proof of claim filing. We generate a field-level diff between the Best Case source and the Twenty destination for every record so you can verify that chapter type, filing date, discharge date, schedule values, and custom fields landed correctly before the full run commits.

  4. Execute full migration with delta-pickup window

    The full data set loads into Twenty with relationships preserved — People records linked to Opportunities via the Opportunity's companyId and peopleId fields; custom object records linked to the parent Opportunity. A delta-pickup window (typically 24–48 hours) captures any new cases, updated creditor records, or schedule amendments made in Best Case during the cutover. Audit log records every operation; one-click rollback reverts the full load if reconciliation identifies missing or mis-mapped records.

  5. Validate relationships and deliver reconciliation report

    After migration completes, we validate: every Opportunity has a linked People record (the debtor); every People record with a case has at least one Opportunity; custom object records are linked to the correct parent Opportunity; custom field values match the source Best Case export for a random 5% sample. We deliver a reconciliation report listing record counts by object, any records that failed validation, and the action taken for each failure.

Platform deep dives

Context on both ends of the pair

Best Case Bankruptcy logo

Best Case Bankruptcy

Source

Strengths

  • OneTouch™ e-filing has survived every court ECF transition since 2005 without a single manual re-entry requirement.
  • Built-in Means Test Calculator and Exemption Analyzer handle the most calculation-heavy portions of case prep automatically.
  • Due Diligence Reports import credit bureau data directly into forms, averaging 60 minutes of saved data entry per case.
  • PACER free-look integration and automatic court calendar sync replace a separate docket-monitoring subscription.
  • Client intake questionnaire enables fully remote initial consultations through a secure online portal.

Weaknesses

  • No publicly documented API means all data exports require file extraction, screen-scrape, or manual CSV pulls.
  • Compatibility issues between desktop and cloud versions cause document loss and court-sync failures.
  • Customer support quality is inconsistent; users report slow response times on urgent e-filing issues.
  • Frequent screen layout and form redesigns introduce friction for established users who have muscle-memory workflows.
  • Newer add-on modules (consumer loan management, legal noticing) are seen as unnecessary complexity by solo practitioners.
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. 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 Best Case Bankruptcy and Twenty CRM.

  • 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

    Best Case Bankruptcy: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Best Case Bankruptcy 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 Best Case Bankruptcy to Twenty CRM data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Best Case to Twenty migrations complete in 5–10 business days for firms with under 5,000 cases. The longest phase is usually custom object design in Twenty Settings — your admin creates the bankruptcy-specific custom objects and fields before data export begins. Firms with complex Chapter 13 plans, multiple proof-of-claim records per case, and over 10,000 total records extend to 3–5 weeks. Data export from Best Case, sample migration, and full load each run within 24–48 hours.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Best Case Bankruptcy.
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