Migrate from AgileCase to Twenty CRM

AgileCase Contacts map directly to Twenty People. Each People record stores name, email, phone, job title, and company link. Primary company link resolves via companyId reference to the migrated Companies record. Non-primary company associations are stored as custom fields or Notes for reference.

AgileCase Companies map to Twenty Companies with domain, industry, size, and location fields preserved. Parent-company hierarchies in AgileCase translate to the Companies relation model in Twenty. Multi-contact companies land with one primary contact assigned via the People.companyId field. Address information and industry classifications transfer as standard fields on the Company record.

AgileCase Cases become Twenty Opportunities — the core structural translation of this migration. Case-specific metadata (case number, case type, priority, status, assigned attorney, billing rate) migrates as custom fields on the Opportunity. The case description migrates to the Opportunity name or a custom long-text field. Case stages map to Opportunity stage values.

AgileCase case plans and automation workflows have no equivalent in Twenty's workflow model. We export the full workflow definition — triggers, conditions, action sequences, and due-date rules — as a structured JSON reference document. Your Twenty admin uses this to rebuild equivalent automations in Twenty's workflow builder or via external tools.

AgileCase email templates (10 on Professional, unlimited on Business) do not migrate. We export template names, subject lines, body content, and merge-field mappings as a CSV reference. These must be rebuilt as Twenty workflow email actions or a dedicated email template tool.

AgileCase Tasks link to Cases and Contacts and map directly to Twenty Tasks. Task subject, due date, assignee, status, and linked record (People or Company) are preserved. Tasks without a due date or assignee land with default values set during migration.

AgileCase Notes attached to Cases or Contacts migrate as Twenty Notes. Rich-text formatting is preserved where AgileCase's export format allows. Notes are linked to the corresponding People, Company, or Opportunity record via the standard relation model, maintaining full context and association from the original source system.

AgileCase file attachments on cases or contacts do not migrate via standard export. We provide a file manifest (record ID, filename, URL if accessible) so your team can re-upload files manually to Twenty or via the Twenty API. Attachments not accessible via API require manual re-upload.

Every AgileCase custom field on Cases must be pre-created in Twenty as a custom field on Opportunity before migration runs. We deliver a field-creation checklist from the AgileCase field inventory so Twenty's Data Model is ready before records land. Field types (text, number, select, multi-select) map to their Twenty equivalents.

AgileCase users are resolved to Twenty Workspace Members by email match. Unmatched users are flagged with a fallback assignee (typically the migration admin). AgileCase user roles and permissions do not transfer — Twenty roles and permissions must be configured independently post-migration.

AgileCase's 180-day audit trail (Business plan) or full audit log (Enterprise) does not migrate as a structured object. We export audit entries as a CSV and surface them as a linked Note on each record or a reference field pointing to the audit export file.

AgileCase tags and case labels map to Twenty custom fields with pick-list or multi-select types. We export the full tag vocabulary and create corresponding options in Twenty before migration so values land correctly on records. The tag-to-field mapping preserves all label hierarchies and categorization from AgileCase.