Migrate from Infor CloudSuite Customer Relationship Management (CRM) to Odoo CRM

Infor Customers are the top-level organizational records with territory, SIC code, revenue, and employee count stored on the CRM tab. We map these to Odoo Res.partner records with partner_type=company. The Infor Customer ID becomes the external ID for Odoo import, and the CRM tab fields (territory, revenue range, employee count) map to custom fields on the Res.partner record. This is the parent record for all subsequent Contact and Opportunity imports.

Infor Sales Contacts link to the Customer record and store name, role, phone, and email. We map to Odoo Res.partner records with partner_type=contact and parent_id pointing to the Company partner. Infor's Outlook export creates duplicates rather than syncing — we deduplicate on email address before import so that no duplicate contact lands in Odoo. Contact roles map to Odoo's function field; multiple roles per contact use the Contacts app's tags.

Infor Opportunities track deal stage, value, probability, and close date with links to Accounts and optional Sales Period. We map to Odoo crm.lead (lead_ids in the CRM pipeline). The Infor opportunity stage maps to an Odoo stage in the pipeline; we pre-create the Odoo stage sequence to match the Infor stage order. Probability, expected revenue, and close date transfer directly. Owner assignment maps to Odoo user_id on the lead.

Infor Prospects and Leads are pre-conversion records with source, status, and owner. We map them to Odoo crm.lead records in the Lost or New state (not yet in the active pipeline). Lead source maps to Odoo's source_id (medium_id on the lead). Owner maps to user_id. We preserve the original Infor lead creation date as create_date for audit.

Infor Sales Forecasts aggregate Opportunities under named Sales Periods — date-range constructs that are a distinct schema type, not standard date fields. We decompose each Sales Period into its start and end date, then filter the migrated Opportunities by close date to reconstruct the forecast group in Odoo CRM Forecast. The Odoo Forecast mechanism uses date filters rather than named period objects, so we replicate the grouping logic as saved filter views per period.

Infor tracks Prospect and Customer Interactions (calls, emails, meeting notes) against the Contact record. We map these to Odoo mail.message records attached to the Res.partner contact. Call interactions with disposition and duration map to crm.phone.call records if the Odoo VoIP module is installed; otherwise they land as mail.message with a custom call type tag. Activity timeline ordering is preserved by setting create_date to the original interaction timestamp.

Infor Campaigns store type, status, start/end dates, and budget. Campaign Items link contacts or products to a campaign. We map to Odoo Utm.campaign records for the campaign itself, with utm.mixin mixin fields added to the linked Contact and Lead records during import. Campaign Items that reference specific Contacts or Opportunities are handled via Odoo's mass mailing and campaign tagging mechanism.

Infor CRM's ticketing system stores support cases with status, priority, assigned agent, and conversation history. We map to Odoo Helpdesk.ticket (part of the Helpdesk app). Ticket status maps to stage_id, priority maps to priority. The linked Infor Customer and Sales Contact map to the Odoo partner_id and contact_id on the ticket. Multi-line ticket threads map to mail.message records on the ticket. Odoo Helpdesk requires the app to be installed in the destination environment.

Infor Territories assign sales reps to geographic or account-based regions with quotas per rep per territory per period. We map Territories to Odoo Crm.team records (sales teams) and Territory assignments to the team membership list. Infor quota values do not have a direct Odoo CRM equivalent — we store quota amounts in a custom decimal field on the Crm.team record as a reference value for the Odoo sales team, noting that Odoo does not natively enforce quota against team membership. The customer's admin rebuilds quota enforcement in Odoo Studio or via a custom server action.

Infor Products and Price Lists manage the product catalog and pricing tiers for quoting. We map Product records to Odoo Product.template. The Infor price list becomes Odoo's Pricelist (product.pricelist) with the pricing tiers migrated as pricelist.item rules. Complex tiered pricing structures require validation in Odoo because Infor's surcharge calculation logic (commodity-based surcharges stored in the product form) has no direct Odoo equivalent and may require a custom module.

Infor CRM Quotes are linked to Opportunities and Accounts with products, prices, and discounts. We map Quote headers and line items to Odoo Sale.order records. Opportunity lookups map to the Odoo sale.order's opportunity_id reference if Odoo CRM is linked to the Sales app. Quote status (draft, sent, confirmed) maps to Odoo order_state. Line item products, quantities, and unit prices transfer directly; Odoo recalculates tax and totals on import if taxes are configured in the destination.

Infor CRM custom fields on Accounts, Contacts, Opportunities, and Tickets use Infor-specific field types (picklists, lookups, dates). We inventory every custom field during scoping, map Infor picklist values to Odoo selection fields or many2one relations depending on the data type, and pre-create the Odoo custom fields in developer mode before any data loads. Custom fields with lookup relationships require pre-import creation of the referenced records to satisfy the foreign key constraint.

Infor CRM Groups are saved query results that segment records by criteria. We document every active Group with its filter criteria and replicate the segmentation in Odoo as saved Ir.filters (filter views visible in the CRM pipeline kanban and list views). Groups that reference custom fields or complex AND/OR logic are recreated as Odoo domain strings in the filter definition. The customer reviews and validates the filter replication during the sandbox phase.

Infor CRM attachments on Contacts, Accounts, Opportunities, and Tickets migrate as Ir.attachment records in Odoo, linked to the corresponding Res.partner or crm.lead via res_model and res_id. We export attachments from Infor to a file store (S3 or Azure Blob), then create the Ir.attachment records with the external file URL stored in the store_fname or url field. Attachments stored in Infor's database are extracted and re-hosted in Odoo's attachment store.