Migrate from SimplyConvert to Twenty CRM

SimplyConvert's Case record is the core object — it stores matter type, statute of limitations, jurisdiction, case status, assigned attorney, and intake chatbot transcript. We map Case fields into Twenty's Opportunity, creating custom fields for matter_type, statute_of_limitations, and case_status so the full matter context is searchable in Twenty's Opportunity view. Original case_create_date maps to a custom Created_Date__c field since Twenty sets its own createdAt on import.

SimplyConvert Contact records (plaintiffs, defendants, witnesses, medical providers) map directly to Twenty Person records. We preserve the contact's email, phone, address, and job title as standard Twenty Person fields. Contacts without an email receive a generated placeholder address to satisfy Twenty's uniqueness constraint, flagged for manual review post-migration.

SimplyConvert Company records (defendant firms, medical providers, employer entities) map 1:1 to Twenty Company records. Company name, domain/website, industry, address, and employee count carry over as standard Twenty Company fields. SimplyConvert parent-company hierarchies map to Twenty's Parent Company relation field.

SimplyConvert referral records track co-counsel relationships with fee-split percentages and referral-source attribution. We split this into two migrations: the referring firm maps to a Twenty Company record, and a custom Referral junction object links the referring Company to the associated Case/Opportunity with fee_terms preserved as a custom text field. FlitStack surfaces this mapping plan before the full run so your admin can decide whether to collapse co-counsel labels.

SimplyConvert file attachments on cases (pleadings, medical records, intake forms) are downloaded and re-uploaded as Notes in Twenty, with the Note body pointing to the file URL or containing a summary. Files exceeding 25MB are noted separately; your team re-uploads directly to Twenty's file storage post-migration. Inline images in chatbot transcripts are extracted and hosted as Notes.

SimplyConvert's Instant Case Evaluator chatbot stores structured conversation metadata — criteria answers, qualification score, auto-retain decision. This data migrates into a custom chatbot_summary field on the Twenty Opportunity record as a JSON-encoded string, preserving every criteria-answer pair for audit and matter-review purposes.

SimplyConvert case custom properties (BSA TDP Quantifier scores, trauma-informed flags, case-specific intake criteria) require custom field creation in Twenty before migration. We read the custom property schema via the SimplyConvert API, create matching fields in Twenty's data model via Settings → Data Model, then populate them during the data load. Select/multi-select properties map to Twenty select field types with the same option labels.

SimplyConvert users and case owners are matched to Twenty Workspace Members by email address. FlitStack generates a user-mapping table before migration — any SimplyConvert owner without a matching Twenty user is flagged and assigned to a fallback Workspace Member (default admin) so no case record lands without an owner. Original owner IDs are preserved in a custom source_owner_id field for audit trails.

SimplyConvert tracks case status transitions (Submitted → Under Review → Qualified → Retained). We preserve the full status history as a custom status_history field (JSON array with timestamp and status label) on the Twenty Opportunity. Twenty's built-in stage tracking is available but doesn't natively capture the multi-step litigation-status model that SimplyConvert uses for case intake.

SimplyConvert contact custom properties (e.g., plaintiff injury type, medical provider relationship, expert witness flag) migrate as custom fields on the Twenty Person object. Each custom property type maps to the closest Twenty field type: text fields for string values, select for enumerated choices, checkbox for boolean flags.

SimplyConvert intake playbooks, automated qualification rules, and referral routing automations are not migrated. These are exported as JSON definition files so your Twenty admin can rebuild equivalent rules in Twenty's workflow builder or via the GraphQL API. FlitStack provides a rebuild reference document mapping each SimplyConvert automation trigger to its Twenty workflow counterpart.