Migrate from Furious to Odoo ERP

Furious Clients map to Odoo res.partner records. The client name becomes partner name, email and phone map to standard email and phone fields, and address data maps to street, city, state, and country fields. If Furious stores multiple contacts per client (e.g., a primary billing contact and a project manager), we split them into separate res.partner records and link them via the parent_id field for hierarchy. Any Furious custom fields on Clients (e.g., agency code, billing tier, VAT number) map to custom Char or Selection fields on res.partner via Odoo Studio or ir.model.fields during the discovery phase.

Furious Projects map to Odoo project.project records. Project name, status (active/archived), owner assignment, start date, and end date transfer directly. Furious project-level custom fields (e.g., project type, client tier, budget code) require field-by-field mapping to Odoo custom fields on project.project. If the agency uses Furious's project profitability reporting, we recommend enabling Odoo's Project app with the Timesheet and Invoicing features to replicate that visibility in Odoo. Project-task hierarchy from Furious Tasks maps to Odoo's project.task structure under the parent project.

Furious Quotes map to Odoo sale.order records in quotation state. Quote name and date transfer to name and date_order. The Furious-to-project linkage becomes sale.order project_id if Odoo Project is linked to the Sale Order. Quote line items (description, quantity, unit price, discount) map to sale.order.line records with product_id resolved either to an existing Odoo product or as a descriptive text line. Furious quote status (Draft, Sent, Accepted, Lost) maps to Odoo state values (draft, sent, sale, cancel). Custom fields on Quotes require field-level mapping to sale.order or sale.order.line custom fields.

Furious Invoices map to Odoo account.move records with type='out_invoice'. Invoice number, date, and due date map to name, invoice_date, and invoice_date_due. Furious invoice line items map to account.move.line with account_id resolved to the appropriate Odoo revenue account from the chart of accounts. Open invoices are flagged for manual reconciliation because payment status can change during the cutover window; any payments received in Furious between snapshot and DNS cutover require a manual journal entry in Odoo. Historical paid invoices migrate with full line item detail and the paid state preserved.

Furious Purchase Orders map to Odoo purchase.order records. PO number, date, and vendor reference transfer directly. PO line items (product description, quantity, unit cost) map to purchase.order.line with product_id resolved to an Odoo product or entered as a description line. Vendor records must exist in Odoo before PO import; we create supplier Contact records (res.partner with supplier rank) from Furious vendor data during the master data phase. If Furious Purchase Orders are linked to Projects, we set the Odoo analytic account or project_id on the PO line to preserve the project association for cost tracking.

Furious Time Entries map to Odoo account.analytic.line records via the Timesheet app. Employee (from Furious User), Project, Task, date, duration (hours), and the billable/non-billable flag transfer directly. The billable flag maps to Odoo's validated boolean on the timesheet line if the Timesheet app is installed. We recommend installing Odoo's Timesheet app before migration if the agency tracks project profitability by time; if not installed, time entries land as analytic account lines without the timesheet interface. Task mapping requires that the destination Odoo project.task records exist first so the task_id foreign key resolves at import time.

Furious Tasks map to Odoo project.task records under the parent project.project. Task name, description, assignee (mapped to Odoo User), status, priority, start date, due date, and planned hours transfer directly. Task custom fields (e.g., task category, estimated effort, billing type) require field-by-field mapping to custom fields on project.task. If Furious uses sub-tasks, we map those to Odoo child_ids within the task hierarchy. Task status values from Furious (e.g., Not Started, In Progress, Review, Done) map to Odoo kanban stage values that we configure before migration.

Furious Users map to Odoo res.users records by email match. Name, email, and role string transfer. Furious role names (e.g., Project Manager, Account Lead) do not map directly to Odoo's permission groups; we map them to the closest Odoo group (e.g., Project User, Sales User) and flag any roles that require manual group assignment post-import. Inactive Furious users are excluded unless the customer specifies they should be migrated as inactive Odoo users. Owner assignment on Furious records (Projects, Tasks, Quotes, Invoices) is resolved via the User-to-User email match before record import begins.

Furious custom fields defined on Projects, Quotes, Invoices, Tasks, and other objects require field-by-field discovery, type mapping, and Odoo schema creation before any data import. We discover the full custom field set during scoping, classify each field type (text, number, date, picklist, checkbox), and create matching ir.model.fields in Odoo with the correct field type (Char, Text, Float, Date, Selection, Boolean). Custom fields on Furious that have no Odoo equivalent are flagged for manual entry or an Odoo Studio field creation during the configuration phase. Skipping this step results in data landing in wrong fields or being silently dropped during import.

Furious stores binary file attachments linked to Projects, Quotes, and Invoices. We do not extract or transfer binary file attachments in the automated migration pipeline. We audit and inventory every record with an attachment, recording the record type, record ID, and attachment filename in a CSV delivered to the customer. The customer re-uploads attachments manually post-migration via Odoo's document management or the attachment icon on each record. This is the single largest manual post-migration task for most Furious migrations and should be budgeted for during planning.

Furious Quote line items map to Odoo sale.order.line records attached to the parent sale.order. Line description, quantity, unit price, tax, and discount percentage transfer directly. If the Furious Quote references a product SKU, we resolve it to an Odoo product.product record during import; if no matching product exists, the line imports as a description-only text line for manual product creation. The sequence order of line items is preserved via the sequence field on sale.order.line.

Furious Invoice line items map to Odoo account.move.line records on the parent account.move (type=out_invoice). Line description, quantity, unit price, tax, and account mapping transfer directly. The revenue account on each line is resolved from the Odoo chart of accounts based on the product or, for description-only lines, a configurable default revenue account selected during scoping. Tax rates from Furious map to Odoo tax IDs that must exist in the Odoo tax chart before invoice import.