Migrate from Patent Hive to Odoo CRM

Hive contacts map directly to Odoo res.partner records in a straightforward one-to-one transformation. The partner record is created with type set to 'contact'. All standard fields including email address, phone number, job title, and complete address components map to their Odoo field equivalents. Record ownership is resolved by matching the Hive owner email to an existing Odoo res.users record before assignment, ensuring accurate accountability on migrated contact data.

Hive companies map to Odoo res.partner records with the partner_type field explicitly set to 'company' to distinguish them from individual contacts. The company name from Hive becomes the primary partner name field in Odoo. Domain/website, industry classification, and employee count data are stored either in Odoo native fields where available or in custom fields created specifically to capture these Hive attributes that lack direct Odoo equivalents.

Hive records in a pipeline stage map to Odoo crm.lead. Pipeline name becomes crm.team (sales team) assignment; pipeline stage maps to crm.stage via value mapping. Odoo crm.lead holds both lead and opportunity records — the distinction is preserved via a custom lifecycle_status__c field.

Hive projects with a commercial pipeline component map to both project.project (for task tracking) and crm.lead (for pipeline reporting). The link between the two is preserved via a custom project_id field on crm.lead. Pure delivery projects land in project.project only.

Hive tasks map directly to Odoo project.task records with comprehensive field preservation. The task stage, priority level, due date, assigned user, and full description text all transfer to their corresponding Odoo fields without transformation. The project.task.project_id field establishes the critical parent-child relationship linking each task to its originating project.project record. Sub-task hierarchy from Hive is preserved through the parent_id field on project.task, maintaining nested task structures within the Odoo task management structure.

Hive meetings, phone calls, and logged email activities all map to Odoo crm.activity records, with the activity_type_id field set appropriately based on the Hive activity type. Original creation timestamps, duration information for meetings and calls, the activity subject line, and full body text content are all preserved during migration. User assignment for activity records follows the standard pattern of email matching to Odoo res.users to maintain accurate ownership and accountability across the migrated activity history.

Hive notes transfer directly to Odoo note.note records with all content preserved. The note title becomes the note.name field, complete body text transfers to the body field, and the original creation timestamp from Hive is preserved in the create_date field. Tag information attached to Hive notes converts to Odoo note tags for consistent categorization. Notes without an associated parent record in Hive are created as standalone notes within the appropriate user's note channel in Odoo, ensuring no information is lost in the migration.

Files attached to contacts, companies, projects, or tasks in Hive are downloaded from the Hive file store and re-uploaded as Odoo ir.attachment records. Each attachment is properly linked to its parent Odoo record via the res_model and res_id fields, maintaining the relationship context. Original file names and MIME types are preserved throughout the process to ensure downstream retrieval and display functionality works as expected in the Odoo interface without requiring manual intervention.

Hive team members are matched to existing Odoo res.users records by email address as the unique identifier. The original name and role title from Hive are recorded in a reference field for audit purposes. However, access rights, group memberships, and sharing rules from Hive do not translate to Odoo's permission architecture and must be configured separately in Odoo post-migration to ensure appropriate security and data visibility settings are in place for all migrated users.

Any Hive custom field that lacks a native Odoo equivalent is systematically created as a custom field on the appropriate target model before migration begins. Target models include crm.lead, res.partner, project.project, and project.task. The Odoo field type is inferred from the source Hive data type: text-based Hive fields become either char or text fields depending on length, numeric fields translate to float or integer types, and date or datetime fields become date or datetime in Odoo for accurate temporal data representation.