Migrate from MotionOps to Odoo CRM

MotionOps customers map directly to Odoo res.partner records. The partner functions as both contact and company depending on the type field (contact vs. company). Primary address, email, phone, and website map to Odoo standard fields. MotionOps customer IDs are preserved in a custom field for traceability.

MotionOps company records with multiple linked customers map to res.partner with type='company'. Child contacts are created as res.partner records with parent_id pointing to the company partner. The Odoo parent-child hierarchy mirrors MotionOps company-to-customer linking, preserving the relationship tree where company-level data (industry, tax ID, payment terms) applies to all child contact records automatically.

MotionOps jobs convert to Odoo crm.lead records in opportunity mode. The job name becomes the opportunity name. Job status (Scheduled, In Progress, Completed, Cancelled) maps to Odoo stage_id values via per-pipeline value mapping. Active jobs with no close date set stage_id to the first Open stage.

MotionOps jobs with line items, proposals, or estimates merge into Odoo sale.order records. The customer partner links to res.partner. Job description maps to sale.order.note. Line items map to sale.order.line with product, quantity, and price. Historical proposals become confirmed sale orders if they have a signed status.

MotionOps proposals map to Odoo sale.order records in draft (quotation) state. The proposal total maps to amount_total. Proposal validity dates map to validity_date. If the proposal was accepted, the sale.order state advances to sent or sale based on signature status in MotionOps.

MotionOps job status values (New, Assigned, En Route, On Site, Completed, Invoiced, Cancelled) require value-by-value mapping to Odoo CRM stage names. We recommend creating one Odoo pipeline per MotionOps job status group to keep Kanban columns clean. Stage probabilities are set per stage in Odoo pipeline configuration.

MotionOps technician assignments map to Odoo res.users records matched by email. The assigned user populates crm.lead.user_id. Unmatched technicians are flagged before migration — either invited to Odoo first or assigned to a fallback user. Team assignment (crm.lead.team_id) resolves from MotionOps route or service area.

MotionOps job notes and technician comments map to crm.lead.description for the main narrative summary. Timestamped internal notes and chronological comments migrate as Odoo mail.message records attached to the lead, preserving the full conversation history, author attribution, and timestamp for each entry. This maintains complete audit trail on the Odoo lead chatter.

MotionOps custom fields on jobs (e.g., service_type, permit_required, property_access_instructions) require Odoo custom fields created before migration. We use Odoo's custom field IR model so fields appear in the Kanban and form views. Multi-select custom fields map to Odoo char or many2many tags depending on usage.

MotionOps customer-level custom fields (e.g., billing_terms, preferred_payment_method, service_contract_type) map to res.partner custom fields created via Odoo's Settings > Technical > Custom Fields interface. These fields are created before the migration run so the fields exist during the import process, ensuring all custom property data transfers correctly without null values or skipped records.

MotionOps job photos, signed forms, and attached documents download and re-upload to Odoo ir.attachment records linked to the corresponding crm.lead. Files are stored in Odoo's filestore using the attachment naming convention. Maximum file size is 25MB per attachment in Odoo Community edition. All attachments retain original filenames and MIME types for identification.

MotionOps invoices map to Odoo account.move records in the Odoo Accounting app. Customer invoice linkage uses res.partner to maintain referential integrity. Invoice line items map to account.move.line records with proper account_id assignments. Invoice status (Paid, Overdue, Void) maps to state values on account.move. The Odoo Accounting app must be installed and configured for this mapping to function.

MotionOps QuickBooks Online sync settings have no direct Odoo equivalent. We preserve the sync configuration details including customer mappings, invoice templates, tax code associations, payment term rules, and宋代 synchronisation parameters as a JSON reference file. Your Odoo consultant uses this file to rebuild equivalent settings using Odoo's Accounting app configuration, chart of accounts, and fiscal position setup.

MotionOps automations including auto-assign rules by zip code, SMS notifications on status changes, and custom trigger conditions do not migrate automatically. We export all automation definitions in structured JSON format with trigger events, conditions, and actions documented. Your Odoo administrator can rebuild these automations using Odoo Studio for visual configuration or server actions with Python code for complex workflow logic in Action Rules.