Migrate from ArkCase to Twenty CRM

ArkCase Persons map 1:1 to Twenty People. The Person's email, phone, job title, and address fields transfer directly. A Person's Organization relation resolves to a Twenty CompanyId — the Organization must exist in Twenty before the Person import runs. If duplicate email addresses exist across organizations, the migration flags them for manual disambiguation before inserting records into Twenty.

ArkCase Organizations map to Twenty Companies. Organization name, domain/website, industry, and address fields transfer directly. Parent-child Organization hierarchies in ArkCase map to the Companies parentId field — the parent Company must be imported before child records. When multiple organizations share the same domain, the migration records the first occurrence and marks subsequent duplicates for admin review.

ArkCase Cases do not map as a standard CRM object — they represent compliance requests, FOIA inquiries, or legal matters rather than sales deals. FlitStack AI maps Case title to Opportunity name, Case status to Opportunity stage, and Case priority to a custom Priority field. Compliance metadata (request type, litigation flag, fee waiver) migrates as custom fields.

ArkCase Tasks migrate as Twenty Tasks. Original due dates, assignees, and completion status transfer. Tasks linked to Cases map to the corresponding Opportunity record via the task's relatedId field. Unassigned tasks receive the migration fallback owner. If a task references a case that has not yet been migrated, the system queues the task for re-linkage after the Opportunity record is created.

ArkCase documents and file attachments re-upload to Twenty Files. Files are associated to the parent record (Person, Organization, or Opportunity) after import. ArkCase's ECM-integrated files may require download-and-reupload depending on ArkCase's storage configuration. File size capped at 25MB per file in Twenty.

ArkCase notes migrate as Twenty Notes attached to the relevant record. Rich-text formatting is preserved. Notes without a parent record attach to the originating Person or Organization. Note timestamps and author information transfer as custom audit fields. If note content exceeds the storage limit, the migration truncates the body and logs a warning for admin review before final import.

ArkCase categorizes cases by type (FOIA, Legal Hold, Public Records, Investigation). Twenty has no native equivalent — we create a custom select field (Request_Type__c) on the Opportunity object and map each ArkCase case type value to the corresponding pick-list option.

ArkCase tracks whether a case is under litigation hold. This boolean flag migrates as a custom checkbox field (Litigation_Hold__c) on the Opportunity object so legal and compliance teams can filter affected records in Twenty without rebuilding the flag logic. During migration, the flag's state is validated against ArkCase case status to ensure no hold information is inadvertently dropped.

ArkCase FOIA cases track fee waiver requests and expedite flags as individual checkboxes. Both migrate as custom boolean fields on the Opportunity. The fee amount field migrates as a custom currency field (Fee_Amount__c) for reporting on waiver volume post-migration. If a fee amount exceeds the currency field's limit, the migration records the value in a text field and flags the record for manual review.

ArkCase workflows built with the BPMN 2.0 engine (approval chains, escalation rules, automatic status transitions) do not transfer to Twenty. FlitStack AI exports each workflow definition as a JSON structure documenting triggers, conditions, and actions — your Twenty admin uses this as a rebuild reference in Settings → Workflows.