Migrate from work4all to Twenty CRM

work4all Customers are the primary organisational anchor with address, contact details, commercial terms, and open items attached. We map them to Twenty Company records. The work4all customer number becomes the Company id field, and address data maps to Twenty's address compound field. If the work4all Customer has linked personal contact persons (Ansprechpartner), those become separate Person records in Twenty linked to the Company via the people array on the Company object.

work4all Suppliers mirror the Customer structure with address, contact details, and purchasing history. We map Suppliers to Twenty Company records with a custom field source_type__c set to 'supplier' to distinguish them from Customer Companies in list views and reports. If the customer wants to keep Customers and Suppliers in separate Twenty workspaces, we map Suppliers to a second Company workspace or a custom Company subtype.

work4all Sales Opportunities track pipeline progress, estimated value, stage, and linked Customer. We map each to a Twenty Opportunity with stageName from the work4all pipeline stage, amount from the opportunity value, and the linked Customer resolved to a Company lookup. Closed-Won and Closed-Lost outcomes and any stage probability data migrate as custom fields.

work4all Items are the product catalogue with pricing, descriptions, stock levels, and variants. We map Items to either Twenty's Product object (if used for sales quoting) or a custom 'Product' object (if used for inventory reference). Price list structures flatten into a single pricebook or a custom price field depending on the customer's quoting workflow in Twenty.

work4all Invoices, Offers, and Cost Receipts are ERP documents linked to Customers and Items. These have no direct Twenty CRM equivalent because Twenty does not have a native ERP document object. We map document headers as a custom 'ERP Document' object with fields for document type, number, date, amount, and currency; line items map as child records of the custom object. PDF attachments require a separate file migration step with ContentDocument records linked to the parent.

Open items track outstanding invoices and credit memos against a Customer. We map them to a custom 'Open Item' object with fields for the related invoice reference (linked to the ERP Document custom object), open amount, due date, and payment status. Partial payments require reconciliation against the original invoice document to compute the correct open amount before migration.

Phone call logs are CRM activities linked to a Customer and an Owner in work4all. TAPI integration populates caller ID but the note body is free text. We map each call log to a Twenty Note or Task record with the body preserved, timestamp set from the call date, and the linked Customer resolved to a Company lookup. Call duration and disposition migrate as custom fields if present in the export.

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 map the report body as a Note body in Twenty, the visit date as the creation timestamp, and the linked Customer to the Company lookup. Any industry-extension custom fields on the visit report require pre-migration discovery and map to custom fields on the Note or a linked custom object.

Time entries in work4all link to Employees, Projects, or Tasks depending on configuration. Light-tier users have restricted time entry access. We map each time recording to a Twenty Task with the description, duration, date, and owner resolved via email match. Project-linked time entries require a custom 'Project' object in Twenty if the customer tracks project associations.

Standalone CRM Tasks in work4all carry status, priority, due date, and owner assignment linked to Customers, Contacts, or Documents. We map them directly to Twenty Task with status, due date, assignee resolved by email match, and the linked entity resolved to a Company or Person lookup. Status enums map from work4all's task-state values to Twenty's task status values.

work4all custom fields across CRM activities and ERP documents are not exposed via a metadata endpoint, so we discover them by requesting the customer to provide a screenshot or field inventory and by inspecting the exported schema for non-standard fields. Each discovered custom field is created as a custom field in Twenty's Data Model before the corresponding records are imported. Custom fields that cannot be enumerated from the export require a vendor-assisted schema inspection as an additional scoping step.