Migrate from Aidoo Mobile to Odoo CRM

Aidoo Mobile customer records map 1:1 to Odoo res.partner records in company mode. The customer name maps to res.partner.name, primary email to res.partner.email, and phone to res.partner.phone. Sites attached to the customer become additional Address records linked to the same res.partner parent.

Individual contacts within an Aidoo Mobile customer map to res.partner records in contact mode (type='contact') linked via res.partner.parent_id to the company partner. Email, phone, mobile, and job title map directly. If Aidoo stores a contact as a standalone customer record, it is treated as a res.partner without a parent.

Aidoo Mobile sites attach address, city, state, postal code, and country to a customer. In Odoo, these become res.partner address records (type='other') linked to the parent company partner. The site name is stored in res.partner.street2 or in a custom Char field (x_site_name) if the site has a display name distinct from the customer name.

Aidoo Mobile work orders translate to Odoo crm.lead opportunity records. The work order subject becomes crm.lead.name. Work order status (Scheduled, In Progress, Completed, Cancelled) is mapped to Odoo crm.stage names via a value-mapping table — New maps to your Odoo 'New' stage, In Progress maps to 'Qualification' or 'Proposal' depending on your stage names, and Completed maps to 'Won'.

Aidoo Mobile work-order priority (Low, Medium, High, Urgent) has no native Odoo CRM equivalent. We create a custom Char or Selection field (x_priority) on crm.lead and populate it from the source priority value. If Odoo Studio is available, this can be a Selection field; otherwise it is a Char field with values stored as text.

Service tickets in Aidoo Mobile capture issue description, reported date, and resolution notes. The primary issue description is stored in crm.lead.description (plain text). Detailed ticket history, internal notes, and resolution comments are stored as Odoo mail.message records linked to the crm.lead, preserving the original timestamp and author.

Aidoo Mobile assets (equipment name, serial number, model, installation date) do not have a native Odoo CRM equivalent. We map assets to product.product records if Odoo Inventory is active, or to custom Char fields on res.partner (x_asset_serial, x_asset_model) if only the CRM app is in use. We flag which approach during the planning phase.

Aidoo Mobile technician assignment on a work order maps to crm.lead.user_id in Odoo. Resolution is by email match: if a technician email in Aidoo Mobile matches a res.users.login email in Odoo, we assign crm.lead.user_id directly. Unmatched technicians are flagged before migration and assigned to a fallback user or imported as res.users records first.

The original work order creation timestamp in Aidoo Mobile is preserved as crm.lead.create_date in Odoo. Odoo's own create_date reflects the migration timestamp, so we store the source create date in a custom field (x_original_create_date) for reporting continuity on historical records.

Free-text notes attached to Aidoo Mobile customers or work orders are migrated as mail.message records on the corresponding res.partner or crm.lead in Odoo. Each message carries the original author name, creation timestamp, and body text. This preserves audit history without modifying the Odoo note layout.

Aidoo Mobile custom fields and custom objects not covered by the standard mappings above are migrated as Odoo custom fields (x_ prefixed Char, Selection, or Text fields) on the closest Odoo model. If the source custom object is entity-like with multiple records, we create a dedicated Odoo model via module development and populate it via XML-RPC after the core migration.

File attachments stored in Aidoo Mobile (photos, signed forms, equipment images) are downloaded, re-hosted in Odoo's ir.attachment model, and linked to the corresponding res.partner or crm.lead record via res_model and res_id. The original filename, MIME type, and file content are preserved and stored in Odoo's filestore for retrieval through the standard attachment API.