Migrate from Gold-Vision to Odoo CRM

Gold-Vision Accounts map to Odoo CRM Companies. The Gold-Vision account name becomes the Company name, address fields map to Odoo's street, street2, city, state_id, zip, and country_id fields. Industry and sector from Gold-Vision custom fields migrate to a custom res.partner category or tag field. The Gold-Vision owner assignment (user_id) maps to Odoo's user_id field on the CRM team configuration.

Gold-Vision Contacts map to Odoo res.partner records with type=contact. Each Contact's parent_id is set to the mapped Company record. Email, phone, mobile, and job title migrate to the standard Odoo fields. Custom fields on the Contact object (Gold-Vision supports unlimited per tenant) map to custom fields on res.partner, with type mapping: text to char, date to date, number to float or integer, and dropdown to selection. Gold-Vision communication history logs migrate as Odoo mail.message records linked to the Contact.

Gold-Vision Leads map to Odoo crm.lead with type=lead. The Gold-Vision lead status and pipeline stage map to the Odoo stage_id within the CRM team. Gold-Vision's lead source and campaign attribution migrate to Odoo's source_id and campaign_id. Lead score, priority, and any custom fields migrate to custom fields on crm.lead. If Gold-Vision uses multiple lead pipelines, we create separate CRM teams in Odoo to isolate stage sequences per pipeline.

Gold-Vision Opportunities map to Odoo crm.lead with type=opportunity. The Gold-Vision dealstage property maps to Odoo stage_id via a stage mapping table built during discovery. Expected revenue, close date, and probability migrate to planned_revenue, date_deadline, and probability. Custom opportunity fields migrate to custom fields on crm.lead. Gold-Vision pipeline assignments map to Odoo CRM team and sales team assignments.

Gold-Vision pipelines and their stages are captured during discovery as a named list. We create Odoo CRM stages within the relevant team for each Gold-Vision pipeline, preserving the stage sequence order. Probability weights migrate to the probability field on each stage. If Gold-Vision has multiple named pipelines, we create a corresponding Odoo CRM team per pipeline so that stage isolation is maintained.

Gold-Vision Campaigns are complex records with multi-stage status, ROI tracking, and member associations. Odoo CRM does not have a native campaign object at the CRM layer; we create crm.tag records for campaign names and tag the associated Opportunities. For customers requiring full campaign history, we create a custom crm.campaign model in the Odoo database. Campaign member contacts are tagged with the campaign identifier and linked to their Opportunities.

Gold-Vision Quotes map to Odoo sale.order in draft state. Quote header fields (account, contact, validity date, payment terms) migrate to the Odoo sale.order fields. Line items migrate to sale.order.line with product, quantity, unit price, and taxes resolved. Gold-Vision branding templates and e-sign metadata are preserved as URL references in a custom field; the actual PDF or signed document migrates as an Odoo ir.attachment linked to the sale.order. If the customer does not use Odoo Sale, we flag Quote migration as out of scope and preserve quote data in a custom CSV export.

Gold-Vision Projects are standalone records with time entries and task hierarchies that do not map directly to Odoo CRM. During scoping, the customer chooses between two strategies: (a) Projects migrate as Odoo project.project records with the CRM opportunity linked via a custom Many2one field, preserving tasks and time entries; or (b) Projects migrate as CRM Opportunities with a project_reference__c custom field for admin-created Odoo Project records post-migration. Strategy (a) requires the Odoo Project app to be active on the destination tenant; strategy (b) is the default when only the CRM app is licensed. Time entries from Gold-Vision migrate as project.task.timesheet records in strategy (a) or as notes on the Opportunity in strategy (b).

Gold-Vision Tickets migrate to Odoo helpdesk.ticket. The ticket subject, description, priority, and status map to name, description, priority, and stage_id. Conversation threads migrate as Odoo mail.message records linked to the ticket. Agent assignment migrates to user_id on the ticket. Custom fields on the Gold-Vision Ticket object map to custom fields on helpdesk.ticket. If the Odoo Helpdesk app is not licensed, we migrate tickets as CRM Opportunities with type=support and a custom status field, flagging the Helpdesk app as a future licensing requirement.

Gold-Vision's Communications log (M365-synced emails, calls, appointments) distributes across Odoo models. Emails become mail.message records linked to the parent res.partner or crm.lead. Calls become crm.phone.call records linked to the Contact or Opportunity. Meetings become calendar.event records linked to the related Opportunity or Contact. Gold-Vision task entries map to project.task records or crm.activity records depending on whether the Odoo Project app is active. Activity timestamps are preserved by setting write_date and create_date on the migrated records.

Gold-Vision supports unlimited custom fields per object. We extract the full custom field schema per object during discovery and pre-create matching custom fields in Odoo before any data import. Field type mapping follows Gold-Vision types to Odoo field types: varchar to char, textarea to text, integer to integer, decimal to float, date to date, datetime to datetime, dropdown to selection, and checkbox to boolean. Lookup fields (e.g., Account lookup on Contact) are resolved during import by matching the foreign key to the mapped destination record ID.

Gold-Vision documents and file attachments stored against Accounts, Contacts, Opportunities, Projects, and Tickets are exported as binary blobs and re-associated to the corresponding Odoo record via ir.attachment with res_model pointing to the destination model (res.partner, crm.lead, project.project, helpdesk.ticket) and res_id set to the migrated record ID. Attachment filenames and create dates are preserved. If the total attachment volume exceeds 5 GB, we migrate attachments in a phased batch after the primary record migration completes.

Gold-Vision tags and categories are preserved as Odoo crm.tag records. The tag name and any taxonomy hierarchy (category > subcategory) are flattened into a single tag name or preserved as a crm.tag.parent_id hierarchy if the Odoo version supports it. Tags applied to multiple object types (Contacts, Opportunities, Accounts) are re-applied individually to each migrated record in the destination.

Gold-Vision Users and Owners are mapped to Odoo res.users by email match. Gold-Vision role and team assignments are noted in a user_mapping.csv for the customer's Odoo admin to configure Odoo access rights and CRM team membership post-migration. Any Gold-Vision Owner without a matching email in the destination is held in a reconciliation queue. Inactive Gold-Vision users are mapped to Odoo portal users or flagged for the admin to deactivate.