Migrate from Prophet CRM to Odoo CRM

Prophet Company records map to Odoo res.partner records with is_company=True. Standard fields (name, street, city, state, country, phone, website, industry, employee_count, annual_revenue) map to their Odoo partner equivalents. The industry classification from Prophet maps to partner.category_id as tags if the customer's Prophet industry list is a picklist; otherwise it maps to a custom field x_prophet_industry. Company records are inserted first in the migration sequence so that Contact imports can resolve the parent company_id lookup.

Prophet Contact records map to Odoo res.partner with is_company=False and parent_id pointing to the mapped Company partner. We freeze the Outlook bidirectional contact sync before extraction and re-enable it post-import to prevent duplicates. The Prophet contact email address is used as the Odoo partner dedupe key. Prophet contact title, phone, mobile, function (job title), and address fields map to their Odoo equivalents. Owner (assigned rep) maps to Odoo user_id via email match against Odoo res.users.

Prophet Opportunity records map to Odoo crm.lead with type='opportunity'. The opportunity name maps to Odoo name, expected_revenue maps to planned_revenue, close_date maps to date_deadline, probability maps to probability, and description maps to description. Stage assignments migrate as stage_id by resolving the Prophet stage name against the Odoo stage sequence. Prophet owner maps to Odoo user_id via email match. Pipeline stage values are captured during scoping and pre-created in Odoo as stage records within the relevant team before migration begins.

Prophet pipeline stages are configurable per department, meaning stage names vary across organizations and across Prophet departments. We capture the full stage list during the scoping audit (including per-department stage variations), create each stage as an Odoo crm.stage record within the customer's pipeline, and map the stage probabilities to Odoo probability percentages. Stage ordering is preserved by setting the Odoo sequence field. If Prophet stages are department-scoped, we assign the relevant Odoo crm.team to each stage record.

Prophet departments are a first-class concept with custom field templates and configurable cross-department read/write access. We map each Prophet department to an Odoo crm.team record. Department assignments on records (Contact.owner_department, Opportunity.department) migrate as the Odoo team_id reference. Team members (users in the Prophet department) map to crm.team.member_ids via Odoo user_id email match. Custom field schema variations per department require the custom field audit step before migration to ensure all department-specific fields are represented in Odoo.

Prophet email tracking engagements (sent emails, tracked opens and clicks) map to Odoo mail.message records with message_type='email'. The message is linked to the parent crm.lead (Opportunity) and/or the related partner record via res_model='crm.lead' and res_id pointing to the migrated opportunity ID. Email body and subject transfer to body and subject fields. We do not migrate the full email thread chain as separate messages unless the customer specifically requests thread reconstruction; Prophet's OData export provides individual engagement records per email.

Prophet call log engagements map to Odoo crm.phone.call records if the Odoo instance has the crm_phone module installed; otherwise they map to mail.activity records with activity_type='call'. Call duration, disposition (outcome), and direction (inbound/outbound) transfer to call_duration, disposition, and direction fields on crm.phone.call, or to custom fields on mail.activity. The related partner and opportunity are linked via res_model and res_id on the record.

Prophet appointment engagements map to Odoo calendar.event records. Start and end datetime preserve from Prophet, location transfers to location, and meeting title transfers to name. Attendees resolve by email match to Odoo res.partner records for contacts and crm.lead records for opportunities. If the Odoo instance has the calendar_sms or calendar module installed, the meeting links to the CRM record via calendar.event.res_id and res_model.

Prophet task engagements (follow-up tasks) map to Odoo mail.activity records. Task subject maps to activity_type_id (or a custom activity type if the customer has configured one), due date maps to date_deadline, priority maps to priority, and outcome maps to a custom result field or note. Assignment (owner) resolves via email match to Odoo user_id. Activities are inserted after their parent Contact, Company, and Opportunity records to satisfy the res_model and res_id foreign key.

Prophet custom fields on Companies, Contacts, and Opportunities (plus department-template-scoped fields) require a mandatory pre-migration audit. We enumerate every custom field name, data type, and which departments use which templates. In Odoo, custom fields are created via Odoo Studio or as Python-defined fields in a custom module. Field types map: Prophet text to Odoo char or text, Prophet number to Odoo float or integer, Prophet date to Odoo date, Prophet picklist to Odoo selection or many2one, and Prophet boolean to Odoo boolean. Department-scoped fields that do not appear in the default view are explicitly included in the export and created as custom fields in Odoo before import.

Prophet file attachments on Companies, Contacts, and Opportunities are extracted from the OData export as attachment metadata (filename, URL, mime_type, size) and stored in Odoo ir.attachment records linked via res_model and res_id to the migrated partner or crm.lead record. The actual file content is downloaded from Prophet's attachment URLs and uploaded to Odoo via xmlrpc/2/object using base64 encoding. If the attachment URL is inaccessible (expired token or deleted file), we record the attachment name and URL in a custom migration_notes field on the record for manual retrieval.

Prophet Owner (assigned rep) on Contact, Company, and Opportunity records resolves by email match against the Odoo res.users table. We extract every distinct Prophet owner referenced on records during scoping, match each by email, and provision any missing Odoo users into a reconciliation queue for the customer to resolve before migration. Active owners must have a matching Odoo user before record import proceeds because user_id is a required foreign key on crm.lead in Odoo.

Prophet notes (free-text entries not tied to an engagement type) map to Odoo note.note records. The note body migrates as the Odoo note's content field. Notes linked to specific Contact, Company, or Opportunity records in Prophet migrate as note.note records with res_model and res_id linking to the corresponding Odoo partner or crm.lead. If the customer uses Prophet's internal messaging thread, those messages migrate as mail.message records.

Prophet tags on Contacts and Companies (industry tags, segment tags, custom labels) map to Odoo res.partner.category records as partner tags. Tags are created as category records in Odoo before the partner migration phase, and partner.category links are created via the Odoo partner category many2many field during partner import. Prophet tags that do not have an Odoo equivalent are flagged in the scoping report for the customer to confirm before creation.

If the customer uses Prophet's product catalog for Opportunity line items, we map product records to Odoo product.template. Prophet product name, SKU, unit price, and description map to Odoo name, default_code (sku), list_price, and description. Product categories map to Odoo product.category. The migrated products are linked to Opportunity line items via the Odoo sale.order or crm.lead.line_ids mechanism depending on whether the customer uses Odoo CRM quoting.