Migrate from Virtual Case Management to Twenty CRM

VCM Client maps directly to Twenty People. The Client record's name, date of birth, contact fields, address, and demographics move to the corresponding Twenty People fields. Client IDs are stored as Source_System_ID__c on the People record for traceability and delta-run de-duplication.

VCM Case maps to Twenty Opportunity. The case enrollment date becomes the Opportunity CreatedAt timestamp; case discharge date maps to a custom Close_Date__c field since Twenty Opportunities represent deal closure rather than case resolution. Case status (Active, Discharged, etc.) maps to a custom pick-list field (Case_Status__c) on the Opportunity.

If your VCM workflow requires per-case enrollment tracking with program codes and referral sources that don't fit the Opportunity model, we create a custom Case__c object in Twenty (Pro and Organization tiers support unlimited custom objects) and link it to the People record via a relation field. This approach preserves the full case hierarchy but requires Twenty-side schema setup before migration.

VCM service records (date, service type, duration, staff member, units) have no Twenty native equivalent. We create a Service_History__c custom object with fields for Service_Date, Service_Type, Duration_Minutes, Staff_Member, and Units. Each service record links to the parent People record via a relation field.

Referrals with simple referring-agency and referral-date data migrate as custom fields on the Opportunity (Referring_Agency__c, Referral_Date__c, Referral_Outcome__c). Complex referrals with multiple referral contacts and interaction history get a custom Referral__c junction object linked to both the People and Company records.

VCM case notes migrate as Twenty Notes attached to the relevant People record (for client-level notes) or Opportunity record (for case-level notes). Original author, created date, and note-category metadata are preserved in custom fields on the Note object. Rich-text formatting in VCM notes is flattened to plain text to ensure compatibility with Twenty's Note body field, and file attachments on case notes are re-uploaded as Twenty Files linked to the same parent record.

VCM agencies and service providers map to Twenty Companies. Agency name becomes Company Name; agency type, service categories, and address data map to the corresponding Company fields. The agency's relationship to multiple clients (N:N in VCM) is resolved by creating one Company per agency and linking it to each relevant People record via the Company relation.

VCM case workers map to Twenty Workspace Members. We match VCM staff by email address to Twenty workspace invitees. Caseload assignments (which clients a worker is assigned to) migrate as a custom People custom field (Primary_Case_Worker__c) on the People record. If a VCM staff member has no matching Twenty account, they are flagged for manual workspace invite before migration.

VCM file attachments re-upload to Twenty Files linked to the parent People, Opportunity, or custom Case__c record. File category metadata (intake form, consent document, service log) migrates as custom text fields on the file. File size limits per Twenty storage configuration apply.

VCM program codes (e.g., Emergency Shelter, Food Pantry, Case Management) are pick-list values in VCM. We map each program code to a corresponding custom pick-list value in Twenty's Service_Type__c or Program_Code__c field. Unmapped program codes are flagged for manual value creation in Settings → Data Model before migration.

VCM workflows — enrollment triggers, service-reminder automations, case-update notifications — have no Twenty CRM equivalent and do not migrate. FlitStack AI exports the workflow definitions as a JSON reference document for your Twenty admin to rebuild using Twenty Workflows (available on Pro and Organization tiers).

VCM reports on enrollment rates, service-delivery metrics, and client outcomes do not transfer to Twenty. The underlying data (People, Opportunities, custom Case__c, Service_History__c) migrates and becomes available for Twenty views and API-based reporting. Your team builds new reports in Twenty from the migrated data.