Migrate from Thryv to Odoo CRM

Thryv Clients map to Odoo res.partner with company_type = 'person'. Standard fields (name, email, phone, street, city, state, zip, country) migrate directly. Mobile phone maps to partner.mobile. We preserve all Thryv custom field values as x_thryv_ prefixed custom fields on res.partner. Tag assignments migrate via res.partner.category_id many2many after tag normalization. Thryv Client IDs are stored in x_thryv_client_id for dedupe validation on subsequent delta migrations.

Thryv's flat Company structure (separate from Client) maps to Odoo res.partner with company_type = 'company'. The company contact becomes the parent partner, and any Thryv Company address fields map to child res.partner records with parent_id pointing to the company partner. This reconstructs the Odoo hierarchical address model where individual contacts at the same company share a parent. We use the Thryv Company ID as x_thryv_company_id on the parent partner for reconciliation.

Thryv Clients can be associated with Companies via a relationship field. In Odoo, res.partner.parent_id carries this association. We extract the client-company linkage from Thryv's relationship table during data profiling, resolve the parent Thryv Company to its migrated res.partner ID, and write parent_id on each client partner during migration. Clients without an associated Company have no parent_id set (they remain standalone contacts).

Thryv Opportunities map to Odoo crm.lead records with type = 'opportunity'. The Thryv pipeline stage names map to Odoo stage_id values via a stage-mapping table we create during scoping. Deal value, expected close date, and probability migrate to Odoo's expected_revenue, date_deadline, and probability fields. Owner assignment uses email-based User lookup against res.users.

Thryv custom pipeline stages map to Odoo crm.stage records within the relevant team. We preserve Thryv stage order (sequence) and probability percentages. Lost reasons from Thryv custom fields map to Odoo's lost_reason_id if the crm_lost_reason module is installed; otherwise they become a note on the crm.lead record.

Thryv Appointments map to Odoo calendar.event with start (date + time), stop (calculated from duration), duration, and name preserved. The assigned staff member resolves to an Odoo res.users record by email. Attendee contacts resolve to calendar.attendee records linked to the event. Recurring appointment series are flattened into individual calendar.event records during migration because Odoo handles recurring events via calendar.recurrence rather than as a series reference.

Thryv Invoices map to Odoo account.move with move_type = 'out_invoice' for sent invoices. Line items migrate to account.move.line records with product, quantity, price_unit, and tax handling. Thryv payment status (paid, unpaid, partial) maps to Odoo payment_state. Because Odoo requires a Journal configured for invoicing, we create or identify the appropriate sales journal during schema setup. Invoice PDFs are stored as Odoo ir.attachment linked to the account.move record.

Thryv Invoice line items map to Odoo account.move.line with product_id resolved to an Odoo product.product record. If the Thryv product name does not match an existing Odoo product, we create a minimal product.product placeholder during migration so line item references are intact. Discount amounts and tax codes from Thryv map to discount and tax_ids on the Odoo line.

Thryv freeform tags on Client records are collected, deduplicated, and normalized into Odoo res.partner.category records during a pre-migration tag audit. Each unique Thryv tag becomes a category with the original tag name as name. During Client migration, res.partner.category_id is populated via the res.partner.category_id many2many relation. Tags with duplicate names (case variations, plural/singular) are merged into a single category during normalization.

Thryv custom fields migrate to Odoo custom fields on res.partner (for Client/Company fields) or crm.lead (for Opportunity fields). Field types are matched: Thryv text fields become char, long text become text, date fields become date, number fields become float or integer. We check Odoo edition limits during schema design; Odoo does not impose a field count ceiling at the level Thryv does (100 Pro, 150 Max), so custom field migration is not constrained by edition on the Odoo side.

Thryv User records (staff and owners) map to Odoo res.users via email match. The customer's Odoo admin provisions res.users before migration begins. We flag any Thryv Owner referenced on Opportunities who has no matching res.users in the reconciliation queue and hold Opportunity migration for those records until the admin provisions the user or reassigns the Owner.

Thryv Email and SMS communication logs (available on Keap tier) migrate to Odoo mail.message records linked to the res.partner via model = 'res.partner' and res_id pointing to the partner ID. Message body, direction (inbound/outbound), and timestamp migrate. Thryv's SMS thread structure maps to separate mail.message records within the same thread grouped by subject or conversation ID.

Thryv Marketing Center social posts are exported as mail.message records with a custom subtype and platform metadata (Facebook, Instagram, etc.) stored in extra fields. The post content, scheduling metadata, and performance metrics (likes, shares, impressions) migrate as structured fields on the message record. Platform-native posts are not recreated in Odoo; content is delivered as a data record for manual reposting.

Thryv website form submissions are mapped to Odoo crm.lead with type = 'lead'. Form field data populates lead name (from submitted name field), contact_email, contact_phone, and any custom field values. The form submission date becomes the lead create_date. These records land in the Odoo CRM pipeline for follow-up rather than as partner records, preserving the lead qualification workflow.