Migrate from work4all to Zoho CRM

Customer master records are the primary organisational anchor in work4all, carrying address, contact details, commercial figures, and open-item summaries. We export Customers as flat records with address parsed into the Zoho CRM Account standard address fields. work4all's customer type (Debitor/Kreditor distinction) maps to a Zoho CRM custom picklist field w4all_party_type__c to preserve the classification. Open-item summary amounts are not imported as standalone fields; they are reconstructed from invoice and payment data in a subsequent step.

Supplier master data mirrors the customer structure in work4all with address, contact details, and purchasing history. We map Suppliers to Zoho CRM Account records and flag them as vendors using the w4all_party_type__c custom field. If the destination Zoho CRM instance includes Zoho Books integration, the Account vendor flag synchronises to the vendor file in Zoho Books automatically.

work4all Item master records include pricing, descriptions, stock information, and variants. We export Items and variants into a flat product catalogue schema. Variant attributes (size, colour, material) that work4all stores as sub-items are flattened into Zoho CRM Product records with a custom variant identifier field. Pricing tiers from work4all map to Zoho CRM Product Pricing Details records. Standard price book entries are created in Zoho during import.

CRM-linked sales opportunities in work4all track pipeline stage, estimated value, expected close date, and linked Customer and Contact references. We map these to Zoho CRM Deals with StageName set from the work4all pipeline stage, Amount from estimated value, and Closing Date from the close date. The Deal is linked to the Account via Account Name lookup resolved from the parent Customer ID.

work4all stores Invoices, Offers, and Cost Receipts as ERP documents with header and line-item structure. Zoho CRM has no native invoice object. We present two options during scoping: map documents to Zoho CRM Deals with a custom document type field (Invoice, Offer, Cost Receipt) and line items stored as JSON in a long-text area field, or create a custom module Documents_C with a header subform for line items. The customer's admin chooses based on whether they will use Zoho Books for accounting post-migration. PDF attachments to ERP documents require a separate file migration step using Zoho Drive API.

Phone call logs in work4all are CRM activities linked to Customers and Contacts with free-text summaries and timestamps. The TAPI integration in work4all populates caller ID automatically, but exported notes are free-text. We migrate these as Zoho CRM Tasks with Task_Type = Call, preserving the timestamp as Activity Date, the free-text body as Description, and the linked Customer as the Parent ID lookup. Caller ID details that are structured (number, duration) are mapped to custom Task fields if they exist in the export.

Visit reports in work4all are time-stamped CRM records associated with a Customer and an Owner, potentially carrying custom fields from industry extensions. We export the report body as a Zoho CRM Task with Subject prefixed by 'Visit Report: ' and the full report body in the Description field. Any custom fields in work4all visit reports are enumerated during the discovery step and mapped to custom Task fields in Zoho CRM. Owner resolution maps the work4all user reference to a Zoho CRM User by email match.

Time entries in work4all are linked to Employees, Projects, or Tasks depending on configuration. Light-tier users have restricted time entry access only, which we flag during scoping. We export time entries with project reference, task reference, and owner. In Zoho CRM these migrate as Tasks with a custom time_entry flag and the duration stored in a custom integer field. If the destination Zoho CRM instance includes Zoho Projects integration, the time entries can be linked to Zoho Projects tasks as a post-migration integration step.

Standalone CRM Tasks in work4all carry status, priority, due dates, and owner assignments linked to Customers, Contacts, or Documents. We export all task fields including the status enum and owner reference. Migration to Zoho CRM Task preserves Status, Priority, Due Date, and Activity Date, with the work4all status values mapped to Zoho CRM Task Status values during the transform phase.

Open items represent unpaid or partially paid invoices and credit memos tied to Customers. work4all open items do not automatically include payment history; partial payments require the open amount to be calculated from the original invoice amount minus any recorded payments. We request the customer to confirm whether partial payments exist and, if so, ask the vendor to include payment records in the export or we reconstruct open amounts from invoice and payment data separately. Open items migrate as Zoho CRM Deals with Amount equal to the open amount, Stage = 'Closed Won' (representing the outstanding receivable), and a custom field w4all_open_item_ref__c carrying the original invoice reference. Due dates map to the Expected Close Date field.

work4all supports custom fields for CRM activities and ERP documents, particularly in industry extensions, but these are not exposed in a self-service interface or API. 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 a schema inspection of the exported data to detect fields not in the standard object list. Each discovered custom field is mapped to a Zoho CRM custom field of equivalent type: text fields to Zoho Text, dates to Date, picklists to Picklist. Custom fields with no equivalent Zoho type are mapped to Long Text and flagged in the migration report for admin review.