Migrate from Pega Sales Automation to Odoo CRM

Pega Accounts map to Odoo res.partner records with the partner_role field set to 'company'. Industry classification from Pega's Industry property maps to Odoo's industry_id lookup. Account address fields (street, city, state, country, zip) map to Odoo's standard address fields on res.partner. We import Accounts first because all other entities have foreign-key dependencies on them. Odoo requires the parent partner record to exist before Contact records can reference it via parent_id.

Pega Contacts map to Odoo res.partner records with partner_role set to 'individual' and parent_id pointing to the Account partner record. Pega's Contact-to-Account association migrates as the parent_id reference on the individual partner. Email, phone, mobile, title, and function fields map directly. If Pega Contacts carry a separate job title, we map it to res.partner.function.

Pega Leads map to Odoo crm.lead records with type = 'lead'. Pega-specific disposition codes (qualification status, lead source) are preserved in custom fields on the crm.lead because Odoo's crm.lead model supports extension via custom fields. If the destination Odoo instance uses Odoo's native Lead-to-Opportunity conversion workflow, we map Pega's lead status to Odoo's lead_stage_id so the conversion action works without manual intervention.

Pega Opportunities map to Odoo crm.lead records with type = 'opportunity'. Stage progression, amount, expected_close_date, and probability transfer to Odoo's stage_id, planned_revenue, date_deadline, and probability fields. The Pega-to-Odoo stage name mapping is configured during scoping based on the customer's stage matrix. Odoo's crm.lead uses a many2one reference to the responsible partner (user_id), which we resolve via owner email matching against Odoo's res.users table.

Pega Opportunity-Product junction records (quantity, unit price, discount) map to Odoo sale.order.line records attached to a sale.order. We first create the sale.order header (linked to the Opportunity's Account partner and responsible user), then create line records for each product. Product lookups are resolved via product_code matching against Odoo's product.product table.

Pega Activities attached to Opportunities, Contacts, or Accounts map to Odoo mail.activity records. Activity type (call, email, meeting, task) maps to Odoo's activity_type_id, with the original Pega activity notes preserved in the note field. Activity dates and timestamps transfer directly to Odoo's date_deadline and create_date. We resolve the parent record reference (res_model and res_id) by matching the Pega parent entity type and ID against the migrated Odoo record's ID.

Pega Products map to Odoo product.product records. The Pega product code becomes Odoo's default_code (sku). Unit price migrates to Odoo's list_price. If the customer uses Odoo's sale module, we also create corresponding product.pricelist.item entries in the standard price list.

Pega Sales Teams (assignment entities defining which users have access to an Account or Opportunity) map to Odoo crm.team records. Team membership migrates as crm.team.member records linking to res.users. If the destination Odoo has a different team segmentation model, we map the team assignments to Odoo's salesteam_id on crm.lead or to a custom many2many field on res.partner.

Pega Territories (geography or business-unit segmentation rules) do not have a direct Odoo equivalent. We map territory assignments to Odoo crm.tag records (one tag per Pega territory name) and attach them to the relevant Account and Opportunity records via crm.lead.tag_ids. For more granular segmentation requirements, we add a custom selection field on res.partner.

Pega Campaigns group Leads and Activities for coordinated outreach. We map campaigns to Odoo crm.tag records (one tag per campaign name) on the relevant crm.lead records, or to Odoo's utm.source and utm.campaign models if the customer uses Odoo's marketing attribution features. Campaign status is preserved in a custom field on crm.lead.

Pega custom fields (properties added via App Studio or Rule configuration) require individual manual mapping against Odoo's field registry. There is no automated discovery endpoint in Pega's API that enumerates every custom field across all entities in a single call, so we enumerate them entity by entity via the Pega API or by reviewing the customer's Ruleset exports. Each custom field is then created as a custom ir.model.fields entry in Odoo (via the settings interface or a data migration script), with the Pega data type matched to the nearest Odoo field type (char, integer, float, date, datetime, selection, many2one, etc.). Custom field mapping is performed before any data import so that the destination schema accommodates the extended records.

Pega wraps many entities as Cases (Work Objects) under its BPM engine, with their own lifecycle states, assignments, and SLA timers. Migrating Cases to Odoo CRM requires flattening the case structure: we map the case's primary subject to the crm.lead name, the case status to a custom field on crm.lead, and the SLA timer data to a date field. If the customer uses Odoo's helpdesk module (app_website_helpdesk), we can route Cases to helpdesk.ticket instead, which supports SLA configuration natively. The case lifecycle state is preserved in a custom field for audit trail purposes.