Migrate from InfoTrack to Twenty CRM

InfoTrack matters are case-centric records linking parties, documents, and court filings. We map them to Twenty Opportunities (if the firm tracks case status as a sales pipeline) or to a custom Matter object (if the firm needs litigation-specific fields like court name, case number, opposing counsel, and filing deadline). The mapping decision is made during the schema planning step based on your firm's workflow.

InfoTrack party records — including plaintiffs, defendants, attorneys, witnesses, and process servers — map directly to Twenty People. We preserve the party role as a custom pick-list field (Party_Role__c) so your team can filter by role type within Twenty's list views and workflow triggers.

InfoTrack records for law firms, corporate clients, and opposing counsel organizations map directly to Twenty Companies. The company's domain is used as the unique identifier for relation mapping during CSV import, per Twenty's import documentation requiring domain for Company references. Each law firm or organization becomes a single Company record linked to all associated party People records.

InfoTrack process-serving orders include service address, attempt history, and court return status. We map these to Twenty Tasks if the firm wants basic tracking, or to a custom ServiceRequest object if the full attempt timeline, court return documents, and expense records need to be preserved. The custom object approach maintains richer context.

InfoTrack eFiling records (filing date, court, document type, filing status) do not have a direct Twenty CRM equivalent. We preserve filing metadata by attaching full eFiling details as Notes to the related Matter record, while storing key fields like court name, filing date, and filing status as custom fields on the Matter object for quick reference and reporting visibility.

InfoTrack document records with file names, types, and matter associations map to Twenty Notes attached to the corresponding Matter (Opportunity). File references are stored as URLs or file paths in the Note body. Twenty's 20,000-record export limit applies if you export Notes separately from other objects.

InfoTrack expense records track court fees, process-serving costs, and other litigation expenses billable to the client. We store expense totals as custom Number fields on the Matter object (Expense_Total__c) and attach itemized expense lists as Notes. For full expense line-item history, a custom Expense object can be created in Twenty's Data Model settings.

InfoTrack user accounts (attorneys, paralegals, admins) map to Twenty Workspace Members by email match. Your Twenty admin must invite all team members before migration — Twenty's import documentation explicitly requires users to exist before owner/assignee relations can be mapped. Unmatched InfoTrack owners are flagged for manual assignment.

InfoTrack allows firms to define custom party role types beyond the standard plaintiff/defendant/attorney set. We create a Party_Role__c pick-list field on the People object in Twenty's Data Model settings and map each unique role value. Role values are preserved exactly as they appear in InfoTrack to maintain reporting continuity.

InfoTrack's integration settings with Clio, LEAP, and Time Matters are platform-specific connection configs that have no equivalent in Twenty CRM. We export the integration configuration JSON as a reference document for your admin to use when setting up Twenty's REST/GraphQL API or webhook connections to your existing practice management system post-migration.