Migrate from GleanView to Odoo CRM

GleanView Company records map to Odoo res.partner with partner_type set to 'company' and the is_company flag enabled. Company name becomes partner name, address fields map to street, street2, city, state_id, zip, and country_id. Industry, website, and custom fields map to res.partner fields or Odoo Studio custom fields. We resolve duplicate company names before import using fuzzy matching on the company name and domain. Partners are created before Contacts so that Contact imports can satisfy the partner_id lookup.

GleanView Contact records map to Odoo res.partner with partner_type = 'contact' and parent_id set to the mapped Company Partner. Email becomes the primary dedupe key; we flag any Contacts sharing an email with an existing Partner for manual review before import. Name, phone, mobile, function, and title map to the corresponding res.partner fields. Custom Contact properties export from GleanView CSV headers and map to Odoo Studio fields on res.partner. Lifecycle stage from GleanView maps to a custom Char field for audit.

GleanView Lead records map to Odoo crm.lead with type = 'lead'. Lead status, source, and owner map to stage_id, source_id, and user_id respectively. Unqualified GleanView Leads land as Odoo Leads and can be converted to Opportunities later through Odoo's Lead Conversion action, which creates a Partner and Opportunity from the Lead. We preserve the original GleanView lead identifier in a custom reference field.

GleanView Deal records map to Odoo crm.lead with type = 'opportunity'. Deal stage maps to stage_id on the Odoo Opportunity, and the pipeline assignment maps to a Odoo Sales Team or using Odoo Studio to create a pipeline-specific stage set. The GleanView deal amount maps to planned_revenue. Partner_id on the Opportunity is resolved by matching the GleanView Company name to the imported Partner. Deal owner maps to user_id. Closed-Lost and Closed-Won reason custom fields become tag additions on the Opportunity.

GleanView pipeline stages map to Odoo crm.stage records within the relevant Sales Team. Stage order and probability percentage migrate to sequence and sequence fields on the stage. Each GleanView pipeline becomes a separate Sales Team in Odoo, and stages are scoped per team. We configure the stage sequence in Odoo Settings before importing any Opportunities so that the stage_id foreign key is satisfied at import time.

GleanQuote Products export via CSV with base price, cost, margin, and attributes. We map base_price to list_price and cost to standard_price on product.product. Simple products migrate cleanly. Products with conditional options or bundles are flagged as complex and mapped to Odoo product variants using the attribute lines model. We pre-create the Odoo product attribute and attribute value records before importing the product variants.

GleanQuote Services map to Odoo product.product with type = 'service'. Service pricing rules from GleanQuote export as base cost fields and map to list_price. Time-based or unit-based service pricing is preserved in a custom field for Odoo Sales to evaluate against Odoo price lists post-migration.

GleanView Quote records export as CSV with quote headers and line items. We reconstruct sale.order records in Odoo: the quote header maps to order_id fields (partner_id, user_id, date_order, validity_date), and quote line items map to sale.order.line with product_id resolved from the GleanQuote product mapping, quantity from the CSV quantity field, and price_unit from either the flat price field or the pre-computed value for formula-derived prices. Template-attached PDFs are flagged as document references to re-upload or re-generate via Odoo's sale report.

Quote line items map to sale.order.line with product_id resolved via the Product mapping, quantity mapped directly, discount mapped to discount percentage, and price_unit resolved from the CSV flat value or pre-computed staging sheet. Bundled quote line items with conditional visibility map to sale.order.line with a note field referencing the parent bundle and a custom visibility flag. Each sale.order.line references its parent sale.order quotation.

GleanView engagements—emails, calls, meetings, and notes attached to Contacts or Deals—map to Odoo mail.message records linked to the crm.lead via model = 'crm.lead' and res_id = the Opportunity ID. Call duration and disposition migrate as custom fields on the message. Email body migrates as message_body on mail.message. Meeting details (date, location, attendees) migrate as mail.message with subtype 'meeting'. Note text migrates as mail.message with body. Each engagement type gets a subtype tag for filtering in Odoo's activity timeline.

GleanView owners referenced on Contact, Company, Lead, and Deal records are resolved by email match against the Odoo res.users table. We extract every distinct owner identifier from the CSV exports and present a lookup worksheet during scoping. Any GleanView owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision the User before record import resumes. Active/inactive status on the User determines whether the owner_id foreign key is set to active or inactive in Odoo.

GleanView custom fields on Contacts, Companies, Deals, and Leads are read from the CSV column headers. We create corresponding fields in Odoo using Odoo Studio (for user-built customizations) or via direct ir.model.fields creation for API-named fields. Field type mapping follows: text to char or text, number to float or integer, date to date, dropdown to selection, multi-select to char or many2many. Custom field values migrate as part of the parent record import. Any custom fields without a clear Odoo equivalent are flagged for a custom field decision during scoping.

GatherSpaces proposal PDFs, product images, and content library files are not included in GleanView's standard CSV export. We document every file URL and its associated record (Contact, Company, Deal, Quote) in a file manifest CSV delivered alongside the migration. The customer re-uploads binary files to Odoo's document management (Documents app or ir.attachment) and re-links them to the relevant record. We do not download and re-upload binary files as part of standard migration scope.