Migrate from Higher Logic Thrive to Odoo CRM

Higher Logic Thrive Contacts and Members map directly to Odoo CRM Contacts. We export name, email, phone, address, and all demographic custom fields up to the 30-field Thrive limit. In Odoo we map these to the standard contact fields plus res.partner custom fields created during schema setup. Member status (active, expired, pending) does not have a native Odoo equivalent—we map it to a custom Contact Status picklist field and optionally to a Partner Tags field for segmentation. Odoo's address fields follow a structured model (street, street2, city, state, zip, country) that we populate from Thrive's flat or nested address format during transformation.

Higher Logic Thrive Community Groups serve two roles: membership access control (which maps to Odoo Partner Tags) and content organization (which maps to Odoo Project records). We determine the split during scoping based on whether the group is primarily a discussion container or an access-control entity. Groups with active discussion posts, libraries, or events become Odoo Project records with the Project Tasks module enabled. Groups used purely for membership segmentation become Odoo Tags on the Contact record. We preserve the group's description, member count, and creation date as project description fields or tag metadata.

Higher Logic Thrive Security Groups (Authenticated, IsMember, Public, Staff, and custom groups) control content visibility. Odoo does not have an equivalent permission group model for community content access. We map Security Groups to Odoo Partner Tags for visibility filtering (contacts tagged with the group name can be targeted in marketing or filtered in reports). If the customer uses Odoo Portal for external member access, we configure Portal Access Rights separately using Odoo's Access Rights management under Settings > Users > Access Rights. The higherlogic_key and legacy_key identifiers from Thrive export are preserved in custom fields for audit.

Higher Logic Thrive discussion threads map to Odoo Project Tasks. Each top-level discussion post becomes a Task; reply posts become Task descriptions or sub-tasks depending on thread depth. We preserve post body as Task description (Odoo supports HTML in descriptions), author as Task assigned_to (resolved by email to Odoo Contact), timestamps as Task create_date and write_date, and @mentions and #hashtags as plain text with the mention preserved as a reference note. Large threads exceeding Odoo's Task description length are split across sub-tasks. The parent Community Group maps to the Task's Project reference.

Higher Logic Thrive Resource Library entries (documents and media files) map to Odoo IrAttachment records. The file directory with full paths from Thrive determines the Odoo storage location. Each library entry is linked to its parent Community Group (via Project) or to a Contact record depending on whether the resource is community-wide or user-specific. We verify path integrity during import scoping and re-link attachments to parent records by resolving the file path to the corresponding Odoo record ID at migration time.

Higher Logic Thrive Events with registrations and attendance tracking map to Odoo Calendar Events. We export event name, start/end datetime, location, description, and registration records. Registrations become Odoo Calendar Event attendee records linked by email to Odoo Contacts. Attendance status (registered, attended, no-show) migrates to a custom Event Attendance Status field on the attendee record. Recurring events require Odoo Calendar module extension for recurrence rules.

Higher Logic Thrive marketing campaigns with message content, send history, and trigger logic do not have a direct Odoo CRM equivalent. The Odoo Marketing Automation app (a separate paid module) provides campaign-building capabilities, but it is not part of the base CRM module. We export campaign structure, audience segments, and message content as a structured dataset. Trigger conditions and automation workflows require manual rebuild in Odoo Marketing Automation or through Odoo Studio automations post-migration. We deliver a written campaign inventory documenting every Thrive campaign with its trigger logic, audience criteria, and message sequence.

Higher Logic Thrive landing pages with form fields do not migrate to Odoo CRM. Odoo does not have a native landing page builder in the CRM module. We export landing page URL, form field definitions (mapped to Custom Fields), and submission records as contact data. Landing page rebuild options include Odoo Website builder (if the customer licenses it), third-party forms linked via API, or manual record creation for historical submissions.

Higher Logic Thrive's 30 Custom Fields per account map to Odoo custom fields on the res.partner model. We pre-create every Thrive Custom Field definition as an Odoo custom field (Char, Integer, Float, Selection, Many2one, etc.) during schema setup, matching the field type from Thrive's export schema. The Custom Field limit in Thrive means we are unlikely to encounter more than 30 fields; Odoo's unlimited custom fields mean there is no destination-side constraint. Values are re-evaluated at migration time against the migrated contact record.

Higher Logic Thrive User Lists and Segments built with List Builder criteria do not migrate as active lists. We export list definitions (name, criteria logic, member count) and map them to Odoo Partner Tags (for static lists) or Odoo Saved Filters (for dynamic lists based on field criteria). The customer chooses the strategy during scoping. Active list membership is resolved at migration time: contacts in a Thrive list receive the corresponding Odoo Tag.

Higher Logic Thrive pre-built reports with configurable columns export to XLS but do not migrate as report definitions. We capture report exports as structured datasets. Odoo reporting equivalents include the native Reporting menu under CRM (pipeline, win/loss, activity analysis) and Odoo Spreadsheet for custom analytics. Custom report definitions must be manually recreated in Odoo using the Reporting module or Studio. We deliver a report inventory listing every Thrive report with its column configuration and filter criteria.

Files attached to discussion posts, library items, and user profiles in Higher Logic Thrive map to Odoo IrAttachment records. We require a file directory with full paths per object from the Thrive export. Path integrity is verified during import scoping, and attachments are re-linked to parent records (Project Task for discussions, Contact for profile attachments) by resolving the file path to the corresponding Odoo record ID at migration time. Inline images embedded in discussion post bodies migrate as ContentDocument records attached to the parent Task.