Migrate from CASEpeer to Twenty CRM

CASEpeer has no public API — data extraction requires the managed data transfer team

CASEpeer does not expose a REST or GraphQL API for self-service data export. Firms must engage CASEpeer's data implementation team to generate a custom CSV export matched to your destination schema. This introduces a review-and-approval cycle (Stages 1–4 in CASEpeer's data transfer process) that adds 5–10 business days to the project timeline before FlitStack receives a usable data file. We coordinate directly with CASEpeer's team on your behalf, but the export cadence is controlled by their schedule. Firms should initiate the CASEpeer data transfer request early to avoid blocking the migration start date.

Multi-party plaintiffs require a custom mapping strategy that Twenty's standard schema doesn't handle natively

Personal injury cases frequently involve multiple plaintiffs (spouses, family members, multiple defendants) each represented as a separate CASEpeer Client record linked to one Case. Twenty CRM's People-to-Companies model enforces a single primary companyId per Person record, and the Opportunity (Case) object links to one primary Person. When migrating multi-plaintiff cases, we create separate Opportunity records for each plaintiff and preserve the case grouping via a custom Parent_Case_Reference__c field. The firm's attorneys need to decide whether to consolidate all plaintiffs into one Twenty Opportunity or maintain separate Opportunity records — this decision is made during the pre-migration schema planning session.

CASEpeer Advanced tier custom intake fields need a schema design session before migration

CASEpeer Advanced tier's custom intake forms generate per-case-type field groups that are structured differently from standard CRM fields. A motor vehicle accident intake form might have 30 custom fields (impact details, vehicle information, injury specifics) while a medical malpractice form has an entirely different set. Twenty CRM supports unlimited custom fields, but each custom field must be created individually in Twenty's Settings before migration runs. The migration plan must include a schema design session that maps every CASEpeer custom intake field to a Twenty custom field, defines the field type (text, number, date, select), and identifies which Twenty object (Person or Opportunity) each field belongs to. Fields on the wrong object cause mapping failures at migration time.

Twenty's CSV import order constraint requires Companies before People before Opportunities

Twenty's import system enforces referential integrity at load time: Companies must be created before People (since People link to a companyId), and People must be created before Opportunities (since Opportunities link to People as contacts). CASEpeer does not export data in this dependency order — its export follows CASEpeer object structure. FlitStack re-sequences the CASEpeer export into Three CSV batches: Companies first (insurance carriers, medical providers, employer entities), then People (clients, contacts), then Opportunities (cases linked to the migrated people and companies). Skipping or reordering these batches causes import failures because Twenty's UI will reject Person records with invalid companyId values and Opportunity records with non-existent Person links.

Workflows, automations, and CalendarRules-driven deadline tracking do not migrate

CASEpeer automations — including case status change rules, SOL countdown alerts, intake form routing, and attorney task assignments — are stored in CASEpeer's proprietary automation engine and are not exportable as portable definition files. Twenty's workflow builder (available on Pro and Organization tiers) provides trigger-based automation but does not have a CASEpeer automation importer. FlitStack documents every CASEpeer automation as a textual specification describing the trigger condition, the rule logic, and the resulting action. The firm's admin uses this specification to rebuild automations in Twenty's workflow builder after go-live. Statute of limitations countdown reminders and court deadline CalendarRules integration must be rebuilt as Twenty Tasks with manual due dates or via a third-party calendar integration.