Migrate from Function 365 to Odoo CRM

Function 365 Contact rows become res.partner records with partner_type set to 'contact'. The contact's primary account lookup (parentcustomerid in Dynamics 365) maps to the parent_id field on the res.partner record, establishing the relationship between individual contacts and their employing organizations. Email addresses, phone numbers, street addresses, city, state, and postal code fields map directly to their corresponding res.partner field names, preserving all standard contact information during the transformation process.

Function 365 Account rows become res.partner records with partner_type='company'. The company name maps to name, website maps to website, and industry code maps to industry. Child Contact records under an Account receive parent_id pointing to the newly created company partner, preserving the account-to-contact hierarchy in Odoo's partner structure.

Function 365 Opportunity rows map to crm.lead records where type='opportunity'. The accountid lookup resolves to the target res.partner (company) record. Estimatedvalue maps to planned_revenue; closeprobability maps to priority as a percentage. The original opportunityid is preserved in x_source_opportunity_id for reconciliation.

Function 365 Lead rows map to crm.lead records where type='lead'. LeadSource maps to source_id (linking to crm.tracking.source). The lead's companyname field is used to either match an existing res.partner company or create a new one before the lead converts to opportunity.

Function 365 activityparty records (phonecall, email, appointment) become mail.activity entries. The activity_type_id is resolved by matching the Dynamics 365 activity type code: 1=Call, 2=Email, 3=Meeting. The res_id links to the target crm.lead or res.partner; the user_id links to the activity's owner.

Function 365 Annotation records with notetype set to 'annotation' migrate as ir.attachment entries linked to the target model (crm.lead or res.partner) through the res_model and res_id fields. The original document body content and filename are preserved intact during the migration, and Odoo's standard attachment storage path is utilized on the destination instance for all migrated annotation files.

Function 365 systemuser records are matched to Odoo res.users by email address (internalid). Unmatched users are flagged before migration; your team either creates the Odoo user first or assigns records to a fallback user. The user's full name populates the res.users name field.

Function 365 BusinessUnit rows map to crm.team records in Odoo, with each business unit becoming a separate CRM team. The business unit's name and member list (derived from systemuser positions within the business unit) populate the team name and team member structure in Odoo. All Opportunity records owned by a business unit are reassigned to the corresponding crm.team based on the opportunity's owning business unit lookup.

Dynamics 365 pipeline stages defined in the ProcessStage entity are mapped value-by-value to Odoo crm.stage records within each corresponding crm.team. The stage's statecode (Active, Won, or Lost) maps to the folded and stage_type flags on the crm.stage record. The original sort order from Dynamics 365's ProcessStage stepid is preserved to maintain the kanban column sequence in Odoo's pipeline view.

Function 365 custom entities (tables created in the Power Platform or solution layers) require Odoo custom model creation via the ORM. We create the model with the appropriate _name, add x_ prefix fields matching the source schema, and set up the many2one relations to standard Odoo models before data loads.

Dynamics 365's LeadToOpportunityProcess plugin does not have a direct Odoo equivalent. The conversion logic (creating an Opportunity from a Lead, linking the Contact, setting initial stage) must be replicated using Odoo's crm.lead convert wizard after migration. We document the source conversion rules as a rebuild reference.

Function 365 Connections representing N:N record relationships used for customer partnerships and stakeholder tracking are merged into Odoo's mail.followers model for record following functionality, and partner_id relations on crm.lead for stakeholder association. Only connections that represent 'stakeholder' roles migrate as partner_ids on the opportunity record, ensuring that relevant business relationships are preserved in the target Odoo system.