Migrate from Markate to Odoo CRM

Markate Customers map to Odoo Contact records with address details split into separate Address records (res.partner). The Markate customer name becomes Contact name, email and phone map directly, and service address fields map to the contact's delivery address. We resolve the Address as a related res.partner record linked via add_parent_id / type='delivery' so that Odoo's quotation-to-sale-order flow uses the correct delivery address. Customers without an email are flagged for manual review since Odoo's Contact uniqueness relies on email as a dedupe key.

Markate Items map to Odoo Product records (product.product or product.template depending on Odoo variant tracking settings). The item name becomes Product name, SKU maps to Product barcode or default_code, and the list price maps to Product list_price. Items are imported before Invoices so that the Odoo product.product record exists at the time of invoice line creation.

Markate Categories map to Odoo Product Category (product.category) records. Categories must be imported before Items because Odoo Product references a parent category_id. The Markate category name becomes product.category name, and any category description maps to the Odoo category's property_account_expense_categ_id if accounting is active.

Markate Estimates map to Odoo Sale Order in draft quotation state. Markate estimate line items map to sale.order.line records with the Markate Item resolved to an Odoo product.product ID via the Item migration step. Estimate status (sent, accepted, declined) maps to Odoo state (draft, sent, sale_order, cancelled). Customer lookup uses the email dedupe key resolved during the Customer migration phase.

Markate Work Orders map to Odoo Project Task records when the Odoo Project module is active. The Work Order description and job details become Task description; assigned team members map to Odoo User records resolved by email; schedule fields map to Task date_deadline and planned_hours if timesheet tracking is enabled. Work Orders without an assigned team member map to Tasks owned by the Project's default user. If the customer does not activate the Project module, Work Orders are documented as Sale Order lines linked to the Customer contact for manual task creation.

Markate Invoices map to Odoo Account Invoice (account.move with type='out_invoice') for customer-facing invoices, or account.move type='in_invoice' if Markate vendor bills are involved. Invoice line items reference the Odoo product.product IDs resolved during the Item migration. Payment status (paid, partial, unpaid) maps to Odoo payment_state field. Partial payment amounts and payment method details migrate to Odoo's account.payment records linked to the invoice.

Markate Expenses map to Odoo HR Expense records (hr.expense) if the Odoo HR module is active in the destination instance. Vendor name maps to expense product or to the Odoo hr.expense.sheet vendor field. Amount and currency map directly. Job-related expenses linked to a Work Order are connected to the corresponding Project Task via the Odoo project_id and task_id fields once the Work Order migration phase is complete.

Markate Team Members map to Odoo User records resolved by email match. A Markate team member assigned to Work Orders and Invoices becomes an Odoo User with the appropriate access rights (Employee group for timesheet access, User group for CRM access). Owner assignments on Markate records resolve to the Odoo user_id via this User mapping. Any Markate team member without an Odoo User match is held in a reconciliation queue for the customer admin to provision before the parent record migration continues.

Markate does not expose custom field definitions via its CSV export interface. Any custom fields added by the customer in Markate are not visible in the exported CSV and cannot be migrated. We document this as a gap in the scoping report and provide a manual-recreate checklist for each custom field, noting the Odoo field type to configure (char, selection, float, etc.) and the records to which it applies.

Markate's Data Migration tool does not export or import file attachments (photos, signed documents, receipts). We flag all attachments as manual-migration items and deliver a checklist of files organized by Customer and Work Order to re-upload in Odoo after migration. Photos from Work Orders are the highest-priority gap for field service teams; we recommend uploading to Odoo Project Task attachments via the Project module's document management.

If Markate's QuickBooks Online sync is active at migration time, we document the QuickBooks Online customer, invoice, and payment records that exist independently of Markate. These do not migrate through Markate but represent data that should be imported directly from QuickBooks into Odoo Accounting after Odoo setup. We provide a separate QuickBooks-to-Odoo import checklist scoped to the overlapping invoice and customer records.

Markate CSV exports include created_at and updated_at timestamps for each record type. We map these to Odoo's create_date and write_date fields where the Odoo XML-RPC API allows write access to those fields (admin context required). For records where create_date cannot be set via API, we create a custom field markate_created_date__c to preserve the original Markate timestamp for audit and reporting continuity.