Migrate from Apollo ERP to Odoo CRM

Apollo contacts map to Odoo res.partner records with is_company=False. The partner's name is assembled from first_name and last_name (Apollo) into Odoo's display_name. Email, phone, mobile, title, and address fields map directly. If a contact has no email or phone, Odoo requires at least a name — we use the contact's full name as a fallback.

Apollo companies map to Odoo res.partner records with is_company=True. The company name becomes display_name, domain becomes website, industry is stored as category_id (a many2many tag), and employee count is stored as employee_count (an integer field on partner). The company's address fields map to street, city, state_id, country_id, and zip on the partner record.

Apollo stores a primary_company_id on each contact. We map this to res.partner.parent_id — the individual contact's parent_id points to the company partner record. Apollo contacts without a primary company are migrated as standalone partners. Odoo enforces that child partners have a parent_id; contacts without a company are created without one and flagged for admin review.

Apollo deals map to Odoo crm.lead records where type='opportunity'. Deal name becomes name, amount becomes expected_revenue, close_date becomes date_deadline, stage maps via value_mapping to an Odoo crm.stage record, and owner resolved by email match to Odoo res.users records. Deals without an amount are migrated with expected_revenue=0 and stage=first_open_stage.

Apollo pipelines have no direct Odoo equivalent — Odoo organizes pipeline visibility by crm.team (sales team) and each team has its own set of crm.stage records. We map each Apollo pipeline to a crm.team with its own stage set. If the Odoo instance already has teams configured, we map Apollo pipelines to existing teams or create new ones based on pipeline names. Each pipeline stage becomes a crm.stage within that team.

Apollo deal stages are string labels ('Prospecting', 'Qualified', 'Demo Scheduled', 'Proposal Sent', 'Negotiation', 'Closed Won', 'Closed Lost'). Each maps to an Odoo crm.stage record within the target team. Stage probability is pulled from Odoo's default model or set per stage if Apollo has probability data. Closed Won and Closed Lost are Odoo's mandatory terminal stages; we ensure every Apollo pipeline maps to them or equivalent terminal stages.

Apollo engagement records (calls, emails, meetings, notes) migrate as Odoo mail.message records linked to the target crm.lead or res.partner. Call logs use subtype 'mt_comment' with a custom 'Call' subtype flag; emails use 'email'; meetings create a calendar.event record plus a related mail.activity. Timestamps, body content, and owner (user_id) are preserved. Attachments on activities download and re-upload to Odoo's ir.attachment storage.

Apollo custom fields on contacts (created via POST /api/v1/fields with modality='contact') require Odoo custom field creation in Settings > Technical > Models > Fields. We use the field label as display_name and generate a technical name with x_ prefix (Community) or without (Enterprise). Field type mapping: string/textarea → char/text, number → float or integer, date → date, datetime → datetime, boolean → boolean. Required flags are set if Apollo marked the field as required.

Apollo custom fields with modality='account' map to Odoo res.partner custom fields, same creation mechanism as contact custom fields. Both individual contacts and company partners can have the same custom field name — we create a single field on res.partner and it is available on both record types in Odoo.

Apollo deal custom fields (modality='opportunity') map to custom fields on the crm.lead model in Odoo. These are created the same way as partner custom fields. Note that crm.lead is the same model as crm.lead for leads — the field is available on both leads and opportunities in Odoo.

Apollo sequences (automated email cadences with step timing, A/B split, and delivery tracking) have no structural equivalent in Odoo CRM. Odoo's Email Marketing app handles mass campaigns but not individual rep-level sequences. We export sequence definitions as structured JSON — step order, delay days, subject, body template, and conditions — for a consultant to rebuild using Odoo server actions and mail.mass_mailing.

Apollo stores owner_id on contacts, companies, and deals. We match Apollo owner email addresses against Odoo res.users records by email. Unmatched owners are flagged before migration — either the user is invited to Odoo first or records are assigned to a fallback Odoo user designated by the admin. No record lands in Odoo without a valid OwnerId (user_id) field.