Migrate from Allegory to Odoo CRM

Allegory contacts map directly to Odoo res.partner records. The partner's type field is set to 'contact'. Allegory contacts without a primary company assignment land as res.partner records with no parent_id, and the owning user is resolved by email match against Odoo res.users.

Allegory company records map to Odoo res.partner entries with type='company'. The company name populates res.partner.name, and address fields (street, city, state, country, zip) map to the partner's address fields. Industry and employee-count fields from Allegory migrate as custom fields on res.partner.

Allegory's contact-to-company association (N:N with primary flag) maps to Odoo's parent_id on res.partner. The primary company becomes the parent partner; additional company associations are recorded as related company-type res.partner records linked via address fields or stored in a migration reference field.

Allegory deal records map to Odoo crm.lead with type='opportunity'. Deal name becomes crm.lead.name, amount maps to crm.lead.expected_revenue, close date maps to crm.lead.date_deadline, and stage maps to the corresponding Odoo crm.stage record within the target pipeline. The probability percentage from Allegory transfers to crm.lead.probability, and deal notes migrate to crm.lead.description.

Each Allegory pipeline becomes an Odoo CRM Pipeline record. Odoo pipeline records group stages and control access per sales team via team_id. We create the pipeline in Odoo before migrating deals so stage foreign keys resolve correctly during data load.

Allegory stage names map to Odoo crm.stage records by value, per pipeline. Stage probability, legend color, and is_won flags are carried over. Stage-entered timestamps from Allegory are preserved in a custom datetime field on crm.lead for historical stage-duration reporting. The stage sequence order is maintained to preserve the original pipeline flow and deal progression logic.

Allegory activity records — calls, emails, meetings — map to Odoo mail.activity entries with activity_type_id set per activity kind (call, email, meeting). Original timestamps and assigned user are preserved via activity_date_deadline and user_id. The activity is linked to the corresponding crm.lead or res.partner record by source ID.

Allegory notes become Odoo mail.message records with subtype='comment' on the target res.partner or crm.lead. The note body populates mail.message.body; create_date and author_id are preserved from the Allegory record. Attachments on notes are downloaded and re-uploaded to Odoo's ir.attachment, with the original filename and content type retained for traceability and audit continuity.

Allegory file attachments are downloaded from source storage, re-uploaded to Odoo's filestore (or linked external storage), and attached to the corresponding res.partner or crm.lead record. The original filename and content type are preserved. Large file handling follows Odoo's 25MB per-file default.

Allegory custom fields on Contact, Company, and Deal require Odoo custom field creation before migration. We analyze Allegory's custom field types (text, number, pick-list, date, checkbox) and map them to equivalent Odoo field types (char, float, selection, datetime, boolean) using ir.model.fields with the appropriate ttype and selection_options.

Allegory owner IDs are resolved by email address against Odoo res.users. Records whose owner email has no Odoo user match are flagged pre-migration; you either invite those users to Odoo or reassign to a fallback user. No Allegory record lands in Odoo without a resolved user_id.

Allegory tags applied to deals and contacts map to Odoo crm.tag (for crm.lead) and res.partner.category (for res.partner) respectively. Any tags that do not have an existing equivalent in Odoo are created automatically during migration. Both the tag color attributes and the original tag names from Allegory are fully preserved throughout the migration process.