Migrate from work4all to Odoo CRM

work4all Customer master data maps to Odoo res.partner with partner_type set to 'contact' and customer_rank set to a positive value. The Customer's commercial figures (credit limit, payment terms) map to Odoo's internal fields on res.partner where supported. The customer's primary address becomes the partner's main address record; additional addresses map to res.partner with type='delivery' or type='invoice'. We flag any industry-extension custom fields discovered in the exported schema for manual mapping in Odoo Studio post-migration.

work4all Supplier master data maps to Odoo res.partner with supplier_rank set and partner_type left blank or set to 'supplier'. Supplier purchasing history (last purchase price, default lead times) map to equivalent fields if present in the export; otherwise we preserve as custom fields on the partner record. The same address-role splitting logic applies as with Customers.

work4all Items map to Odoo product.template with product variants handled via product.attribute and product.attribute.value if the source includes variant definitions. The item's pricing tiers map to Odoo product.pricelist.item entries on the applicable Pricelist. Stock quantity information from work4all's inventory module maps to Odoo's stock.quant records if the customer activates the Inventory app; otherwise we import the item without stock data and note the gap for the customer's inventory admin.

work4all Sales Opportunities map to Odoo crm.lead records with type='opportunity'. The opportunity's stage, estimated value, and linked Customer and Contact references migrate directly. work4all's opportunity-level custom fields (industry-extension fields visible in the export) map to crm.lead custom fields created in Odoo Studio before migration. Owner assignment from work4all maps to Odoo crm.lead user_id after User reconciliation in Step 5 of the approach.

work4all contact persons linked to a Customer map to Odoo res.partner records with parent_id pointing to the Customer partner record and type='contact'. Email, phone, and function/title fields migrate directly. The relationship graph between contact persons and their parent organisation is preserved by resolving the parent_id reference after the Customer partner records are created.

work4all ERP document headers and line items map to Odoo sale.order (for Quotes and Offers) or account.move (for Invoices and Cost Receipts) depending on document state. Draft or offered documents map to sale.order with state='draft'; sent or confirmed documents map to sale.order with state='sent' or 'sale'; posted accounting documents map to account.move with state='posted'. Document line items map to sale.order.line or account.move.line with product, quantity, and price resolved against the imported product catalogue.

work4all Open Items represent unpaid or partially paid invoices and credit memos. We export the open item with invoice reference, amount open, due date, and currency. Partial payments require the customer to confirm whether partial payment records exist and, if so, to provide payment history so we can reconstruct the correct open amount and create matching account.payment entries in Odoo. If payment history is unavailable, we flag the discrepancy and document it in the reconciliation report for the customer's accountant to resolve post-migration.

work4all telephone notes are CRM activities linked to a Customer and Contact with a free-text summary and timestamp. They map to Odoo crm.phone.call.log records if the customer's Odoo instance has the crm_phonecall module installed, or to crm.lead chatter notes if not. Caller ID and duration are preserved as custom fields where present in the export. TAPI caller-ID data is extracted from the note text field if it appears in a structured format.

work4all visit reports are time-stamped CRM records associated with a Customer and an Owner. They may contain custom fields depending on industry extension usage. We export the report body as plain text and create an Odoo note.note record linked to the relevant res.partner (customer). If the customer uses the Odoo Field Service module, we map visit reports to field.service.task or project.task with the customer set as the partner. Custom fields from industry extensions map to custom fields on the target object.

work4all Tasks are standalone CRM objects with status, priority, due date, and owner assignment. Tasks linked to a Customer map to Odoo project.task (if the customer uses project tracking) or to crm.lead if the task is pipeline-adjacent. Tasks with no CRM context map to project.task in a catch-all project created for migration purposes. Status and priority enums are mapped to Odoo's equivalent picklist values during the transform phase.

work4all time entries are linked to Employees, Projects, or Tasks depending on configuration. Light-tier users have restricted time entry access only, which we identify during scoping. Time recordings map to Odoo account.analytic.line records if the Project Management or Timesheet app is active; otherwise we export as note.note records with a time_spent field for manual re-entry. We resolve the Employee reference by matching against Odoo hr.employee records created from work4all's user list.

work4all supports custom fields across CRM activities and ERP documents, particularly in industry extensions, but these are not exposed in a self-service metadata endpoint. We address this by requesting the customer to provide a field inventory of any custom fields they have created, and by performing schema inspection on the exported data to detect fields not in the standard object list. Any discovered custom fields are pre-created in Odoo as custom fields on the mapped target object before the data load phase begins.