Migrate from Bill4Time to Odoo CRM

Bill4Time clients map to Odoo res.partner records. We preserve clientName as name, billingName as display_name override, and all address fields (address1/2/3, city, state, country, postalCode). The clientType field populates a custom partner_category_id for segmentation. Active/Disabled status maps directly to Odoo's active flag.

Bill4Time Enterprise Add-On custom fields on clients (text, number, date, list, client list, user list types) migrate as Odoo ir.model.fields x_name definitions on res.partner. List-type custom fields require value-mapping to Odoo selection fields or many2one relations depending on the source field's data type. JSON customFields payload is parsed and exploded into individual field writes.

Bill4Time projects map to Odoo crm.lead as opportunities. projectName becomes name, description carries over, clientId links to the corresponding res.partner via partner_id. billingMethod (Hourly/Flat Fee/Percentage) is stored in a custom Char field since Odoo opportunities lack a native billing method attribute — flat-fee deals may alternatively generate sale.order records if Odoo Sale app is active.

Bill4Time project-level custom fields migrate as custom fields on crm.lead. Fields such as hourlyOverrideRate, hourlyOvertimeOverrideRate, and billingMethod require corresponding Odoo custom Float and Selection fields. The projectType values are mapped via value_mapping to existing stage names in Odoo, or alternatively stored as a custom Char field for reference preservation during reporting.

Bill4Time time entries map to Odoo account.analytic.line (timesheet) records linked to the project (project_id) and the assigned user (user_id). entryDate becomes date, billableAmount populates unit_amount, and activityType sets the analytic line's name. isBillable flag preserves billability for reporting. Unbilled entries link to the crm.lead opportunity; already-invoiced entries link to the account.move.

Bill4Time invoices migrate to Odoo account.move records with move_type='out_invoice'. invoiceDate becomes invoice_date, invoiceAmount populates amount_total, laborAmount and expenseAmount are preserved in line amounts. invoiceNumber maps to Odoo's name sequence field. prebill status becomes draft; finalized maps to posted. paidStatus drives the move state: paid maps to posted with reconciled payments, partially paid creates a partial reconciliation.

Bill4Time expense entries map to Odoo hr.expense records if the HR/Expense app is active. expenseAmount becomes unit_amount, expenseType maps to product_id via a value-mapping table (e.g., 'Mileage' → mileage product, 'Travel' → travel product). clientId links the expense to the relevant res.partner. If hr.expense is not activated, expenses are stored as custom fields on crm.lead.

Bill4Time users map to Odoo res.users by email match. fname/lname populate name, email maps to login. userType (System Admin, Office Admin, Standard User, Limited User, Financial User) requires Odoo access rights mapping: System Admin → Group / System, Standard User → Group / User, Limited User → Group / Public. billingRate and overtimeRate store in custom fields on res.users for timesheet rate lookup.

Bill4Time assignedTo on projects maps to Odoo project team members. assignedTo is a single user in Bill4Time; Odoo project allows multiple members. We create the project with the primary assigned user and add additional members from any secondary assignments found in custom fields or notes. Unmatched user IDs are flagged for admin resolution before migration.

Bill4Time accountManagerId on clients maps to Odoo res.partner.user_id (the responsible salesperson field on the partner). This ensures the account manager is automatically assigned as the Odoo sales representative on the partner record, driving automated lead routing if Odoo's team assignment rules are active.

Bill4Time documents attached to clients or projects migrate as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead via res_model and res_id. Inline images in notes are downloaded and re-hosted in Odoo's filestore. Maximum file size follows Odoo's ir_attachment size limits; files exceeding the threshold are flagged for manual download links stored in a custom URL field.

Bill4Time workflow templates and automation rules do not have a destination equivalent in Odoo CRM. These must be rebuilt using Odoo Studio (for simple rules), Python server modules, or the OCA/automation-tools community modules. We export your Bill4Time workflow definitions as a structured JSON reference document to hand to your Odoo administrator for recreation.