Migrate from Tall Emu CRM to Odoo CRM

Tall Emu Company records map to Odoo res.partner records with partner_type set to company. Company name, street address, city, state, postcode, country, phone, and website transfer directly. Odoo requires a partner to exist before any Contact can reference it via parent_id, so we import Companies first in every migration run. Email and domain fields are preserved for deduplication. If the destination Odoo instance has contacts from other integrations, we run a domain-based dedupe pass before inserting.

Tall Emu Contact records map to Odoo res.partner with partner_type set to individual and parent_id pointing to the mapped Company partner. First name, last name, email, phone, mobile, role, and address fields transfer directly. We resolve parent_id by matching the Tall Emu Company name against the destination partner name field. If multiple companies share the same name in Odoo, we use the most recently created or the one with matching city and country as additional disambiguation criteria.

Tall Emu Products map to Odoo product.template records with product variants managed via Odoo's attribute and value system. SKU, product name, description, sales price, cost price, and stock on hand transfer. Serial number tracking, landed costs, and reorder points map to Odoo's lot_id, landed_cost_ok, and reorder_point fields. BOM structures map to Odoo mrp.bom records with component lines and routing steps. The migration sequence is product templates first, then BOM components, then stock quant data last.

Tall Emu Pipelines map to Odoo crm.lead records with type = opportunity. Stage names, probabilities, and stage order transfer to Odoo's stage_id and probability fields. Odoo stage probabilities default to 0-100 integers; we map Tall Emu's decimal probability values by rounding. Each Tall Emu pipeline becomes a separate Odoo team (crm.team) with its own stage sequence. Closed-Lost and Closed-Won reasons map to Odoo's lost_reason_id if the Odoo CRM app is version 17 or later.

Tall Emu Quotes map to Odoo sale.order records in draft/quotation state. Line items (product, quantity, unit price, discount) transfer to sale.order.line records linked to the sale.order. Terms and acceptance status migrate as a note and state field respectively. Tall Emu Quote status values (Draft, Sent, Accepted, Declined) map to Odoo state values (draft, sent, sale, cancel). PDF templates and signed documents do not transfer as binary files; we flag attachments for manual re-upload post-migration.

Tall Emu Sales Orders map to Odoo sale.order records in confirmed or done state for the order header, with picking records (stock.picking) generated via Odoo's delivery module if the Inventory app is active. Line items carry over to sale.order.line. If the destination has Odoo Manufacturing installed, confirmed orders with manufactured components can trigger mrp.production records. We flag any order with fulfilment state outside Odoo's standard picking workflow for manual review.

Tall Emu Subscriptions (Plan, Status, Order Quantity, Billable Quantity, Price, Period, Renewal Due Date) map to Odoo sale.subscription records. Status values (Active, Expired, Paused, Cancelled) require explicit mapping to Odoo's close_reason_id and state fields. Odoo Subscription requires the sale_subscription app (Odoo Enterprise) or the sale_management module (Community) with custom fields. Period and billing frequency map to Odoo's recurring_interval and recurring_rule_type. If the destination lacks the subscription module, we map to sale.order with a recurring note field and flag for rebuild.

Tall Emu Activities (meetings, calls, emails, tasks) with assignees, due dates, and completion status map to Odoo mail.activity records linked to the parent res.partner or crm.lead via res_model and res_id. Activity type (call, meeting, email, task) maps to Odoo's activity_type_id. The original timestamp preserves the activity timeline ordering. If Odoo has theDiscuss or VoIP module enabled, call records can be further classified with subtype. We resolve res_id by matching the activity's related record against the migrated partner or lead IDs.

Tall Emu custom fields on Companies, Contacts, Products, Pipelines, and Quotes migrate as Odoo custom ir.model.fields created via Settings > Technical > Custom Fields before migration. We audit Tall Emu's custom field availability per module during discovery (some modules do not support custom fields). If the destination Odoo version lacks an equivalent field type (e.g., Tall Emu checkbox with no Odoo equivalent boolean), we flag it for pre-migration field creation as a char or selection field with a note for manual cleanup post-migration.

Tall Emu freight records (carrier, tracking number, delivery status) map to Odoo stock.picking records with delivery_type and carrier_id if the Inventory and Delivery apps are active. Tracking URLs map to picking.note. If the destination Odoo instance does not have the Delivery app installed, freight records migrate as notes on the related sale.order. We flag this gap during scoping and recommend installing the Delivery app before migration if freight history is critical for the customer's operations.

Tall Emu Users map to Odoo res.users by email match. Roles and team assignments transfer as Odoo access rights groups (res.groups) and crm.team membership respectively. Teams migrate as crm.team records with member_ids linking to the mapped res.users records. Any Tall Emu User without a matching Odoo user email is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Tall Emu stores document attachments (PDFs, images) linked to records, but there is no documented bulk export endpoint for binary files. We export file metadata (filename, record association, upload date) and flag all attachments for manual re-upload post-migration. For Quotes and Orders with associated PDFs, we note the parent record so the customer's admin can re-attach the files in Odoo's document management module after migration.