Migrate your work4all data
German all-in-one CRM and ERP for small-to-medium businesses, covering the full customer lifecycle from first contact through accounting in a single Windows-based platform.
In its favor
Why people choose work4all
The signal that keeps work4all on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
All-in-one CRM and ERP reduces the need for multiple disconnected tools, which resonates with small teams who want a single source of truth from initial contact through to invoicing.
Digital time tracking for field technicians is purpose-built for service businesses, making it accessible for non-desk workers to log time directly in the platform.
User-based licensing with a Light tier starting above 6 euros accommodates field technicians who only need time tracking and delivery note access, keeping costs proportional to role.
The platform is fundamentally industry-neutral but ships with industry extensions, allowing businesses in sectors like manufacturing, trade, and services to add sector-specific functions on top of a standard base.
Fast and highly rated customer support is frequently cited in reviews as a key differentiator that reduces friction during onboarding and ongoing operation.
Organisations scaling beyond 250 users or with complex multi-entity structures find the platform's architecture constraining and look toward enterprise-grade ERP systems like SAP or Microsoft Dynamics.
Teams that require extensive API-driven integrations or custom automation find work4all's limited public API documentation a blocker for modern CI/CD and data pipeline workflows.
Businesses seeking a modern web-first or mobile-native experience report friction with the Windows-desktop-first interface, which lacks the UX polish of newer SaaS alternatives.
Some customers cite difficulty achieving full GDPR compliance tooling within the platform, particularly around automated data retention policies and audit trails for deleted records.
Reasons to switch
Why people leave work4all
The recurring reasons buyers give for replacing work4all. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where work4all fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
work4all pricing overview
work4all uses per-user, per-month licensing across four tiers. Light starts above 6 euros per month for role-restricted technician access. Professional is priced at 55 euros per user per month and represents the most common tier for full CRM and ERP functionality. Basic and Ultimate pricing is not publicly disclosed and requires direct contact with the vendor.
Light
Tier 1 of 4
>6€ per user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on work4all's schedule — see our quote-based pricing →
What gets migrated
work4all object support
Object-by-object support for work4all migrations. Per-pair details surface during scoping.
Customers (Debitoren)
Fully supportedCustomer master data is the primary organisational anchor in work4all. Address, contact details, commercial figures, and open items are all linked to the Customer record. We export this as a flat record with embedded contact persons and address history preserved in a related table.
Suppliers (Kreditoren)
Fully supportedSupplier master data mirrors the customer structure with address, contact details, and purchasing history. We map Suppliers to the destination system's Vendor or Supplier object with a source type flag to distinguish them from customers.
Items (Artikel)
Fully supportedItem master records include pricing, descriptions, and stock information. The platform supports item variants and price list structures that we flatten into a standard product catalogue schema, preserving pricing tiers where they exist.
Sales Opportunities
Fully supportedCRM-linked sales opportunities track pipeline progress, values, and associated contacts. We export each opportunity with its current stage, estimated value, and linked Customer and Contact references as a distinct object.
Invoices and ERP Documents
Mapping requiredInvoices, offers, and cost receipts are stored as ERP documents linked to Customers and Items. We export document headers and line items as structured records, noting that PDF attachments require a separate file export pass, and credit notes must be distinguished from invoices by document type flag.
Telephone Notes and Call Logs
Mapping requiredPhone call logs are CRM activities linked to Customers and Contacts. The TAPI integration populates caller ID automatically, but exported notes are free-text summaries; we preserve the timestamp and duration if available, otherwise we flag them as text-only.
Visit Reports
Mapping requiredVisit 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 text and map any structured custom fields individually.
Time Recordings
Mapping requiredTime entries are linked to Employees, Projects, or Tasks depending on configuration. Light-tier users have restricted time entry access only. We export the time entry with project, task, and owner references, flagging any entries that belong to users whose licences do not support full data export.
Tasks
Fully supportedTasks are standalone CRM objects linked to Customers, Contacts, or Documents. They carry status, priority, due dates, and owner assignments. We export all task fields including the status enum and owner reference, mapping status values to the destination system's equivalents.
Custom Fields
Mapping requiredwork4all supports custom fields across CRM and ERP objects, particularly for industry extensions. Custom field definitions are not exposed in a public metadata API, so we discover them by querying the database schema directly or by asking the customer to provide a field inventory before export scoping.
Open Items (Offene Posten)
Mapping requiredOpen items represent unpaid or partially paid invoices and credit memos tied to Customers. We export the open item with the invoice reference, amount open, due date, and currency. Partial payments require reconstruction from payment records if the platform does not expose payment history separately.
| Object | Support | Notes |
|---|---|---|
| Customers (Debitoren) | Fully supported | Customer master data is the primary organisational anchor in work4all. Address, contact details, commercial figures, and open items are all linked to the Customer record. We export this as a flat record with embedded contact persons and address history preserved in a related table. |
| Suppliers (Kreditoren) | Fully supported | Supplier master data mirrors the customer structure with address, contact details, and purchasing history. We map Suppliers to the destination system's Vendor or Supplier object with a source type flag to distinguish them from customers. |
| Items (Artikel) | Fully supported | Item master records include pricing, descriptions, and stock information. The platform supports item variants and price list structures that we flatten into a standard product catalogue schema, preserving pricing tiers where they exist. |
| Sales Opportunities | Fully supported | CRM-linked sales opportunities track pipeline progress, values, and associated contacts. We export each opportunity with its current stage, estimated value, and linked Customer and Contact references as a distinct object. |
| Invoices and ERP Documents | Mapping required | 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, noting that PDF attachments require a separate file export pass, and credit notes must be distinguished from invoices by document type flag. |
| Telephone Notes and Call Logs | Mapping required | Phone call logs are CRM activities linked to Customers and Contacts. The TAPI integration populates caller ID automatically, but exported notes are free-text summaries; we preserve the timestamp and duration if available, otherwise we flag them as text-only. |
| Visit Reports | Mapping required | 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 text and map any structured custom fields individually. |
| Time Recordings | Mapping required | Time entries are linked to Employees, Projects, or Tasks depending on configuration. Light-tier users have restricted time entry access only. We export the time entry with project, task, and owner references, flagging any entries that belong to users whose licences do not support full data export. |
| Tasks | Fully supported | Tasks are standalone CRM objects linked to Customers, Contacts, or Documents. They carry status, priority, due dates, and owner assignments. We export all task fields including the status enum and owner reference, mapping status values to the destination system's equivalents. |
| Custom Fields | Mapping required | work4all supports custom fields across CRM and ERP objects, particularly for industry extensions. Custom field definitions are not exposed in a public metadata API, so we discover them by querying the database schema directly or by asking the customer to provide a field inventory before export scoping. |
| Open Items (Offene Posten) | Mapping required | Open items represent unpaid or partially paid invoices and credit memos tied to Customers. We export the open item with the invoice reference, amount open, due date, and currency. Partial payments require reconstruction from payment records if the platform does not expose payment history separately. |
Gotchas
What to watch for in work4all migrations
Issues we've hit on past work4all migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Light licence users cannot export all data types
No public REST API; migrations rely on Excel templates and vendor-assisted exports
Custom fields are not discoverable via a metadata endpoint
Open items require reconciliation against payment history before export
| Severity | Issue |
|---|---|
| High | Light licence users cannot export all data types |
| High | No public REST API; migrations rely on Excel templates and vendor-assisted exports |
| Medium | Custom fields are not discoverable via a metadata endpoint |
| Medium | Open items require reconciliation against payment history before export |
Leaving work4all?
Where work4all customers move next
12 destinations work4all can migrate to.
How a work4all migration works
Four steps, work4all-specific
Connect
Not publicly documented into work4all. Scopes limited to read-only on the data we move.
Map
We translate work4all-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate work4all quirks before production.
Migrate
Full migration with work4all rate-limit handling. Rollback available throughout.
FAQ
work4all migration FAQ
Answers to the questions buyers ask most during work4all migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your work4all migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate work4all.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your work4all setup and destination — written quote back within a business day.