Migrate from RunSensible to Twenty CRM

RunSensible clients map directly to Twenty People. The primary contact name, email, phone, and address fields migrate as-is. A company linkage is created in Twenty's Companies object if the RunSensible client record contains an organization name, preserving the client-to-organization relationship.

When RunSensible clients represent law firms or corporate legal departments, their organization name, domain, industry classification, and employee count migrate to Twenty's Companies object. This enables the people-within-companies data model Twenty uses for B2B relationship tracking, preserving firm-level details while adapting to Twenty's standardized company object structure.

RunSensible matters (cases) map to Twenty Opportunities using the matter name as the opportunity name, the matter's status or practice area as the opportunity stage, and the matter's case number as a custom field. Matter-type distinctions (litigation, corporate, real estate) require a custom opportunity stage setup in Twenty to preserve this classification.

RunSensible matter statuses (Active, Pending, Closed, Archived) map to Twenty opportunity stages. Each status value requires explicit value-by-value mapping to the stage names your Twenty workspace uses. Active matters become open pipeline stages; closed matters become won or lost based on outcome in RunSensible.

RunSensible contact records for opposing counsel, partners, and third parties migrate as Twenty People. They link to the primary client Person record via Twenty's relation field. Email, phone, and role fields migrate as custom fields or standard fields where field names align.

RunSensible time entries (billable hours linked to matters) migrate as Twenty Notes with original timestamps, attorney name, and duration preserved. The note body contains the time entry description and hours logged. This preserves historical billing context without requiring a dedicated billing module in Twenty.

RunSensible documents attached to clients and matters migrate as Twenty Notes with a reference to the original file. We download the files from RunSensible's storage and re-upload them to Twenty's file storage, attaching each document to the corresponding Person or Opportunity record for complete file preservation and accessibility.

RunSensible's three-way reconciliation IOLTA trust accounting has no Twenty CRM equivalent. Trust balances, client trust records, and reconciliation history cannot migrate. We export the trust account data as a CSV reference file for your new accounting platform (Clio Manage, CosmoLex).

RunSensible statute of limitations dates on matters migrate to a custom date field (SOL_Date__c) on the corresponding Twenty Opportunity record. This preserves the critical legal deadline information and ensures your team can track filing windows without relying on a native legal construct in Twenty's standard Opportunity object.

RunSensible custom fields on client records — such as referral source, bar number, or billing arrangement — migrate to Twenty custom fields on the Person object. Field type mapping handles text, number, date, and pick-list types individually, ensuring data integrity and proper field formatting during the migration.

RunSensible custom fields on matter records — court division, assigned judge, practice area — migrate to Twenty custom fields on the Opportunity object. Multi-select pick-list values in RunSensible map to Twenty multi-select fields with the same value options, preserving all categorization and metadata across platforms.

RunSensible sequences, triggers, and email automations do not migrate. These must be rebuilt in Twenty's workflow builder (limited on Pro tier, full on Organization). We export the RunSensible workflow definitions as a JSON reference file for your Twenty admin to use as a rebuild guide.

RunSensible's native invoicing and trust accounting module has no Twenty CRM equivalent. Invoices, payments, and disbursement records cannot migrate automatically into Twenty. We export the full billing history as a CSV reference file and recommend connecting a dedicated legal accounting platform post-migration for complete financial record preservation.

RunSensible calendar events and court date reminders migrate as Twenty Tasks with the original date, time, and description preserved. Court appearance dates and filing deadlines that were scheduled in RunSensible become Tasks with due dates attached to the corresponding Opportunity, maintaining all scheduling context in the new CRM.