Migrate from Gauss Box CRM & Sales to Odoo CRM

Gauss Box Organization records map to Odoo res.partner with partner_type set to company. The organization name, industry, size, address fields, and any D&B data (creditworthiness, risk indicators) migrate to partner fields and custom fields we pre-create in Odoo. Organization is the first record type imported because Contacts in Odoo reference the parent partner_id field on the partner record. The Odoo partner.vat field can carry D&B DUNS number if present in the Gauss Box export.

Gauss Box Product catalog entries (name, category, type, price, sale tax configuration) map to Odoo product.template records. Product categories map to Odoo product.category. The Gauss Box sale tax field maps to Odoo's account.tax on the product template's seller_ids. Tiered pricing and volume discount rules from Gauss Box Products are not natively supported in Odoo Product Templates — we flag these as Odoo Pricelist Items to configure post-migration.

Gauss Box Contact records map to Odoo res.partner with partner_type set to individual. We preserve the Contact's name, email, phone, job title, and address fields. The parent Organization reference from Gauss Box resolves to an Odoo res.partner (company) via the partner_id lookup. Custom attribute-set fields on Contacts migrate to custom fields on the partner record after we enumerate them during discovery.

Gauss Box Lead records map to Odoo crm.lead with type=lead. The lead's work status, assigned team member, and lead source migrate to Odoo crm.lead fields. If the Gauss Box Lead is already linked to a Contact in Gauss Box, we resolve that Contact's new Odoo partner_id and set the lead's partner_id in Odoo during import. Lead status values from Gauss Box are mapped to Odoo stage_id values in the target team's pipeline.

Gauss Box Deal records map to Odoo crm.lead with type=opportunity. The Gauss Box deal stage name maps to the target Odoo crm.team's stage. Deal value, budget, owner assignment, and product associations carry over. The product associations from Gauss Box resolve to the imported product.template records. Owner assignment maps via email match to Odoo res.users.

Gauss Box pipeline stages are configurable per account. We enumerate every active stage name and probability value during discovery and create matching crm.stage records within the target crm.team in Odoo. Stage probability percentages migrate as probability fields on crm.lead. If the customer uses multiple Gauss Box pipelines, each becomes a separate crm.team in Odoo with its own stage sequence.

Gauss Box Activities (calls, emails, meetings, tasks) tied to Deals and Contacts map to Odoo mail.activity records linked to the migrated crm.lead or res.partner. Activity type, timestamp, description, and the parent object link are preserved. Activity types vary by account in Gauss Box — we map them to Odoo's activity types (Call, Meeting, Email, Upload Document) during the discovery phase. Gauss Box smart notification records embedded in parent metadata are flagged separately for manual recreation.

Gauss Box Activities of type Meeting migrate to Odoo calendar.event. Start datetime, end datetime, location, and attendee list map directly. Odoo calendar.event records link to the target crm.lead or res.partner via the res_model and res_id fields. Meeting notes migrate as mail.message records attached to the event.

Gauss Box call activities map to Odoo mail.activity with activity_type_id set to Call. Call duration and disposition from Gauss Box migrate to custom activity fields we add to Odoo's activity model. The owner assignment resolves via email match to Odoo res.users.

Gauss Box documents stored per record migrate as ir.attachment records in Odoo, linked via res_model and res_id to the corresponding migrated record (crm.lead or res.partner). Filename and any stored metadata are preserved. Document access permissions from Gauss Box do not carry over — we recommend the customer review Odoo's record-level access rules for the CRM module post-migration.

Gauss Box user accounts referenced on Leads, Contacts, Deals, and Activities resolve by email match to Odoo res.users records. Owners without a matching Odoo user are held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Gauss Box users should be deactivated before export to avoid orphaned owner assignments in the CSV.

Gauss Box attribute-set custom fields on Contacts, Organizations, Deals, and Products are account-specific and require enumeration during discovery. We create matching custom fields in Odoo via Settings > Technical > Custom Fields (requires Technical Features enabled) before any data import. The field type mapping translates Gauss Box field types to Odoo field types (Char, Text, Selection, Many2one, etc.). Fields that exist only in Gauss Box and have no Odoo equivalent become custom fields with a note in the mapping document for the admin to evaluate post-migration.