Migrate from Traffic Ticket CRM to Twenty CRM

Traffic Ticket CRM's Client record migrates directly to Twenty's People object. Client fields — name, email, phone, address, and attorney assignment — map to corresponding Twenty fields. Original Traffic Ticket client IDs are preserved in a custom Source_ID__c field for traceability and delta-run de-duplication.

Traffic Ticket CRM's Contact object (for opposing counsel, court contacts, or witnesses) maps directly to Twenty's People object. Email, phone, and role fields migrate as custom select fields since Twenty People has no native contact-role concept beyond the relationship to Company records.

Traffic Ticket CRM's Company record migrates directly to Twenty's Companies object. Company name, domain, industry, and address fields map to corresponding Twenty fields. A custom CourtJurisdiction__c text field on Companies captures the court location associated with the firm's address for legal-specific reporting.

Traffic Ticket CRM's Case object maps to Twenty's Opportunity. Because Twenty has no native legal case object, all case-level fields — violation type, fine amount, court date, bond status, traffic points, ALR status — migrate as custom fields (CaseViolationType__c, FineAmount__c, CourtDate__c, BondStatus__c, TrafficPoints__c, ALRStatus__c) on the Opportunity record. The Opportunity StageName field maps to case status pick-list values from Traffic Ticket CRM's disposition tracking.

Traffic Ticket CRM document records — PDFs, scanned citations, court notices — migrate as Twenty Notes attached to the corresponding People or Opportunity record. We re-upload files via Twenty's attachment API. Large documents are batched to respect file-size limits. Each document's title, type, and original Traffic Ticket metadata are preserved as custom fields.

Traffic Ticket CRM's activity records (calls, emails, court appearances, status updates) migrate as Twenty Tasks. Each Task links to the corresponding People or Opportunity record. Original timestamps, owners, and activity type (call, email, meeting) are preserved as custom fields on the Task record.

Traffic Ticket CRM's court-data-based lead records map to a Twenty custom object named CourtLead. Court fields — ticket number, issuing officer, court location, violation code — become custom fields on the CourtLead object. Custom object relationships to People and Companies are recreated as Twenty relation fields.

Traffic Ticket CRM mailer campaign records migrate as a Twenty custom object named MailerCampaign. Campaign metadata — mailer type, send date, court target, response rate — migrates as custom fields. Because Twenty has no native mailer feature, this data is preserved for reference and reporting, but outreach automation must be rebuilt using Twenty's workflow builder or API.

Traffic Ticket CRM automation rules do not have a direct equivalent in Twenty and cannot be migrated programmatically. We export your rule definitions as a structured JSON document so your Twenty admin can reference them when recreating automations in Twenty's workflow builder. Rule logic — triggers, conditions, and actions — must be rebuilt manually.

Traffic Ticket CRM's invoicing and trust accounting records have no native equivalent in Twenty's standard objects. These migrate as a custom object named ClientInvoice with fields for invoice number, amount, status, and payment date. Trust account balances migrate to a TrustBalance__c custom field on the People record.