Migrate from Lifeline Suite to Odoo CRM

Lifeline individual constituents map directly to Odoo res.partner records with partner_type='contact'. Address, phone, and email fields transfer as-is. The constituent ID from Lifeline is stored in a custom field (x_lifeline_id) for traceability and delta-run matching. For records where the email address already exists in Odoo, the existing partner record is linked rather than duplicated to prevent data fragmentation.

Organization constituents map to res.partner with partner_type='company'. Company registry fields (name, address, phone, website) migrate as standard Odoo company fields. Parent-company hierarchies from Lifeline map to Odoo's parent_id on res.partner. Child contact records (employees) are linked via the same parent_id relationship, preserving organizational hierarchies during the migration.

Each Lifeline gift record becomes a crm.lead opportunity. The gift amount maps to Odoo's expected_revenue field. Campaign attribution from Lifeline maps to a custom campaign_id field on the opportunity. Stage assignment is based on gift status (Pledged, Received, Cancelled) mapped to Odoo pipeline stages. Recurring gift schedules are represented as separate opportunity records linked by a custom field (x_recurring_group_id) to preserve the recurring relationship.

Lifeline fund codes and campaign names map to Odoo crm.lead tags (crm.tag). Where fund codes carry financial restrictions (restricted vs. unrestricted), we preserve this as a custom selection field (fund_restriction_type) on the opportunity record. Tags are created automatically during migration if they do not already exist in your Odoo instance.

Lifeline household and spouse relationships map to Odoo's 'Related Partner' link on res.partner. We create a custom relational field (x_household_member_id) pointing to the related partner record, preserving the relationship type as a selection field. The relationship type (spouse, domestic partner, household member) is stored in a separate selection field (x_relationship_type) for reporting purposes.

Lifeline call logs, notes, and meeting records migrate as mail.message records linked to the res.partner. Original activity timestamps are preserved in the message create_date. Meeting records with duration map to crm.activity entries with activity_type_id set accordingly. Attachments associated with activities are migrated as ir.attachment records linked to the message.

Lifeline insurance carrier, policy number, and coverage type fields have no Odoo native equivalent. We create custom char and selection fields (x_insurance_carrier, x_policy_number, x_coverage_type) on res.partner for reference. These require your Odoo admin to configure field visibility via Odoo Studio. Group-based access controls can be set in Studio to restrict visibility to authorized staff members only.

Lifeline referral source codes (hospital, clinic, self-referral, etc.) map to Odoo's crm.lead source_id field via value mapping. Unmapped codes are imported as crm.tag records and linked to the opportunity for segmentation. The source_id values are created as utm.source records in Odoo, allowing campaign attribution reporting across your donor pipeline.

Any Lifeline custom fields beyond standard constituents (care program enrollment, intake date, clinical flags) are migrated as custom fields on res.partner or crm.lead depending on object scope. Field type is preserved: text to char, dates to date, selections to selection. Boolean flags from Lifeline map to boolean fields in Odoo, maintaining the original data semantics.

Lifeline export code files (EXPORT_Codes.xlsx) contain pick-list value sets for status fields, relationship types, and segment codes. These map to Odoo ir.model.fields.selection values for pick-list fields or crm.tag for open-ended tagging. The code mapping table is delivered as part of the migration package, documenting the source code and corresponding Odoo value for audit purposes.