Migrate from Jiva to Twenty CRM

Jiva stores individuals (patients, members, caregivers) as custom objects with healthcare-specific fields like coverage tier, member ID, and care coordinator assignment. We map these to Twenty's People object, creating custom fields for every Jiva property that has no standard Twenty equivalent. Original Jiva record IDs are preserved in Source_System_ID__c for traceability.

Jiva's provider or facility records (hospitals, clinics, payers) map directly to Twenty's Companies object. Provider type, network affiliation, and state licensing fields migrate as custom fields on the Company record. Parent-child hierarchies in Jiva map to the Parent Company relation in Twenty.

Jiva care plans contain clinical goals, intervention schedules, and outcome tracking that have no standard CRM equivalent. We create a Care_Plan__c custom object in Twenty and map plan status, start date, goal descriptions, and assigned care coordinator. Linking to People (member) and Company (facility) requires creating the relations before this object is imported.

Jiva authorization records track approval status, authorized service types, and payer responses. These map to a custom Authorization__c object in Twenty with fields for auth number, status, service type, authorized units, and expiration date. Payer name links to the corresponding Company record.

Jiva clinical assessments contain scoring data, risk categorizations, and screening results stored as custom fields on custom objects. We create an Assessment__c custom object, mapping assessment type, score, risk level, and assessment date. Links to the member's People record preserve the relationship.

Jiva encounter records (office visits, telehealth sessions, home visits) map to Twenty Tasks with Type='Encounter'. Original encounter date, visit type, provider name, and encounter outcome migrate as task custom fields. The task links to the member's People record and the facility's Company record.

Jiva staff assignments (care coordinators, case managers) resolve by email match to Twenty Workspace Members. We flag any Jiva staff without a matching Twenty user before migration and surface them in a resolution report so your admin can invite or create the user first.

Free-text notes on Jiva records (clinical notes, care summaries) migrate as Twenty Notes attached to the corresponding People or custom object record. Original creation timestamp and author are preserved. Rich-text formatting is flattened to plain text to match Twenty's Note field constraints.

Jiva payer organization records map to Twenty Companies with company type set to 'Payer' via a custom pick-list field. Payer-specific properties (contracted plans, payer ID) migrate as custom fields. These are distinct from provider organizations and are kept separate for reporting clarity.

Jiva action items and follow-up tasks map directly to Twenty Tasks with the original due date, assignee, status, and description preserved. Tasks that are linked to a specific care plan carry a custom field reference to the migrated Care_Plan__c record ID.

Jiva file attachments on care records cannot be directly re-hosted in Twenty's file storage. We download attachments, re-upload them to Twenty's built-in storage, and create a link record (custom field) pointing from the People or custom object to the new file. Large file size limits apply — documents exceeding 25MB require manual handling.

Jiva integrations with EHR systems, payer clearinghouses, and pharmacy networks have no direct equivalent in Twenty CRM. These connections must be rebuilt separately using Twenty's REST API or GraphQL endpoints. We provide a connection inventory as part of the migration package so your technical team knows exactly which integrations need rebuilding.