Migrate from Jiva to Odoo CRM

Jiva Contact records (people with name, email, phone, jobtitle, address) map directly to Odoo crm.lead records. FlitStack AI maps contact name to contact_name on crm.lead, email to email_from, phone to phone, and creates a res.partner record as a side-effect when Odoo's partner linking is active. Jiva's contact type and lifecycle-stage custom fields migrate as custom selection fields on crm.lead.

Jiva Company records (name, domain, industry, employee count, annual revenue, parent_company link) map to Odoo res.partner records. Jiva's parent_company_id becomes Odoo's parent_id on res.partner. Industry pick-list values require value mapping against Odoo's pre-defined industry list. Multi-company Jiva setups require careful sequencing: parent companies migrate before subsidiaries so parent_id resolves correctly.

Jiva Deal records map to Odoo crm.lead but the routing depends on Jiva's deal status field: Deals marked as 'Open' or 'Working' land in Odoo as crm.lead with stage_id set to the first pipeline stage; Deals marked as 'Closed Won' or 'Closed Lost' set the stage accordingly and preserve amount in planned_revenue. The Jiva dealname becomes the crm.lead name field; amount maps to planned_revenue.

Jiva Care Plan records (care_plan_id, plan_status, enrollment_date, provider_id) have no direct Odoo CRM equivalent. We map these as custom fields on crm.lead: x_care_plan_id (char), x_plan_status (selection), x_enrollment_date (date), x_provider_id (char). The relationship between Jiva's Care Plan and Contact/Deal is preserved as notes in a dedicated custom text field for reference.

Jiva call engagement records (call_date, duration, direction, outcome, owner) map to Odoo mail.activity with type='call'. The call_date maps to create_date, duration stored in a custom x_call_duration (char) field as 'HH:MM:SS', direction stored in x_call_direction (selection), and outcome in x_call_outcome (char). Owner resolved by email match to Odoo res.users.

Jiva email engagement records (email_date, subject, body, to_address, from_address, owner) map to Odoo mail.activity (type='email') with the email subject stored in the activity's note field and a mail.message record created for the full email body. Original timestamps preserved via create_date. Bcc and thread_id fields from Jiva are stored as custom char fields for email continuity.

Jiva meeting records (meeting_date, duration, subject, location, attendees) map to Odoo calendar.event. The meeting subject becomes the event name, start_date maps to start, duration converted to end, and location stored in location. Attendee emails resolved to Odoo res.partner records and added to calendar.event partner_ids.

Jiva file attachments on any record (filename, MIME type, download_url, attached_to_object, owner) map to Odoo ir.attachment. The res_model set to 'crm.lead', res_id set to the migrated lead ID. Odoo's ir.attachment uses a database or filestore path; files are re-uploaded via Odoo XML-RPC binary write. Filename preserved in the name field for user recognition.

Jiva owner_id fields on Contacts, Companies, and Deals resolve by email match against Odoo res.users. Unmatched owners are flagged before migration; their records can be assigned to a designated fallback user or the Odoo admin. Jiva's full user list is exported first and a user-resolution table produced as part of the migration plan.

Jiva custom fields beyond standard CRM objects (healthcare-specific pick-lists, multi-select arrays, calculated fields) are enumerated during discovery and mapped to Odoo custom fields via Settings > Technical > Models. Field types are matched: Jiva date fields become Odoo date fields, Jiva pick-lists become Odoo selection fields, Jiva multi-selects become Odoo char or many2many depending on structure. Custom field labels are preserved from Jiva's field labels.

Jiva workflow rules, care-plan triggers, and sequence automations built in Jiva's workflow engine cannot migrate to Odoo CRM. These are exported as configuration documentation listing rule names, trigger conditions, and action definitions. Odoo Studio, server actions, and automated actions provide the rebuild surface. FlitStack AI delivers a Workflow Rebuild Reference document alongside the migration output.

Jiva tags applied to Contacts, Companies, and Deals are extracted and migrated to Odoo crm.tag records. FlitStack deduplicates the tag list during extraction and bulk-inserts the unique tags into crm.tag before any leads import. During lead migration, tags are linked to crm.lead via the crm.lead.res_partner_crm_tag_rel many-to-many association table, preserving the original tagging relationships from Jiva across all three object types.