Migrate from MeasureSquare to Odoo CRM

MeasureSquare Contact maps directly to Odoo res.partner where type='contact'. First name, last name, email, phone, job title, and address fields map field-for-field. Primary company assignment is handled via the partner's parent_id (linking to the company partner) or the Account Contacts relationship on the company side. Multiple company associations collapse to one primary parent_id with additional associations surfaced as contact_ids on the company partner.

MeasureSquare Company maps to Odoo res.partner where type='company'. Company name becomes partner name, domain becomes website, and address fields map to street, city, state, zip, and country on res.partner. Parent-child company hierarchies in MeasureSquare (parent_company_id) map to parent_id on res.partner. Industry pick-list values require value-by-value mapping since MeasureSquare industry terms differ from Odoo's default industry list.

MeasureSquare Deal maps to Odoo crm.lead treated as opportunity (type='opportunity'). Deal name becomes crm.lead name, amount maps to expected_revenue, and close date maps to date_deadline. The deal's pipeline stage maps to stage_id on crm.lead via value_mapping — each MeasureSquare stage name is matched to the corresponding Odoo CRM stage by sequence order or name. Pipeline name itself maps to crm.team_id so deals land in the correct Odoo sales team.

MeasureSquare pipeline stage names are mapped one-to-one to Odoo CRM stage names via value_mapping. Odoo stores stages as crm.stage records with id and name; we match by name string or by sequence position if names differ. Stage-entered timestamps from MeasureSquare are preserved in a custom datetime field (x_stage_entered_date) on crm.lead since Odoo's crm.lead stage history is not exposed via the standard API.

MeasureSquare Tasks map to Odoo project.task records. Tasks linked to a Deal in MeasureSquare are imported as tasks on a project.project created per pipeline or per owner group. Task name, description, due date, and priority map field-for-field. Odoo's task stage_id is matched to MeasureSquare task status via value_mapping. Unassigned tasks without a project are created on a default 'General' project in Odoo.

MeasureSquare notes and file attachments migrate to Odoo ir.attachment records linked by res_model='crm.lead' and res_id pointing to the corresponding crm.lead id. Notes with rich text are stored as HTML in the attachment's datas field or as a note linked via mail.message. Files are downloaded from MeasureSquare storage and re-uploaded to Odoo's filestore via /web/binary/upload_attachment. File size limits from Odoo's ir_attachment model apply.

MeasureSquare owner_id on Contact, Company, and Deal resolves by email match against Odoo res.users. Unmatched owners are flagged before migration; your Odoo admin either creates a placeholder user or assigns those records to a fallback owner (typically the admin user). Inactive Odoo users cannot be assigned as owners — they must be activated or the record routed to an active user.

MeasureSquare custom fields on Contact, Company, Deal, or Task require manual creation in Odoo Studio before migration runs. We export the full custom field list from MeasureSquare including pick-list values and field types (text, number, date, pick-list) and deliver a setup plan naming the exact Odoo Studio field to create per custom field. Pick-list fields require value-by-value mapping if Odoo's default pick-list values differ from MeasureSquare's.

MeasureSquare quotes and sales orders map to Odoo sale.order. The quote total, line items, and customer reference migrate as order lines on sale.order. MeasureSquare-specific fields (pricing tier, bid template, change order flag) become custom fields on sale.order or sale.order.line. Product lines that reference MeasureSquare product database items are linked to Odoo product.product by SKU match or flagged for manual product re-creation in Odoo.

MeasureSquare lead source (referral channel, marketing campaign tag) maps to Odoo source_id on crm.lead via value_mapping. Odoo stores lead sources as utm.source records. If MeasureSquare uses custom source names not in Odoo's default list, we create matching utm.source records during migration and link them by name. Source attribution history is preserved as a custom field if the utm model is not active in the target Odoo instance.