Migrate from work4all to Pipedrive

work4all Customer master records map to Pipedrive Organization. The Customer record is the primary organisational anchor with address, commercial figures, and open items all linked to it. We export the Customer name, address, and commercial data as Organisation name and address fields, using the work4all Customer number as an external reference identifier. Customer-level custom fields from industry extensions migrate as Organisation custom fields. Address records associated with a Customer export as multiple address fields on the Organisation.

work4all allows multiple Contact Persons per Customer. We map each Contact Person to a Pipedrive Person record linked to the parent Organisation by Organisation ID. The relationship between Contact Person and Customer is preserved by resolving the Organisation ID before Person records are inserted. Each Person record receives the contact's name, email, phone, role, and any linked activity history.

work4all Supplier master records mirror the Customer structure with address and contact details. We map Suppliers to Pipedrive Organisation records with a custom field source_type__c set to Supplier to distinguish them from Customers. The customer's admin can use this flag to filter supplier-related Deals or link them to a separate Supplier pipeline if one is configured.

work4all Sales Opportunities map to Pipedrive Deals. Each opportunity carries a current stage, estimated value, linked Customer, and Contact Person reference. We map the opportunity value to Deal value, the stage to a Pipedrive Pipeline stage, and the linked Customer and Contact to Organisation and Person lookups resolved during migration. The original opportunity creation date migrates as the Deal's add_time for historical ordering.

work4all Item master records include pricing, descriptions, and stock information. We map Items to Pipedrive Products with the item code as the product code, item name as the product name, and pricing migrated as standard pricing on the Product record. Item variants in work4all map to separate Product records or product variations depending on the destination Pipedrive configuration.

work4all ERP documents (Offers, Invoices, Cost Receipts) are linked to Customers and Items but do not have a direct Pipedrive equivalent because Pipedrive is a sales CRM rather than an accounting system. We export document headers and line items as structured Activity records of type Note, linked to the corresponding Organisation and Deal, with the document type and number stored in custom fields. The customer's admin rebuilds invoice and offer workflows in an accounting integration post-migration.

work4all telephone call logs are CRM activities linked to Customers and Contacts. The TAPI integration populates caller ID within work4all, but exported notes are free-text summaries with a timestamp. We map these to Pipedrive Activities of type Call, linked to the corresponding Person and Organisation. Call duration (if available) migrates as a custom duration field on the Activity.

Visit Reports in work4all 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 the Activity title and description in Pipedrive, map the visit date to the Activity due date, and link the Activity to the Organisation and the resolved Owner as the assigned user.

work4all Open Items track outstanding invoices and credit memos. Pipedrive does not have a native accounts-receivable or open-item object. We export open items as Activity records linked to the Organisation, storing the invoice reference, open amount, due date, and currency in custom fields on the Activity. Partial payments require reconciliation against payment history before export; we flag this during scoping and request payment records from work4all if partial payments exist.

work4all Tasks are standalone CRM objects linked to Customers, Contacts, or Documents with status, priority, due dates, and owner assignments. We map these to Pipedrive Activities of type Task, preserving status, priority, due date, and the resolved Organisation and Person lookups. Task assignment migrates by resolving the work4all Owner reference to a Pipedrive user by email match.

work4all Time Recordings are linked to Employees, Projects, or Tasks depending on configuration. Pipedrive does not have a native time-tracking object. We export time entries as Activity records of type Note with a custom time_entry__c flag, storing project, task, and owner references in custom fields. If the customer requires ongoing time tracking, we recommend a Pipedrive integration with a dedicated time-tracking tool as a post-migration configuration step.

work4all supports custom fields across CRM and ERP objects, particularly in industry extensions, but these are not exposed in a self-service metadata endpoint. We address this by asking the customer to provide a screenshot or field inventory of any custom fields they have created. If the customer cannot enumerate them, we attempt schema inspection of the exported data to detect fields not in the standard object list. We then pre-create the corresponding custom fields in Pipedrive before data import begins, matching field type as closely as Pipedrive's typed custom field system allows.