Migrate from Glaze CRM to Odoo CRM

Glaze CRM Company records map to Odoo res.partner with partner_type set to 'company' to distinguish them from individual contacts. Company name becomes the partner's display name, address fields map to street, street2, city, state_id, zip, and country_id, and website maps directly. We create res.partner records first in every migration so that the lookup is satisfied for any subsequent Contact import that references a parent Company.

Glaze CRM Contact records map to Odoo res.partner with partner_type set to 'person'. Email, phone, mobile, and function (job title) migrate directly. The parent_id field links each Contact to its parent Company res.partner record that was created in the Company import phase. If the source Contact has no associated Company, the Contact imports as a standalone partner without a parent_id.

Glaze CRM Lead records map to Odoo crm.lead with type = 'lead'. Lead source, status, and owner assignment map to source_id, stage_id, and user_id respectively. The Glaze CRM lead description (notes) migrates as the crm.lead description field. We preserve the Glaze lead creation date as create_date in Odoo to maintain historical sequencing against the activity timeline.

Glaze CRM Deal records map to Odoo crm.lead with type = 'opportunity'. Deal name becomes the opportunity name, amount maps to planned_revenue, and stage maps to stage_id using a stage reconciliation table we build during scoping. Probability is computed from the destination Odoo stage unless Glaze carries an explicit probability field we can preserve as a custom field.

Each Glaze CRM pipeline becomes a set of crm.stage records in Odoo scoped to the relevant team or sales process. Stage order, name, and probability percentage migrate to name, sequence, and onchange_stage_id probability mapping. We configure crm.stage values in Odoo before importing any crm.lead records to avoid orphaned stage references.

Glaze CRM Tasks map to Odoo mail.activity records linked to the parent crm.lead or res.partner record. Activity type (call, email, meeting, todo) maps to activity_type_id; due date maps to date_deadline; assignee maps to user_id. Completed vs. open status migrates with the activity's state preserved. Task subject migrates as the activity's summary or as a related mail.message body.

Glaze CRM Users map to Odoo res.users by email address as the deduplication key. We extract every distinct owner referenced on Contact, Company, Lead, Deal, and Task and match against the destination Odoo instance's user table. Any Glaze Owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record imports resume.

Glaze CRM Tags on Contacts and Companies map to res.partner.category records linked via res_partner_category_rel. Glaze CRM Tags on Leads and Deals map to crm.tag records linked via crm_lead_tag_rel. Tags migrate as flat string arrays and are reapplied to the corresponding records in Odoo during the relevant object import phase.

Glaze CRM custom fields on Contacts, Companies, and Deals require a schema audit before migration. We request a sample record export from the customer showing all visible custom fields, infer field types (text, date, integer, selection, many2one), and then create matching ir.model.fields in Odoo via a custom module or Odoo Studio before data import. Multi-select fields require splitting into a related res.partner.category mapping table.

Glaze CRM document attachments cannot be exported via an automated API because no document export endpoint is documented. We capture document metadata (filename, upload date, file size, linked record reference) and map it to Odoo ir.attachment records. The actual file binaries require a separate manual export step from Glaze CRM, typically via their admin interface or direct database access, which the customer provides as a zip of files to be imported alongside the metadata migration.

Glaze CRM Lead Source values map to Odoo utm.source records if the Odoo CRM installation includes the Marketing app. If Marketing is not installed, we map Lead Source to a crm.tag entry or a custom selection field. We document which approach the customer prefers during scoping.

The Glaze CRM association between a Contact and its parent Company is preserved in Odoo as res.partner.parent_id pointing to the Company-type res.partner. This relationship is resolved during the Contact import phase by first completing the Company import and then setting the parent_id foreign key by matching on company name or external Glaze ID stored as a temporary reference field.