Migrate from Bluetrait to Odoo CRM

Bluetrait's Customers and Clients map across three Odoo objects. Companies map to Odoo CRM Company (res.partner with type=company). Active clients with an established relationship map to Odoo Contact (res.partner with type=contact) attached to the Company. Prospects or unqualified leads without a company attachment map to Odoo CRM Lead. We apply a lifecycle stage split during scoping based on Bluetrait's CRM status values and preserve the original customer type and status in custom fields on the Odoo Contact for audit. Company domain names from Bluetrait populate the Website field on the Odoo Company record and serve as the dedupe key.

Bluetrait Companies map directly to Odoo CRM Company (res.partner with partner_type=company). Company address, phone, email, and custom fields migrate as typed Odoo partner fields. The Bluetrait company-client linking property migrates as a many2many field on the Odoo Company record, allowing the customer's admin to view associated contacts. Company-level custom fields are pre-created in Odoo before migration to avoid schema errors during data load.

Bluetrait Tickets map to Odoo Helpdesk Ticket (helpdesk.ticket) when the Helpdesk app is active. Ticket status, priority, due date, assignee, internal notes, and tags migrate directly. Custom Bluetrait ticket fields map to custom fields on the helpdesk.ticket model. Ticket conversations (comments and internal notes) migrate as Odoo ticket messages using mail.message. The link between tickets and associated Bluetrait Companies and Clients resolves to the Odoo Company and Contact records created in earlier phases. If the customer does not activate the Helpdesk app, tickets map to CRM Lead as a fallback with the ticket ID preserved in a custom field.

Bluetrait tickets linked to MSP agents (endpoints) do not have a direct Odoo equivalent. Agent-level ticket history migrates as CRM Lead records with the MSP endpoint name preserved in a custom field endpoint_name__c. If the customer activates the Odoo Project app for MSP task tracking, these records can be re-linked manually post-migration using our endpoint inventory document. Watchdog restart logs and alert configurations are not migratable and are documented separately for the customer's IT team.

Bluetrait Timesheet entries (date, hours, user, task/project link, and timesheet type) map to Odoo Timesheet entries (account.analytic.line). The employee record in Odoo is resolved by matching the Bluetrait user email to an Odoo User, and the analytic account links to the project if the Project app is active. Bluetrait's timesheet type is preserved as a custom tag on the Odoo timesheet entry. If the customer uses Bluetrait's auto-billing-from-timesheet feature, the line item descriptions carry the timesheet type; we document these patterns for manual rebuild in Odoo Accounting.

Bluetrait Projects (with project names, budgets, and task counts) map to Odoo Project (project.project). Project budgets migrate as custom fields on the Odoo Project record. Custom project statuses and budget thresholds map as custom selection fields. Tasks within the project migrate as Odoo Project Tasks (project.task) with task name, description, assigned user, and deadline preserved. Task counts from Bluetrait are reconciled against the task records created in Odoo as a post-import validation step.

Bluetrait invoices (open and historical, including line items, taxes, and payment status) map to Odoo Account Invoice (account.move with move_type=out_invoice). Invoice status (paid, open, cancelled) migrates as the Odoo payment_state field. Line items map to invoice lines with product reference, quantity, unit price, and tax account preserved. Recurring billing automation does not export and is documented separately for Odoo Accounting reconfiguration. Historical invoices are migrated as posted records if paid or as open records if unpaid.

Bluetrait quotes map to Odoo Sale Order (sale.order). Quote status (draft, sent, won, lost) maps to Odoo state (draft, sent, sale, cancel). Line items on the quote map to sale.order.line with product, quantity, and price preserved. If Bluetrait quotes have expiry dates, these migrate as validity dates on the Odoo Sale Order. Notes and terms from the Bluetrait quote migrate as order-level internal notes on the Odoo Sale Order.

Bluetrait purchase orders map to Odoo Purchase Order (purchase.order). PO status (draft, confirmed, received, cancelled) maps to Odoo state (draft, purchase, done, cancel). Line items, vendor references, and expected delivery dates migrate as purchase.order.line records. The vendor company from Bluetrait maps to an Odoo Vendor (res.partner with supplier_rank > 0) created or matched during the Company phase.

Bluetrait Products (with quantities, recurring billing frequencies, and pricing) map to Odoo Product (product.product for variants, product.template for the product template). ProductCode from Bluetrait maps to product.default_code. Recurring billing frequency is preserved as a custom field on the Odoo Product; the customer's admin configures subscription cadence in Odoo Subscription or Invoicing post-migration. Product-to-billing associations migrate as custom line-item metadata on the corresponding invoice or sale order line.

Bluetrait Users (username, role, permissions group, and Two-Factor Authentication status) map to Odoo User records (res.users). We match by email address. 2FA status is noted but cannot be migrated for security reasons; the customer resets 2FA for migrated users as a post-migration step. If a Bluetrait User has no email, a placeholder email is generated and flagged in the reconciliation report for the admin to update. Active/inactive status from Bluetrait maps to the Odoo User active flag.

Bluetrait MSP Agents represent managed endpoints with watchdog status, installed software, and alert configurations. Odoo has no native RMM equivalent. We migrate agent endpoint names, associated client companies, and basic endpoint metadata as CRM Lead records with custom fields (endpoint_name__c, watchdog_status__c, installed_software__c). Health monitoring and alert configuration rules are documented in an MSP endpoint inventory report for the customer to re-implement in their chosen RMM tool or Odoo.sh infrastructure monitoring. This is a configuration-only mapping; no live monitoring data transfers.

Bluetrait knowledge base articles and their categories can be exported and map to Odoo Knowledge Base (knowledge.article). Article title, body content, and category structure migrate. Article-to-ticket linking is not preserved automatically through either the Bluetrait export or the Odoo Knowledge import API. We generate a cross-reference document mapping each Bluetrait article ID to the ticket IDs it references so the customer's admin can re-link articles manually in Odoo Knowledge post-migration. This cross-reference is delivered as a spreadsheet alongside the migration package.

Bluetrait Passwords module entries are not accessible via API or CSV export for security reasons. We cannot migrate credentials directly. We generate a full inventory of password entries including folder name, entry name, associated system, and any notes visible to the migration user. This inventory is delivered as a reference document for the customer to manually recreate entries in their chosen password manager (Odoo has no native password module; Bitwarden, 1Password, or a similar tool is recommended). This step is not a migration blocker but requires post-migration customer action.