Migrate from Jiva to Pipedrive

Jiva Member records map directly to Pipedrive People. Each Member's name, contact details, date of birth, and member ID transfer as Person fields. Custom clinical fields on the Member record (diagnosis flags, care tier, payer ID) migrate as Pipedrive custom fields on the Person entity. Pipedrive's Person has no native HIPAA compliance model — this must be addressed outside the CRM for any protected health information.

Jiva's provider-linked Member associations require a two-step map: the Provider becomes a Pipedrive Organization record first, then the Member becomes a Person linked to that Organization via the Person's Org relationship field. If a Member has multiple providers, the primary (most recently active) provider becomes the primary Organization; additional providers are linked via Pipedrive's secondary organization association.

Jiva Provider records (clinicians, facilities, care teams) map to Pipedrive Organizations. Provider name, specialty, NPI number, address, and contact information transfer to standard Organization fields. Custom fields for provider type (MD, NP, Facility, DME) and network status migrate as Pipedrive Organization custom fields. Provider-to-Member relationships are preserved as Person-Organization links.

Jiva Care Episodes are the primary object migrating to Pipedrive Deals. Each episode becomes one Deal, with the Member (Person) linked via the Deal's Person relationship. Episode status (Intake, Assessment, Authorization, Active Care, Discharge) maps to a dedicated Pipedrive Pipeline named 'Care Episodes' with matching stage names. Episode date fields (start date, authorization end date) transfer to Deal expected_close_date and custom date fields. Authorization number and payer information migrate as Deal custom fields.

Jiva records the full stage-transition history of a care episode with timestamps. Pipedrive Deals natively track stage changes, but Jiva's custom stage timestamps (e.g., Assessment entered 2024-03-15 09:30) need preservation as custom datetime fields on the Deal (e.g., Intake_Entered__c, Assessment_Entered__c). We create these fields during schema setup and populate from Jiva's episode audit log.

Jiva Authorizations can exist as standalone records or as sub-records of a Care Episode. In Pipedrive, each Authorization's key fields — auth number, authorized units, utilization remaining, payer ID, authorization type — merge into the parent Deal's custom fields. If an Authorization is not linked to a specific episode, it becomes a standalone Deal in a separate 'Authorizations' Pipeline.

Jiva Care Plans are complex clinical documents containing goals, interventions, and progress notes. We extract the care plan summary and goals list as a Pipedrive Note attached to the related Deal (episode), and key plan fields (plan type, review frequency, care manager assignment) as Deal custom fields. The full care-plan clinical document is exported as a file attachment and re-uploaded to the Deal's activity feed.

Jiva clinical assessments (PHQ-9, SDOH screens, functional status) are stored as structured records. We map the assessment type, score, and date as custom fields on the related Deal. The assessment narrative and clinical notes migrate as a Pipedrive Note attached to the Deal. Long-form assessment responses are exported as files and attached to the Deal's activity feed.

Jiva care team member assignments (Care Manager, Support Specialist, Authorizing Clinician) per episode map to Pipedrive Deal owner assignment. We resolve each Jiva care team member by email against Pipedrive users. Unmatched team members are flagged before migration; their records are assigned to a designated fallback Pipedrive user until new accounts are provisioned.

Jiva care notes, clinical documentation timestamps, and communication logs map to Pipedrive Activities (tasks with type = 'call', 'meeting', or 'email') and Pipedrive Notes attached to the related Person or Deal. Original timestamps and assigned care-team owners are preserved. Large clinical note attachments are exported from Jiva's file store and re-uploaded as Deal or Person file attachments in Pipedrive.

Jiva payers, benefit configurations, and network tiers stored as custom objects in Jiva map to Pipedrive Organization custom fields on the provider Organization record. We create payer-specific custom fields (Payer_ID__c, Benefit_Tier__c, Network_Status__c) on the Organization entity and populate from Jiva's payer configuration records.