Migrate from MobiWork to Odoo CRM

MobiWork Customer records map directly to Odoo res.partner with type='contact' and customer_rank set to a positive value. The partner's address, phone, email, and website fields migrate as direct field-to-field assignments. MobiWork's 'Customer Since' date maps to Odoo's date field or a custom partner field.

MobiWork Prospects map to res.partner with customer_rank=0 (not yet a customer). If the Prospect has a company name, Odoo sets is_company=True and creates a child contact record. If Prospect has only a person name, it becomes an individual res.partner contact. The distinction is stored as a custom field on the partner for reporting clarity.

Each MobiWork Work Order becomes an Odoo crm.lead opportunity record. The lead's name field holds the Work Order description or ticket number. Custom fields on crm.lead store the original Work Order ID, assigned technician (linked via res.users), job status, and parts used. The migration preserves the parent Customer link via the lead's partner_id many2one.

MobiWork status values (Scheduled, In Progress, On Hold, Completed, Invoiced, Cancelled) map to Odoo crm.stage records defined per crm.team. We create stages matching the source labels and set sequence order. Probability values on stages are applied from Odoo's defaults unless the source data contains historical win-rate data to override them.

MobiWork Quotes migrate as Odoo sale.order records in the 'Quotation' state (sale.sale.sale_order). Line items map to sale.order.line with product_id, product_uom_qty, price_unit, and discount. Quote expiration dates map to sale.order.validity_date. Accepted quotes are flagged so they can be confirmed as sale orders post-migration.

MobiWork invoices and progressive billing entries map to Odoo account.move records of type='out_invoice'. Since Odoo invoicing is tightly coupled to the sale.order confirmation workflow, FlitStack migrates invoice headers and lines while noting the source Work Order reference so the link can be re-established in Odoo after sales order confirmation.

MobiWork Recurrent Services and Service Contracts map to Odoo sale.subscription if the Odoo Subscriptions app is installed. If not, the recurring schedule and rate are stored as custom fields on the linked res.partner or crm.lead, and the billing logic is rebuilt using Odoo's automated actions or cron jobs post-migration.

MobiWork Users (technicians, dispatchers, admins) are matched to Odoo res.users by email address. Unmatched users are flagged with a migration report. MobiWork admin-defined roles map to Odoo groups (Sales / Field Service / Manager) if the appropriate groups exist in the target database.

MobiWork form attachments (images, signature captures, PDF reports) migrate as Odoo ir.attachment records linked to the corresponding crm.lead or res.partner via res_model and res_id. Files are downloaded from MobiWork's storage and uploaded to Odoo's filestore or the configured S3 bucket. Binary fields on the parent record are populated with the primary image or signature if Odoo's form view references them.

Every MobiWork custom field gets a corresponding custom field on the appropriate Odoo model (res.partner, crm.lead, sale.order). Field type is mapped: text → char, number → float or integer, date → date, dropdown → selection, checkbox → boolean. Selection options are migrated as selection values on the field. Fields are created via the Odoo migration plan before data loads begin.

MobiWork scheduling data (appointment date, assigned technician, dispatch window) is merged into the target crm.lead as custom datetime fields (x_scheduled_date, x_dispatch_window_start, x_dispatch_window_end) and a many2one to res.users for the assigned technician. Odoo's calendar module can be connected post-migration for full scheduling visualization.

MobiWork payment records (processed via Clearent or Stripe integrations) migrate as Odoo account.payment records linked to the corresponding account.move invoice. Payment method and transaction ID are stored in account.payment fields (payment_method_line_id, ref). If the source shows an unmatched payment, it is held in a staging table for manual resolution.

MobiWork Parts and Services Catalog items migrate as Odoo product.product records with full fidelity. Product type (Stockable, Consumable, Service) is inferred from the MobiWork catalog category. Unit of measure maps to uom_id and uom_po_id. Pricing migrates to list_price and standard_price fields, and product descriptions, barcodes, and vendor information transfer to name, barcode, and seller_ids fields respectively.