Migrate from Fergus to Odoo CRM

Fergus Client maps directly to Odoo res.partner. Odoo stores the client type (company vs individual) in the is_company boolean and the contact type in partner properties. Client-level pricing tiers from Fergus become Odoo Pricelist rules linked to the partner record post-migration.

Fergus Contact maps to res.partner records of type 'contact' linked to the parent client partner via the parent_id field. Fergus contact mobile and phone fields map to Odoo's phone and mobile fields. Email addresses map directly to the email field on the partner record.

Fergus Quotes map to Odoo sale.order records in draft state. Fergus quote line items map to sale.order.line records. The Fergus quote status (draft, sent, accepted, declined) maps to Odoo's state field (draft, sent, sale_order, cancel) with a manual status review step before go-live.

Fergus Jobs map to Odoo crm.lead records with type='opportunity'. The job name becomes the opportunity name. Job status maps to crm.stage using Odoo's default stage pipeline (New, Qualified, Proposal, Negotiation, Won, Lost). Fergus job-assigned staff map to Odoo's user_id via email match.

Fergus job line items with a service description split into two Odoo records: the service line becomes a sale.order.line with the linked product, and the labour description becomes a note on the crm.lead record. Material and labour amounts are stored in separate x_material_amount and x_labour_amount custom fields for reporting continuity.

Fergus Pricing Tiers do not have a direct Odoo equivalent. Each tier's rate rules are exported as Odoo Pricelist rules on the product.product record. Unmatched tier rates are stored as a JSON-formatted custom field (x_pricing_tier_rules__c) on the res.partner for manual Pricelist recreation in Odoo Studio.

Fergus Invoices map to Odoo account.move records of type='out_invoice'. Line items map to account.move.line with debit/credit based on the Fergus invoice amount and tax configuration. Fergus invoice status (paid, overdue) maps to Odoo's payment_state field using value mapping.

Fergus Assets at a client site map to Odoo maintenance.equipment records linked to the client res.partner via the partner_id field. The asset name, serial number, and location fields map directly to Odoo's name, serial_no, and location fields.

Fergus Staff records map to Odoo res.users by email match. Active staff get Odoo user accounts with the CRM extension rights. Inactive or archived staff are created as Odoo portal users so historical job attribution is preserved without granting internal access.

Fergus files attached to Quotes and Jobs are downloaded and re-uploaded to Odoo ir.attachment records linked to the corresponding sale.order or crm.lead via res_model and res_id. Odoo's default 25MB per-file limit applies; files exceeding this are flagged before migration.

Fergus workflows that trigger job creation when a quote is accepted do not transfer. The automation logic must be rebuilt in Odoo using Studio automation rules or server actions triggered on sale.order state change to 'sale_order'.

Fergus payment gateway configuration (Stripe, PayPal links) does not migrate. Odoo's payment providers are configured independently in Accounting > Configuration > Payment Providers. We provide a rebuild checklist with the Fergus payment provider names and credentials for your Odoo admin to re-enter.

Fergus business-wide settings such as default tax rates, invoice numbering sequences, and default job templates do not have Odoo equivalents that migrate automatically. These are documented in a settings export sheet for manual configuration in Odoo Accounting and CRM settings screens.