Migrate from Planado to Odoo CRM

Each Planado job maps to one Odoo crm.lead record. The job name becomes the lead name, job description maps to crm.lead description, and the job status drives the crm.lead stage value. FSM-specific fields like GPS coordinates, checklist responses, and schedule assignments are preserved as custom fields on crm.lead — Odoo CRM has no native field-service equivalent.

Planado clients map to Odoo res.partner records with partner_type set to 'contact' for individual contacts and 'company' for organizations. Client address fields (street, city, zip, country) map directly to res.partner address fields. The primary contact email and phone map to email and phone on res.partner.

Planado task assignments on a job map to Odoo mail.activity records linked to the crm.lead. The activity type (call, email, meeting) is derived from the task type in Planado, and the assigned field worker is matched to a res.users record by email to set the activity user_id.

Planado employee records map to Odoo res.users so that task assignments and activity logs in Odoo carry the correct owner. The employee's name and email map to res.users name and login; phone is stored in the related res.partner contact record. Unmatched employees are flagged before migration.

Files attached to Planado jobs (photos, signed forms, documents) migrate to Odoo ir.attachment records with res_model set to 'crm.lead' and res_id set to the target lead ID. The original filename and file content are preserved; inline images are re-hosted in Odoo's filestore.

Planado custom fields on jobs that have no Odoo CRM equivalent (GPS latitude/longitude, checklist responses, dependency chains) are created as custom fields on crm.lead via Odoo Studio or Settings > Technical > Custom Fields before ingestion. FSM-specific field labels are prefixed with 'FSM_' to distinguish them from standard CRM fields.

Planado checklist items are stored as a structured text blob in Planado. Odoo CRM has no native checklist model, so checklist responses are consolidated into a single custom text field (Checklist_Responses__c) on crm.lead. Teams that need structured checklist lines can recreate them in Odoo Studio after migration using a one2many relation.

Recurring job patterns in Planado (daily, weekly, custom intervals) have no Odoo CRM equivalent — Odoo Projects can model recurring tasks, but the CRM module itself does not support recurrence. Recurrence rules are preserved as a custom text field on crm.lead for reference.

The site address associated with a Planado job maps to the client res.partner address fields. If the site is distinct from the client billing address, it is stored as a secondary contact address on the res.partner record with address_type set to 'other'.

Planado job cost and revenue values map to crm.lead expected_revenue. Odoo CRM uses this field for pipeline value calculations and forecasting. Currency is stored in a custom field since Odoo's base currency is set at the company level, ensuring that monetary values reflect the correct currency for each lead's region.

Labels applied to Planado jobs map to crm.tag records, which can be linked to crm.lead via the tag_ids many2many relation. Tags enable Odoo CRM reporting by category even when the underlying FSM data is stored in custom fields, allowing sales and operations teams to filter leads, generate segmented views, and track performance by job type or service line.