Migrate from Uptick to Odoo CRM

Uptick customer records (name, email, phone, address, company name) map directly to Odoo res.partner. Uptick distinguishes between commercial customers and site locations — both become res.partner records with partner_type set to 'contact' for individuals and 'company' for commercial entities. Parent-company hierarchies in Uptick map to the parent_id field on res.partner.

Uptick assets (fire extinguishers, suppression systems, emergency lights) map to Odoo stock.production.lot records under Inventory > Lots/Serial Numbers. Asset Type grouping becomes a custom lot_name field or product linking. The asset's current service status, last inspection date, and next due date migrate as custom fields on the lot record. For recurring service schedules, maintenance.request records are generated in Odoo's maintenance.app.

Uptick Asset Types (e.g., '2.5kg Dry Chemical Extinguisher') define the servicing standard and inspection frequency per asset. These merge into Odoo product.product records as service products linked to the maintenance.app via maintenance.period. The inspection frequency (e.g., every 6 months) becomes a maintenance周期 rule in Odoo's maintenance module. Each Uptick asset instance links to its corresponding product.product service type.

Uptick work orders split by type: corrective jobs (breakdowns, emergency calls) map to maintenance.request records in Odoo's maintenance.app with the responsible technician assigned via user_id and maintenance_team_id. Planned preventive maintenance jobs originating from Uptick's inspection schedule map to project.task records under a dedicated maintenance project in Odoo's project.app, preserving job description, labor hours, and parts used.

Uptick quotes with line items map to Odoo sale.order. Each Uptick quote line (material, labor, equipment, subcontracted, expense type) becomes a sale.order.line with the correct product.product and quantity. Quote status (Draft, Sent, Accepted, Lost) maps to Odoo sale.order state transitions. Uptick's default discount and tax rules apply via Odoo's fiscal_position and pricelist settings.

Uptick invoices migrate to Odoo account.move records of type 'out_invoice'. The invoice lines (products, labor, materials) map to account.move.line entries. Uptick's payment status and outstanding balance map to Odoo's payment_state field. Historical invoices are created as posted (validated) records so Odoo's accounting reports reflect the migrated financial history accurately.

Uptick product catalog entries (materials, labor rates, equipment rental, subcontracted services) map to Odoo product.product records with the correct type ('service' for labor and subcontracted, 'product' for materials and equipment). Uptick's cost_price and estimated_labour_minutes fields migrate to Odoo's standard_price and sale_delay on product.product so margin reporting works in Odoo Sales.

Uptick technician and staff records map to Odoo res.users. Email addresses serve as the match key for user resolution. Unmatched technicians are flagged before migration and assigned to a fallback maintenance team owner. User rights and portal access in Odoo must be configured separately post-migration — Uptick security groups do not transfer automatically.

Uptick site records (physical locations where assets live) map to Odoo stock.location entries under the warehouse/location hierarchy. The site's address fields migrate to a child res.partner record of the customer company with type 'other address', enabling the Odoo maintenance.app to track work orders by physical location. Multi-floor or zone structures within a site become child stock.location records.

Uptick attachments and inspection photos linked to assets or work orders migrate as ir.attachment records in Odoo, linked via res_model and res_id to the corresponding stock.production.lot or maintenance.request record. Odoo's default 25MB per-file limit applies; larger files are flagged for compression before import. Images embedded in Uptick notes are extracted and stored as separate attachments.

Uptick supplier records map to res.partner with supplier_rank set to 1 and customer_rank 0. The supplier's contact details, payment terms, and purchase currency migrate as fields on the partner record. In Odoo, these suppliers become usable in the purchase.app for buy-and-resell workflows or in the maintenance.app for subcontracted service sourcing.