Migrate from Workpex to Odoo CRM

Workpex Leads map directly to Odoo CRM Lead records. We preserve the lead status (New, Contacted, Qualified, Lost), source field (Manual, Website, Facebook, Referral), assigned owner, and creation timestamp. Any Workpex custom lead properties (regional flags, product interest, budget range) are discovered during scoping and mapped to Odoo custom fields on crm.lead. If Workpex lead records include notes or descriptions, these migrate as the Lead description field.

Workpex Contacts map to Odoo CRM Contacts. We preserve name, phone, email, address, and company association. Workpex stores Contacts linked to Leads — we migrate Contact records independently and note any source_lead_id for manual association review in Odoo since Odoo does not maintain a native Lead-to-Contact reference on the Contact object. Mobile and secondary phone numbers map to Odoo's phone and mobile fields.

Workpex Companies (Accounts) map to Odoo CRM Companies with name, website, street address, city, state, country, and phone preserved. Odoo uses res.partner with the company_flag set for the company-level record. We resolve the Workpex Company-to-Contact associations so that each Contact in Odoo has the correct company_id parent link. Custom company fields from Workpex migrate as custom fields on res.partner.

Workpex Deals map to Odoo CRM Opportunities (crm.lead with type='opportunity'). The Workpex deal name, amount, expected close date, stage, and owner migrate. Stage names from Workpex are mapped to Odoo stage names within the designated Sales Team; stage probabilities are approximated from Workpex if available or set to Odoo defaults and flagged for admin review. Lost reason and notes migrate to Odoo's lost reason and description fields.

Workpex pipeline stages map to Odoo CRM Stages within the default Sales Team or a new Sales Team created to match the Workpex pipeline structure. Each stage receives a sequence order, a probability percentage, and a fold status (whether open deals in that stage collapse in the kanban view). If Workpex has deprecated or custom stages, we flag them during scoping and map them to the nearest Odoo equivalent or a custom stage the admin creates before import.

Workpex Tasks map to Odoo Project Tasks if Odoo Project is installed, or to Odoo CRM Tasks (attached to the Lead or Opportunity via crm.activity). We preserve task name, description, due date, assignee, and open/closed status. If the Workpex task is linked to a specific lead or deal, we create the corresponding crm.activity record in Odoo rather than a standalone task so that the activity appears in the CRM timeline.

Workpex Follow-up Reminders tied to Leads and Contacts migrate as Odoo CRM Activities (mail.activity) of type Reminder. We preserve the reminder date, the associated Lead or Contact, the assignee, and the reminder description text. Odoo displays these as the Next Activity Date and type on the crm.lead form. If Workpex reminder records include a flag for overdue or stagnant leads, we set the Odoo activity_deadline accordingly and flag the record in the migration report.

Workpex call metadata (direction, duration, timestamp, disposition, recording URL if available) migrates as an Odoo CRM Activity of type Call attached to the related Lead or Contact. Call duration and disposition map to custom fields on crm.activity (call_duration, call_disposition). If Workpex exports include audio recordings, we store them as Odoo ir.attachment records linked to the activity. We note that Odoo requires the VoIP or a third-party telephony module (Asterisk, Twilio via connector) to log calls natively in the Activity type picker; without it, calls land as custom-activity-type records.

Workpex Users and Owners are mapped to Odoo Users by email address match. We extract every distinct owner referenced on Leads, Contacts, Deals, Tasks, and Activities and match against the Odoo destination's res.users table. Any Workpex owner without a matching Odoo User is placed in a reconciliation queue for the customer to provision before record import resumes. Inactive Workpex owners map to inactive Odoo Users to preserve historical assignment.

Workpex custom fields on Leads and Contacts are discovered during the pre-migration audit and mapped to Odoo custom fields on crm.lead and res.partner. Field data types are preserved where possible (text to char, number to float or integer, date to date, checkbox to boolean). Multi-select or tag-style custom fields in Workpex map to Odoo many2many tags or char fields depending on the target configuration chosen during scoping. Custom fields are created in Odoo via Settings > Technical > Custom Fields before data import begins.

Workpex WhatsApp message logs and marketing interaction data export as Odoo Mail Message records on the related Lead or Contact. We preserve the message timestamp, direction (inbound/outbound), and text content. Rich media (images, PDFs sent via WhatsApp) migrate as ir.attachment records linked to the message. Odoo's WhatsApp Integration app (Enterprise) or a third-party WhatsApp connector can re-link these as threaded conversations post-migration if the customer enables the integration.

File attachments associated with Leads, Deals, or Tasks in Workpex export as Odoo ir.attachment records linked to the corresponding crm.lead or document record. We map the original filename, file type, and binary content. Large files (>25 MB) may exceed Odoo's default attachment storage limits and are flagged for the customer to configure Odoo's attachment storage (file system, Amazon S3, or Google Drive) before migration. Unsupported binary formats are flagged for manual upload.

Workpex GPS tracking data for field sales teams has an undocumented data structure. We discover the GPS record schema during the scoping phase and map it to Odoo custom fields on crm.lead (latitude, longitude, last_location_timestamp) or store as structured text if the format is proprietary. If GPS data is stored in a binary or proprietary format, we flag it for manual review and export and document the latitude/longitude extraction steps for the customer's admin.

Facebook Ad management data stored in Workpex (campaign name, lead source, ad set, creative, attribution window) exports as Odoo CRM Campaign records with custom fields for the Facebook-specific dimensions. We map the campaign name and lead source attribution; the customer configures the Odoo Marketing app if they want campaign tracking emails to flow back into Odoo. Attribution data (UTM parameters, conversion timestamps) is preserved in custom fields and flagged for reporting reconstruction.