Migrate from Texada Software to Odoo CRM

Texada customers map to Odoo res.partner records. Name, email, phone, and address fields transfer directly using direct mapping. Partner type (customer flag) maps to Odoo's partner_type commercial relationship field. Parent-company hierarchies in Texada become res.partner parent_id links in Odoo, preserving organizational structures. Credit limits and customer ranking transfer to Odoo's credit_limit and customer_rank fields respectively.

Texada rental and sales contracts become Odoo crm.lead records in the Opportunity stage. Contract number maps to name, total contract value maps to Odoo's expected_revenue (or a custom monetary field), and contract status (Active/Expired/Pending) maps to crm.lead stage_id through a value-mapping table. Contract owner resolves via email match to Odoo res.users.

Each Texada contract contains multiple rental or sales line items including equipment, parts, and labor. These merge into Odoo sale.order records linked to the corresponding opportunity (contract). Line-item descriptions, quantities, and rates map to Odoo sale.order.line fields. Pricing rules require Odoo product.pricelist configuration to handle Texada's pricing complexity.

Texada work orders split by type: service work orders route to Odoo project.task (with project_id linking to a service project), while warranty or billing-related work orders that track revenue potential become crm.lead records. Work order status maps to task stage or lead stage via value mapping tables. Assigned technician IDs resolve by email match to Odoo res.users.

Texada equipment inventory and tracked assets migrate to Odoo stock.production_lot for serialized assets or product.product for non-serialized inventory. Serial numbers, equipment category, and current status transfer. Rental-specific fields (daily rate, minimum rental period) become custom fields on the product record. Equipment status becomes a custom x_equipment_status selection field.

Texada product and parts catalog items map to Odoo product.product (for variants) and product.template (for the product definition). Product name, SKU, description, cost price, and sales price transfer directly. Texada's vendor parts catalog relationships map to Odoo's seller_ids on the product record, preserving supplier information.

Texada rental billing transactions including cycle billing invoices and cash receipts migrate to Odoo account.move records in the 'out_invoice' type. Invoice lines link to the original sale.order and contract reference for full audit trails. Texada's AR aging data becomes Odoo account.move line entries with proper account allocation per the chart-of-accounts mapping.

Texada cash receipts and customer payments map to Odoo account.payment records. Payment date, amount, payment method, and linked invoice (via reconcile field) transfer directly. Unmatched receipts are flagged for manual review before migration commits to prevent orphaned payments. Payment method maps to Odoo account.journal records.

Texada employees and technicians migrate as Odoo res.users records with the employee flag set. Employee name, email, and division map directly to Odoo user fields. Texada WorkFlow assignment rules (which assign work orders to technicians) require Odoo automation rules to be rebuilt post-migration using Studio or server actions.

Texada's customer hierarchy (parent/child company relationships) maps to Odoo res.partner parent_id field. The hierarchy depth is preserved — multi-level parent chains in Texada become nested parent_id links in Odoo. Primary contact designation maps to Odoo's contact_type field to preserve which contact is primary at each organization level.

Texada documents attached to contracts (PDFs, images, signed agreements) migrate as Odoo ir.attachment records. Each attachment is linked to the corresponding res.partner (for customer docs) or crm.lead (for contract docs) via res_model and res_id. File content is base64-encoded and stored in Odoo's filestore for secure access post-migration.

Texada custom properties including cycle billing flags, alternate vendor numbers, labor special pricing codes, and custom picklist values require Odoo ir.model.fields custom field creation before migration. Each custom field's ttype (char, selection, float, date) is determined from Texada's field definition API, and selection options are mapped value-by-value for complete fidelity.