Migrate from Less Paper Co. to Odoo CRM

Less Paper Co. work orders map directly to Odoo crm.lead as opportunities. The original work order number (e.g., WO-2024-0042) migrates as x_fsm_work_order_id on the opportunity record. FlitStack creates this custom Char field on crm.lead before migration. Work order status maps to crm.stage via value-by-value mapping per the Less Paper Co. status options.

Each work order's appointment record splits into an Odoo mail.activity linked to the crm.lead. The technician name, scheduled time window, and service address store as custom fields (x_technician_name, x_time_window, x_service_address) on the activity. FlitStack exports the scheduling CSV separately and attaches each row to the matching opportunity via the work order number.

Less Paper Co. customer records map 1:1 to Odoo res.partner as companies. FlitStack imports the company name, billing address, phone, email, and industry as the corresponding res.partner fields. Each customer record receives a partner_id in Odoo that the related opportunities reference via partner_id on crm.lead.

Less Paper Co. locations under a customer map to Odoo res.partner records with type='other' linked to the parent company partner via parent_id. The service address, site name, and location-specific notes store as address fields on the child partner record. FlitStack deduplicates locations by comparing the full address string before creating a new partner record.

Equipment tracked in Less Paper Co. (HVAC units, machinery, systems under service contract) migrate as Odoo product.product records. The equipment type maps to categ_id (product category), and service history notes attach as an Odoo note on the product record. Serial numbers and model numbers store as default_code and description fields on the product.

Less Paper Co. work order line items (parts, labor rates, service fees) map to sale.order.line on a quotation linked to the opportunity. Each line item description, quantity, and unit price migrates. If the migration includes Odoo's sale module, FlitStack generates a draft quotation under the opportunity; otherwise line items store as custom fields on the opportunity.

Less Paper Co. payment records (amounts paid on-site by the technician) migrate as Odoo account.move records with move_type='in_invoice' to represent out-of-pocket expenses. The vendor (the technician's employer or the field company) becomes the partner on the vendor bill. FlitStack flags any payments linked to inventory items for manual entry since those require Odoo's stock.account_move_links.

Less Paper Co. scheduling records (technician name, time window, service address, job type) migrate as Odoo mail.activity records with activity_type='submission' or a custom type created for the migration. The technician name and appointment window store as custom fields on the activity since Odoo's activity model does not natively include technician or window fields.

Less Paper Co. work order completion notes and technician check-in logs migrate as Odoo mail.message records attached to the crm.lead. FlitStack preserves the original timestamp, author name (from the technician record), and note body. Rich-text formatting is simplified to plain text during import.

Files and photos attached to Less Paper Co. work orders (before/after photos, signed PDFs, inspection reports) re-upload to Odoo as ir.attachment records linked to the crm.lead via res_model='crm.lead' and res_id set to the opportunity ID. FlitStack downloads each file from Less Paper Co.'s storage, re-uploads to Odoo's filestore, and creates the attachment record with the original filename preserved.

Any Less Paper Co. custom field on a work order or customer that has no Odoo standard equivalent is created as an x_ prefixed custom field on crm.lead or res.partner before migration. FlitStack generates the Odoo custom field definition (field type, required flag, pick-list values) from the source schema and includes it in the pre-migration Odoo setup plan.