Migrate from FRONTU to Odoo CRM

Frontu Customer maps to Odoo res.partner as a company-type partner. Frontu's company-level fields (name, industry, website) map directly to res.partner name, industry_id, and website. Customer addresses in Frontu become child res.partner records (contact-type) linked to the company partner via partner_latitude/longitude address fields. Multi-site customers generate multiple child contacts.

Frontu Site (a physical service location attached to a Customer) maps to a child res.partner record with type='contact' under the parent Customer partner. Site-specific address, coordinates, and site-code fields become custom Char fields on the child partner record. This preserves the customer-site hierarchy that Frontu uses for dispatch routing.

Frontu WorkOrder maps to Odoo crm.lead in opportunity mode (type='opportunity'). Work order status (Pending, In Progress, Completed, Cancelled) maps to crm.lead stage_id via value_mapping against Odoo's stage names. The WorkOrder description becomes crm.lead name; the linked Customer site becomes the partner_id on the opportunity.

If the Frontu WorkOrder has billable line items, service-type fields, or equipment references that crm.lead cannot hold natively, we create a custom crm.work.order model via Odoo Studio. This custom object links to res.partner for the customer site and stores WorkOrder-level custom properties. Whether to use crm.lead or a custom object is decided during the sample migration review.

Frontu task records with status, description, and timestamp map to Odoo crm.activity entries linked to the parent WorkOrder crm.lead. The task create_date, write_date, and assigned technician are preserved in custom datetime and user fields on the activity record. Task attachments migrate to ir.attachment linked to the same crm.lead.

Frontu Technician records map to Odoo res.users by email address match. Technician's name, email, and phone become res.users name, login (email), and phone. Unmatched technicians are flagged before migration — either the Odoo user is created first or the technician's tasks are assigned to a fallback Odoo user specified by your admin.

The Odoo res.users record automatically creates a linked res.partner record (type='private') for the user. Frontu technician contact details (phone, email) are accessible on this linked partner. This allows Odoo CRM activities to show technician attribution on tasks and work orders.

Frontu file attachments on work orders (photos, PDFs, signed forms) are downloaded from Frontu storage and re-uploaded to Odoo as ir.attachment records. Each attachment is linked to the corresponding crm.lead (WorkOrder) or res.partner (Site) record. Odoo's ir.attachment 25MB per-file limit applies — large files are flagged for chunked upload.

Frontu custom properties on WorkOrder (service type codes, billing category, equipment serial numbers) are mapped to custom fields on the target crm.lead or crm.work.order model. Odoo Studio creates these as x_ prefixed fields or via ir.model.fields insertion depending on the target model. Value pick-list types in Frontu map to Odoo selection fields with value-by-value mapping.

Frontu custom properties on Customer records (industry sub-codes, service-tier flags, contract numbers) become custom fields on res.partner. Odoo Studio is used to define these fields before migration so the import process can populate them. Fields that are pick-lists in Frontu become Odoo selection fields with identical option sets.

Frontu Teams (groupings of Technicians for dispatch) map to Odoo crm.team records. Each crm.team gets a name matching the Frontu team and the resolved Odoo res.users members are assigned as team members via crm.team.member records. Teams without a direct Odoo equivalent are created as crm.team records before migration.

Frontu logs status transitions on work orders with timestamps and the triggering technician. These are captured as Odoo mail.message records on the crm.lead with subtype='comment' and the original status transition text preserved in the message body. This gives Odoo users a full audit trail of work order state changes without requiring a custom model.

Frontu's real-time scheduling, dispatch board, and route-optimization features have no Odoo CRM equivalent. This workflow must be rebuilt using Odoo Project (for task planning) or a third-party Odoo scheduling module. We document the Frontu scheduling rules and dispatch logic as a rebuild reference for your Odoo implementation team but do not carry this data forward.