Migrate from Genoo to Odoo CRM

Genoo Leads map directly to Odoo crm.lead records with type='lead' and is_customer=False. All standard Genoo lead fields (name, email, phone, company, source) migrate as crm.lead fields (partner_name for company, email_from for email, phone for phone). We use email as the dedupe key against res.partner to prevent duplicate contact-person records. Genoo's lead creation date migrates as create_date on crm.lead for activity audit.

Genoo Contacts with known customer status map to Odoo res.partner records. Email is the dedupe key. res.partner.name maps from Genoo contact name, email from email, phone from phone. If the Genoo Contact has an associated Account, we create the corresponding res.partner as a company-type partner first (type='company') and link the contact-person partner as a child contact via parent_id.

Genoo Accounts map to Odoo res.partner with type='company'. company_name from Genoo becomes res.partner.name; website maps to website field; industry maps to industry_id (mapped to Odoo's res.partner.industry taxonomy). Accounts without a linked Contact in Genoo still migrate as company-type partners so that any Lead-to-Account association in the destination is satisfied.

Genoo Opportunities are not first-class objects; they are derived from CRM sync where the destination CRM (e.g., Salesforce) owns the Opportunity. We do not migrate Opportunity records from Genoo because Genoo does not store Opportunity data. Instead, we create the crm.lead records in Odoo from the Genoo Contact and Account with type='opportunity', stage='new', and the customer-provided pipeline stage configuration. Revenue fields and expected close date are set based on any custom fields the customer documents during discovery.

Genoo Campaigns (drip programs and nurture sequences) do not have a direct Odoo CRM equivalent because Odoo does not ship native drip nurture. We map Campaign records to Odoo CRM Tags by campaign name, and create a crm.lead.tag.rel association for each Lead that was enrolled in the campaign. This preserves the 'was in this campaign' membership data. The campaign start/end date and status migrate as custom fields on the tag record or as a migration manifest note.

Genoo Campaign membership (which Leads entered which Campaigns and when) migrates as crm.tag.rel records linking the crm.lead to the corresponding crm.tag. Enrollment date and status (active, completed, bounced) migrate as custom fields on the tag-rel record. If a Lead was in multiple campaigns, all campaign tags attach to the same crm.lead record.

We resolve Genoo Lead-to-Account associations at migration time using email domain match and explicit account_id field. If a Genoo Lead references an Account that has not yet migrated, we queue the association for a second-pass update after Account import completes. Any Lead without an associated Account in Genoo becomes a standalone crm.lead without a partner_id link.

Genoo Contacts link to Odoo crm.lead records via the partner_id field. We create the res.partner first, then create the crm.lead with partner_id pointing to the newly created res.partner record. This satisfies the Odoo foreign-key constraint and ensures the Contact's activity history attaches to the correct partner record.

Genoo landing page form submissions (name, email, phone, custom fields) do not create standard CRM records in Odoo. We import them as note activities on the crm.lead record identified by the submitted email address. The note body contains the form name, submission date, and field values as structured text. This preserves the submission data without requiring custom fields to be pre-created for every unique form.

Genoo event registrations stored as activity records linked to Leads migrate as note activities on the corresponding Odoo crm.lead. The note records the event name, registration date, registration status (registered, attended, no-show), and any custom registration fields. Post-event attendance data from Genoo migrates as a separate note entry with a different note category.

Genoo HTML email templates are extracted as structured data (subject, body HTML, styling). We preserve them as a migration manifest with template body and subject for the customer to rebuild in Odoo email marketing or a third-party tool. Odoo does not ship a native email campaign builder in the base CRM module; email template rebuild in Odoo Studio or a dedicated email marketing app is a separate step documented in the handoff.

Genoo Lead and Contact owner assignments map to Odoo res.users by email match. We extract every distinct owner referenced in Genoo and match against the destination Odoo instance's user list. Any Genoo owner without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import. Owner resolution must complete before crm.lead import to satisfy the user_id foreign key.