Migrate from WorkBuddy to Odoo CRM

WorkBuddy customers (company-level B2B records) map directly to Odoo res.partner with partner_type='contact' and is_company=True. The WorkBuddy customer name becomes partner.display_name, address fields map to street, city, state_id, country_id, and zip. Any WorkBuddy customer notes migrate to res.partner.comment as plain text. WorkBuddy customer-specific custom properties (e.g., ABN, industry segment) become custom fields on res.partner.

WorkBuddy contacts (individual people linked to a customer) map to Odoo res.partner records with is_company=False and parent_id pointing to the partner record created from the WorkBuddy customer. Name fields split into lastname and firstname using WorkBuddy's name field. Email, phone, and mobile map directly. WorkBuddy contact custom properties migrate as res.partner custom fields.

WorkBuddy job records map to Odoo crm.lead in lead mode (type='lead'), not opportunity mode. The job title becomes crm.lead.name; job description maps to crm.lead.description. Job status from WorkBuddy maps to a custom picklist field Job_Status__c on crm.lead and also influences the crm.lead.stage_id by routing statuses to Odoo stage names defined per migration plan. Job type (e.g., Electrical, Plumbing) migrates as a custom field crm.lead.x_workbuddy_job_type. If the WorkBuddy job is tied to a quote, the opportunity conversion path is used after migration.

WorkBuddy quotes (pricing proposals attached to a job) map to Odoo sale.order in draft/quotation state. Quote line items map to sale.order.line records linked to a product in the Odoo product.product catalog; if no matching product exists in Odoo, a placeholder product is created. Quote total, taxes, and discounts are preserved on the sale.order.amount_total and sale.order.line.price_unit / price_subtotal fields. The Odoo version determines whether the model name is sale.order (v16) or sale.quotation (v17+).

WorkBuddy asset records (equipment or property items tracked per job) map to Odoo stock.production.lot for inventory-tracked items or maintenance.equipment for service-maintenance records. The mapping choice depends on how the Odoo instance is configured. Asset name maps to lot_name or name; asset serial number maps to ref; WorkBuddy asset notes migrate to the description field on the target model. If Odoo's maintenance app is not installed, assets migrate to a custom asset model defined in the migration plan.

WorkBuddy timesheet entries (hours logged per job per technician) map to Odoo account.analytic.line records linked to the account.analytic.account associated with the WorkBuddy job. The entry date, duration (hours), user_id (technician), and description map to date, unit_amount, user_id, and name respectively. If Odoo's timesheet app is active, records appear in the timesheet dashboard; otherwise they are available as analytic entries for reporting.

WorkBuddy user IDs (technicians, dispatchers, admin staff) are resolved by email address match against Odoo res.users records. FlitStack creates a mapping table of WorkBuddy user ID to Odoo res.users.id. If a WorkBuddy user has no matching Odoo user, their records are assigned to a fallback Odoo user (typically the migration admin) and flagged in the audit log for post-migration reassignment. Odoo does not create users from scratch during migration — Odoo user provisioning must happen before migration or concurrently.

WorkBuddy custom properties on job records — safety compliance tags, service-area codes, subcontractor assignments — do not exist in Odoo's standard crm.lead schema. FlitStack maps each custom property to a custom field on crm.lead (x_ prefixed by Odoo convention), with field type matching the source data type: Char for text, Selection for picklists, Boolean for flags, Date/Datetime for timestamps. The Odoo admin must pre-create these fields before migration or approve FlitStack's schema-creation module as part of the migration package.

WorkBuddy file attachments (photos, PDFs, signed documents) linked to jobs or contacts migrate as Odoo ir.attachment records with res_model set to the target Odoo model (crm.lead or res.partner) and res_id set to the migrated record's Odoo ID. The file binary content is downloaded from WorkBuddy and re-uploaded to Odoo's filestore via the /web/binary/attachment route or direct filestore write. Attachment names and create dates are preserved. Large files exceeding Odoo's default size limit are flagged for manual handling.

WorkBuddy workflow rules (automatic job status transitions, notification triggers, scheduling rules) are platform-native automation constructs that have no Odoo equivalent at the data layer. FlitStack exports the workflow definitions as a JSON reference file containing rule names, trigger conditions, and action sequences. This file is handed to the Odoo admin or consultant to rebuild in Odoo Studio or as a custom module using Odoo's ir.actions.server and base.action.rule models.

WorkBuddy subcontractor management links a job to one or more subcontractor contacts. Odoo CRM does not have a native subcontractor object — FlitStack maps each subcontractor to a res.partner record (created or matched by email) and creates a custom many2many field x_workbuddy_subcontractors on crm.lead linking the job to the subcontractor partner records. If Odoo's purchase module is installed, purchase orders can be raised against the subcontractor partner after migration.

WorkBuddy safety and compliance records (SWA forms, site risk assessments, permits) attached to jobs do not map to any standard Odoo object. FlitStack migrates them as ir.attachment records linked to the crm.lead and also creates a custom field x_safety_compliant (Boolean) and x_safety_notes (text) on crm.lead for quick filtering. Full safety document content is preserved as attachments; the compliance status flag is searchable in Odoo.