Migrate from work4all to Salesforce Sales Cloud

work4all Customers are the primary organisational anchor with address, contact details, commercial figures, and open items all linked to the Customer record. We export this as a flat record and map it to Salesforce Account. The customer account number becomes the Account Number field and the primary lookup key. If the customer uses industry-specific extensions that add fields to the Customer record, we enumerate these during discovery and create matching custom fields on the Account before migration.

work4all Suppliers mirror the Customer structure with address, contact details, and purchasing history. We map Suppliers to Salesforce Account with a source_type flag set to Supplier, or to a custom Supplier object if the customer needs to keep supplier and customer data in separate schemas. The mapping decision is made during scoping based on the customer's downstream reporting needs.

work4all Item master records include pricing, descriptions, and stock information with support for item variants and price list structures. We flatten the variant structure into standard Product2 records, preserving the original item code as ProductCode and the description as Description. Price list entries are migrated as Standard Price Book entries against a Pricebook2 created during the schema phase.

work4all CRM-linked sales opportunities track pipeline progress, estimated values, and associated Customers and Contact Persons. We export each opportunity with its current stage, estimated value, and linked Customer and Contact references. Opportunity stage names map to Salesforce StageName values, and we create a Salesforce Sales Process and Record Type to scope the allowed stage values per the customer's work4all pipeline configuration.

work4all Contact Persons are sub-records linked to a Business Partner. We export them with their parent Customer or Supplier reference intact. During Salesforce import, we resolve the parent Account reference and link the Contact to the corresponding Account. If a Contact Person has no email or name, we flag it for the customer's admin to review before import because Salesforce requires FirstName or LastName on Contact.

work4all invoices, offers, and cost receipts are stored as ERP documents linked to Customers and Items. We export document headers and line items as structured records. For Salesforce, these map to Contract (for active customer agreements) or to a custom ERP Document object that the customer configures during scoping, since Salesforce does not have a native invoice object at Sales Cloud tier. PDF attachments require a separate file migration step using Salesforce ContentDocument and ContentVersion.

Phone call logs in work4all are CRM activities linked to Customers and Contact Persons. The TAPI integration populates caller ID automatically, but exported notes are free-text summaries. We preserve the timestamp, duration estimate (if stored), and the free-text body as a Salesforce Task with TaskSubtype=Call. The WhatId links to the Account; the WhoId links to the Contact resolved from the Contact Person export.

Visit reports are time-stamped CRM records associated with a Customer and an Owner in work4all. They may contain custom fields depending on industry extension usage. We export the report body as text and map any standard fields to Salesforce Task or Event depending on whether the visit was a scheduled meeting (Event) or a logged report (Task). Custom fields from industry extensions migrate as custom Task or Event fields after schema creation.

Time entries in work4all are linked to Employees, Projects, or Tasks depending on configuration. Light-tier users have restricted time entry access only. We export time entries with project, task, and owner references. In Salesforce, time recording requires either Salesforce Field Service (which includes timesheet objects) or a custom Time Sheet Entry object that we create during schema setup. We confirm the customer's preferred approach during scoping.

Open items in work4all represent unpaid or partially paid invoices and credit memos tied to Customers. We export the open item with the invoice reference, original amount, amount open, due date, and currency. Partial payments require reconstruction: we request the customer to confirm whether partial payments exist and, if so, we ask the vendor to include payment records in the export or we reconstruct open amounts from invoice and payment data separately. The destination is a custom Open Item object with a lookup to the Account and to the original Contract or ERP document record.

work4all Tasks are standalone CRM objects linked to Customers, Contact Persons, or Documents. They carry status, priority, due dates, and owner assignments. We export all task fields including the status enum and owner reference. Tasks map directly to Salesforce Task with Status, Priority, ActivityDate, and OwnerId preserved. Owner resolution is by email match against Salesforce User records.

work4all supports custom fields across CRM and ERP objects, particularly in industry extensions, but these are not exposed in a public metadata API. We discover custom fields by asking the customer to provide a screenshot or field inventory, or by inspecting the schema of exported data to detect fields not in the standard object list. For each discovered custom field, we create a matching custom field on the appropriate Salesforce object during the schema phase before data import begins.