Migrate from Oracle Field Service Cloud to Odoo CRM

Oracle Activities map to Odoo crm.lead records. Activity status (scheduled, in progress, completed, cancelled) maps to Odoo lead stage names. Activity type, work order ID, and scheduled start/end times are stored as fields on the lead. If the activity represents a closed sale rather than a service event, it may instead map to sale.order — your team decides per activity type.

Oracle Customer accounts map directly to Odoo res.partner records with type='company'. Oracle's customer name, phone, email, and industry classification map to the corresponding res.partner fields. Oracle Customer IDs are stored in a custom field on the partner record for traceability.

Oracle Location records attached to a Customer map to address records on the res.partner (company). The location's address, city, state, postal code, and country map to the partner's address fields. Latitude/longitude coordinates are stored as custom float fields on the partner if geolocation tracking is needed in Odoo.

Oracle Equipment records represent customer-owned assets (HVAC units, meters, appliances). These map to Odoo stock.production.lot if the Odoo Inventory app is installed; otherwise they are stored as custom fields on the related res.partner. The equipment's serial number, model, install date, and warranty expiry map to lot fields or custom fields on the partner record.

Oracle Resources (field technicians) map to Odoo res.users if they need CRM access, or hr.employee if the Human Resources app is installed. Resource email, name, and skill set map to the corresponding user/employee fields. Unassigned or contractor resources are flagged before migration so your team can provision or archive them in Odoo.

Oracle Route records have no native Odoo equivalent. Route name, scheduled date, and optimization priority map to a custom Char field on crm.lead and/or a crm.tag for reporting. Route-level scheduling windows are stored as text notes in the lead description field. If route-level reporting is critical, a dedicated Odoo project or crm.team structure can be designed during the migration plan phase.

A Route Plan contains ordered activities with time windows and travel segments. Each activity in the plan maps to its own crm.lead. The sequence order is stored as an integer field on the lead. Travel time between stops is recorded as a custom note. If your team uses Odoo Project to manage field dispatch, the plan maps to project.task records instead — your admin decides the target model before migration.

Oracle attachments on Activities (photos of completed work, signed forms, meter readings) map to Odoo ir.attachment records with res_model='crm.lead' and res_id pointing to the migrated lead. Files are re-uploaded to Odoo's filestore. Signature images from Oracle's completion forms map to ir.attachment and can be displayed on the lead form view if needed.

Oracle records status transitions and technician notes on Activities. These map to Odoo mail.message records on the crm.lead ( Chatter messages) with the original timestamp and author preserved. High-importance notes are appended to the lead description field for visibility without opening the activity log.

Oracle OFSC custom fields map to Odoo custom fields with x_ prefix on the corresponding model. Field type mapping: text → char, number → float or integer, date → date, picklist → selection, checkbox → boolean. Custom field definitions are created in Odoo before migration runs so data lands in the correct schema.

Oracle OFSC quota groups and capacity intervals (defining technician availability windows) have no Odoo CRM equivalent. FlitStack preserves the last-known quota configuration as JSON text in a custom field on hr.employee for reference. Scheduling logic must be rebuilt in Odoo's automation rules or a third-party field service app.

Oracle OFSC SLA policies and automated business rules (time-to-assign, escalation triggers, routing logic) are not data records and do not export. They must be rebuilt as Odoo automation rules (ir.actions.server) or in Odoo's Studio workflow builder. FlitStack exports the rule definitions as a reference document for your Odoo admin.