Migrate from JobTread to Odoo CRM

JobTread Customers map directly to Odoo res.partner records. The partner's type field is set to 'contact'; the customer_rank flag is set so the record appears in Odoo's customer list. Parent-company hierarchies in JobTread map to parent_id on res.partner.

JobTread Customer Contacts become Odoo res.partner records with type='contact' and a parent_id pointing to the Customer partner record. The contact's name, email, and phone fields map directly. JobTread's N:N contact-to-company support is handled by Odoo's address_ids on the parent partner.

JobTread Jobs become Odoo Opportunities (crm.lead with type='opportunity'). The Job name maps to the Opportunity name; job amount maps to Odoo's planned_revenue or a custom amount field. Odoo's pipeline and stage_id replace JobTread's pipeline and job stage concept.

JobTread pipeline stages map value-by-value to Odoo crm.stage records. Each stage needs probability and is_won/is_lost flags set to match the deal lifecycle. Stage sequence order is preserved from JobTread's pipeline configuration.

JobTread Cost Items map to Odoo product.template records. For cost items with pricing, list_price and standard_price are populated from JobTread's unit cost and markup fields. The product's type (service vs. product) is inferred from JobTread's cost item category.

JobTread Vendors map to Odoo res.partner records with supplier_rank=1 and type='contact'. The vendor's name, email, and phone map directly. JobTread's vendor-specific fields (e.g., trade, insurance info) become custom fields on the res.partner record.

JobTread Vendor Contacts become Odoo res.partner child contacts linked to the Vendor partner via parent_id. Their name, email, and phone fields map directly, matching the same pattern as Customer Contacts.

JobTread custom fields across all objects (Customers, Contacts, Jobs, Vendors, Cost Items, Locations) require Odoo custom fields created via Studio or directly on the model. Field type mapping: text → char, number → float or integer, date → date, dropdown → selection. The custom field must exist in Odoo before migration loads the corresponding values.

JobTread Locations map to Odoo delivery addresses on the res.partner record (stored in partner_id's address fields). If the migration includes inventory management, Locations with warehouse semantics map to Odoo stock.location records.

JobTread file attachments on Jobs, Cost Items, and Customer Contacts are re-uploaded to Odoo's ir.attachment table, linked by res_model pointing to crm.lead, res.partner, or product.product and res_id set to the destination record ID. File size limits from Odoo's ir_attachment_max_file_size apply.

JobTread notes on Jobs and Customer Contacts map to Odoo's note.note records. The note body text and create date are preserved. Notes are linked to the target Odoo record via res_model and res_id on the note record.

JobTread workflows (triggers, filters, and automated actions) do not have an Odoo equivalent because Odoo's automation engine uses server actions and ir.cron jobs with a different event model. We export the workflow definitions as a JSON reference file for your Odoo admin to rebuild using Odoo Studio or code-based actions.

JobTread owner IDs are resolved by email matching against Odoo res.users. Any JobTread owner whose email does not match an existing Odoo user is flagged before migration — you can invite them to Odoo or assign their records to a fallback owner.

JobTread budget templates and selection templates are construction-specific structures with formula-driven cost calculations that have no direct Odoo CRM equivalent. The underlying cost items migrate as product templates, but the template structure (with selections, formulas, and parameters) must be rebuilt in Odoo using sale.order.line configuration or a third-party construction module.