Migrate from Aurea CRM to Odoo CRM

Aurea Contact records map 1:1 to Odoo Partner records of company_type = person. The Aurea contact's first name and last name map to Odoo's firstname and lastname fields (installed via the base_firstname_modules convention). Email, phone, mobile, and address fields map directly. We use Partner.email as the dedupe key during import. The Aurea contact's primary Account relationship maps to a separate Partner record of company_type = company with the contact attached as a child Contact record.

Aurea Account (Company) records map to Odoo Partner records of company_type = company. The Account name maps to Partner.name, Account address fields map to Odoo's street, city, state, zip, country fields, and the Account website maps to Partner.website. Parent-child hierarchy between accounts (if configured) maps to Partner.parent_id for subsidiary relationships. All Aurea Contacts linked to the Account receive the corresponding Partner.parent_id during migration.

Aurea Opportunity records map to Odoo CRM Lead records. The Opportunity name maps to crm.lead.name, deal value maps to crm.lead.planned_revenue, close date maps to date_deadline, and probability maps to probability. Aurea's configurable pipeline stage labels map to Odoo's crm.stage values; we create one Stage per Aurea stage and preserve the stage sequence order. Owner assignment migrates by resolving the Aurea user ID to an Odoo res.users record via the User mapping.

Each Aurea pipeline stage becomes an Odoo crm.stage record within the applicable team. Stage names, sequence order, and probability percentages migrate. We configure the stage as is_won or is_won = false per the Aurea closed-won designation. If Aurea's pipeline has multiple deal pipelines, these map to separate Odoo CRM Teams (crm.team) with their own stage sequences.

Aurea Activity records map to Odoo mail.activity. The activity type (call, appointment, task) maps to activity_type_id, subject maps to summary, due date maps to date_deadline, and the Aurea activity note maps to mail.message body linked to the activity. Activity assignment (owner) resolves via the User mapping. If the Aurea activity is linked to an Opportunity, we set the Odoo activity's res_id to the corresponding crm.lead id and res_model to crm.lead.

Aurea Campaign Manager records (Enterprise tier) map to Odoo utm.campaign. Campaign name, type, status, start date, and end date migrate. Response metrics (leads generated, conversions) map to Odoo's custom fields on utm.campaign because Odoo's standard campaign model tracks source attribution rather than campaign performance metrics. We flag any Aurea-specific campaign workflow logic for the workflow inventory document.

Aurea partner relationship management records map to Odoo Partner records with the partner_share flag set to true (indicating a portal-accessible partner). Partner quota and territory assignments from Aurea PRM migrate to custom fields on the Odoo Partner record. If the customer uses Aurea's partner portal, we document the portal access requirements so the Odoo partner portal module can be configured as the replacement.

Aurea document management files linked to records migrate as Odoo ir.attachment records. The file name maps to ir.attachment.name, the file itself migrates as a base64-encoded binary in datas, and the res_model and res_id point to the migrated parent object (Partner for Contact/Account documents, crm.lead for Opportunity documents). We flag high-volume attachment datasets (>10,000 files) for multi-batch import with Odoo's ir.attachment batch write mode.

Aurea administrator-defined custom fields across Contact, Account, Opportunity, and Activity objects map to Odoo custom fields created via Settings > Technical > Database Structure > Custom Fields before migration begins. We preserve field type mapping (text to char, numeric to float, date to date, picklist to selection). Complex Aurea picklists with multi-value support map to Odoo many2many or selection depending on the data. Custom field labels migrate as Odoo field description strings.

Aurea user and owner records migrate as Odoo res.users. We resolve by matching Aurea user email to Odoo res.users.login. Any Aurea Owner without a matching Odoo User goes to a reconciliation queue for the customer's admin to provision. We also create a res.partner record for each user (Odoo's standard practice) so that user-managed CRM records have correct partner associations.

Aurea territory assignments and quota values map to Odoo crm.team records for territory scoping and custom fields on the relevant Partner or User record for individual quota. Because Aurea's territory data model varies by installation, we catalog the exact field structure during discovery and design a target schema that preserves the business relationship without requiring Odoo custom module development unless the complexity demands it.

Aurea Opportunity records carry a linked Contact as the primary buyer contact. We map this relationship by first resolving the Contact to an Odoo Partner, then linking it to the crm.lead via Odoo's standard partner_id field. Secondary Opportunity contacts (influencers, champions) migrate as crm.lead.partner_assigned_ids records. This preserves the Aurea 360-degree view linking a deal to its key contact.