Migrate from Ascora to Odoo CRM

Ascora contact maps to res.partner (for customers) and crm.lead (for unqualified prospects). Active jobs linked to a contact route that contact to res.partner; contacts with no jobs and no quotes become crm.lead records. The contact's email and phone are stored on res.partner as email and phone; the contact's name splits into firstname and lastname on res.partner.

Ascora companies with a ABN/ACN or business name map to res.partner with company_type set to 'company'. Child contacts (site contacts, billing contacts) become child contact_address records under the parent res.partner. Multi-site companies in Ascora with separate contacts per site generate multiple contact_address records under one parent.

Each Ascora site with a service address becomes a res.partner contact_address child record of the primary customer res.partner. Site name maps to contact_name on the address record. Site-specific notes and instructions map to comment on the address record. Sites without an address are flagged for manual review before the migration commits.

Ascora jobs migrate to crm.lead as the base record — job name becomes the opportunity name, job description becomes the opportunity description, and job status maps to the crm.lead stage pick-list. If the job has a linked project or multi-phase scope, Odoo project.project and project.task records are created and linked via the project_id field on crm.lead. Task names derive from the job's line items or work phases.

Ascora job status values (Scheduled, In Progress, On Hold, Completed, Invoiced) map to Odoo crm.lead stage values using a value-by-value lookup table. Completed jobs map to the Won stage; Invoiced jobs map to Won with an invoice_id flag set. Jobs without a closeable status become crm.lead in the New or Qualification stage.

Ascora quotes become Odoo sale.order records with their original quote number preserved in the Odoo name field. Quote line items map to sale.order.line records linked by order_id. Custom terms and notes from the Ascora quote description field map to sale.order.note (displayed on Odoo quotation reports). Quote expiry date maps to validity_date on the sale.order; acceptance status maps to state transitions.

Ascora quote status values (Draft, Sent, Accepted, Declined, Expired) map to Odoo sale.order state values: Draft to draft, Sent to sent, Accepted to sale or done depending on whether confirmation has run, Declined to cancel, Expired to cancel with an expiry flag. A custom field x_quote_original_status preserves the Ascora value for audit purposes.

Ascora custom properties on contacts (trade licence number, insurance policy reference, preferred contact method) require Odoo custom field creation via Settings > Technical > Database Structure > Fields before migration runs. Each custom field is created as a Char, Selection, or Boolean type on res.partner depending on the Ascora data type. The migration plan flags any custom fields that reference pick-list value sets for value-mapping setup.

Ascora custom properties scoped to jobs (work type classification, site access instructions, crew assignment notes) map to custom fields on crm.lead and project.task. Trade-type classifications that drive scheduling rules in Ascora are stored as custom Selection fields on crm.lead for reporting segmentation, since Odoo scheduling logic is handled in the project module and must be rebuilt manually.

Ascora equipment records split into two Odoo objects: if the equipment is a billable product or part, it maps to product.product with the equipment name as product name and the service history stored as a text note. If Odoo Maintenance app is active, equipment maps to maintenance.equipment for asset tracking. Equipment linked to sites generates a note on the corresponding contact_address record referencing the asset.

Ascora file attachments on jobs (photos, signed forms, compliance certificates) re-upload to Odoo as ir.attachment records linked to the corresponding crm.lead via res_model = 'crm.lead' and res_id = the lead ID. Original filenames are preserved in the name field. Attachments without a parent job (orphaned files) are attached to the contact res.partner record instead.

Ascora job owners and contact owners resolve by email match against res.users in Odoo. Unmatched owners are flagged in the migration report — your team either invites them as Odoo users first or assigns their records to a fallback user. This prevents orphaned records where crm.lead.create_uid or user_id cannot resolve.