Migrate from Husky Intelligence to Odoo CRM

The status field distinguishes between active prospects and closed-won accounts. FlitStack AI maps the active prospects to crm.lead records with the appropriate type and stage, while established customers become res.partner records with company_type set to 'company' when applicable. The conversion process ensures that when a lead is won, the associated partner record already exists, preserving the history.

If a company has multiple locations defined as sub‑companies in Husky, each sub‑company becomes a separate res.partner with its own address, and the parent company holds them via the child_ids relation. FlitStack AI preserves the hierarchical depth by creating the top‑level partner first, then linking each subsidiary as a child. This approach allows Odoo's native company view to display the full corporate structure.

Husky job records have no direct Odoo CRM equivalent. We map them to project.task under a dedicated migration project, preserving job status, assigned operative, site/location, and description. If the project app is not active, we map to a custom husky_job model or store as a note on the linked crm.lead.

If a Husky line item references a SKU not in Odoo, FlitStack AI creates a placeholder product with that SKU and flags it for review. The estimate's validity date maps to sale.order's validity_date, and any payment terms are recorded in the order's note. Discount percentages and tax rates are stored on sale.order.line, allowing Odoo to compute totals accurately.

Husky invoices map to Odoo account.move records with move_type='out_invoice' for open invoices and 'out_refund' for credits. Partner/vendor invoices map to 'in_invoice'/'in_refund'. The Odoo Accounting app must be installed and the company’s chart of accounts configured before migration; otherwise FlitStack AI pauses and prompts for setup. Open invoices preserve due date and amount_due, while paid invoices set payment_state='paid'.

Husky scheduling records map to project.task entries with planned_date set from the scheduler's start time, and assigned user set from the operative assignment. If a Husky schedule entry has a specific time slot, a corresponding calendar.event is created in Odoo's calendar module for that operative.

Every custom property defined in Husky's form builder is parsed from the export, and a corresponding custom field is created in Odoo via ir.model.fields before data import runs. Field types are inferred from Husky's data (text → char, number → float, date → date, dropdown → selection). Fields are prefixed x_husky_ to avoid name collisions with native Odoo fields.

Files attached to Husky records — quotes, job photos, signed documents — are downloaded and re-uploaded as Odoo ir.attachment records linked to the target res.partner, crm.lead, or sale.order. Odoo stores files in its filestore; the original filename and MIME type are preserved.

Husky user accounts are matched to Odoo res.users by email address. Unmatched owners are flagged before migration and assigned to a fallback Odoo user. Role and permission sets in Husky have no Odoo CRM equivalent — these must be configured in Odoo's access rights settings post-migration.

Logged calls, emails, and meeting notes from Husky become Odoo mail.message records on the related crm.lead or res.partner, preserving timestamps and the original user. Attachments are stored as ir.attachment linked to the message. Job completion notes are copied into the project.task description field, retaining any internal tags or references, and the message_type is set to 'comment' for communications or 'notification' for system alerts.

Husky Jaspersoft report definitions and custom dashboard configurations cannot be exported in a format Odoo can ingest. FlitStack AI exports a structured JSON reference of report names, parameters, and filter logic so Odoo admins can recreate equivalent reports using Odoo's built-in reporting or the Spreadsheet app.