Migrate from Origo BPO to Odoo CRM

Origo BPO client accounts (companies that receive managed services) map directly to Odoo res.partner records with the company flag set to True. The client account name becomes the partner name field; Origo's original account ID is stored as x_source_account_id in the custom field for traceability back to the source system. Address, phone, and website fields map directly to their Odoo equivalents. If Origo provides a country code or region identifier, those map to Odoo's country_id and state_id records respectively.

Individual contacts associated with Origo BPO client accounts migrate as Odoo res.partner records with company=False. The parent_id field links each contact to the corresponding client account partner. Email, phone, and address fields map directly; title/jobtitle stored as custom if needed.

Origo BPO service tickets become Odoo crm.lead records. Open or in-progress tickets route to crm.lead with type='lead'; tickets tied to active sales conversations route to type='opportunity'. The original Origo ticket number stored in x_origo_ticket_id for reconciliation. Stage mapped from ticket status: New→New Lead, In Progress→Qualified, Resolved→Won (or closed lost depending on SLA outcome).

Origo BPO SLA tiers (Bronze, Silver, Gold, Platinum or custom naming) have no Odoo native equivalent. We create x_sla_tier__c as a selection field on both res.partner and crm.lead, preserving the exact tier label from Origo. SLA response-hour targets stored as x_sla_response_hours (integer). Escalation level stored as x_escalation_level (integer).

Origo BPO communication logs (emails, calls, internal notes attached to service tickets) migrate as Odoo mail.activity records. The activity_type_id maps from Origo note type: email→email, phone call→call, meeting→meeting, internal note→upload_file (or as a note attached to the lead). Original timestamp preserved in create_date; agent owner mapped to Odoo res.users by email match.

Origo BPO service categories (e.g., Finance, HR, IT Support, Field Service) map to Odoo crm.tag records — tags are created for each category and linked to relevant crm.lead records. Alternatively, if a pick-list is preferred, x_service_department__c custom field on crm.lead handles the mapping with value-by-value translation.

Files attached to Origo BPO service tickets or client records re-upload to Odoo ir.attachment and linked to the corresponding crm.lead or res.partner record via res_model and res_id. File size limits per Odoo configuration apply; files exceeding limit split or linked externally.

Origo BPO invoice records related to service fees do not map to Odoo CRM objects. If Odoo Accounting module is active, billing records migrate separately as account.move entries (Accounts Receivable). We flag these as a separate migration scope and apply the account.move field mapping if the accounting module is present.

Origo BPO agents or service owners assigned to tickets or client accounts resolve to Odoo res.users by email address match. Unmatched agents flagged before migration — your Odoo admin either creates the user record or assigns records to a fallback owner. Title and department from Origo stored as custom fields on res.users if needed.

Any extended attributes stored in Origo BPO beyond standard fields (e.g., field_service_region, client_vertical, renewal_date) migrate as Odoo custom fields (x_*). We create the custom field definition in Odoo before data load, then map values during migration. All custom fields documented in the migration plan with Odoo field type recommendation.