CRM migration

Migrate from work4all to Nutshell

Field-level mapping, validation, and rollback between work4all and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

work4all logo

work4all

Source

Nutshell

Destination

Nutshell logo

Compatibility

64%

7 of 11

objects map 1:1 between work4all and Nutshell.

Complexity

BStandard

Timeline

4-8 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Migrating from work4all to Nutshell is a structural decomposition as much as a data transfer. work4all combines CRM and ERP in a single platform where Customers are the master record carrying both contact details and commercial history; Nutshell uses a separate Account and Person model for commercial parties and a standalone Deal object for pipeline tracking. We split work4all Customers into Nutshell Accounts (company level) and Persons (contact level) using address and contact sub-records, map Suppliers to Accounts with a type flag, and resolve open-item and ERP document data into structured Activities or Notes. Because work4all has no published REST API, we coordinate vendor-assisted database exports or iterate the built-in Excel import templates in reverse, which adds scheduling coordination to every migration. Custom fields from work4all's industry extensions are discovered via schema inspection and pre-created in Nutshell before any record import. We do not migrate workflows, automations, or ERP configurations; these are documented for your admin to rebuild in Nutshell's workflow builder.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

work4all logo

work4all

What's pushing teams away

  • 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.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How work4all objects map to Nutshell

Each row shows how a work4all object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

work4all

Customer (Debitor)

maps to

Nutshell

Account + Person (split required)

1:many
Fully supported

work4all Customers are the master record combining company address, contact person details, commercial figures, and open items. We split this into a Nutshell Account (company level: name, address, type, commercial fields) and a Person record (individual contact: name, email, phone, role, linked to the Account). The work4all Customer type field (Kunde, Interessent, etc.) informs whether the Account is created as a Company or a Lead in Nutshell. We preserve all open-item references by linking them to the Account after both records are inserted.

work4all

Supplier (Kreditor)

maps to

Nutshell

Account (with type flag)

1:1
Fully supported

work4all Suppliers are first-class Kreditoren records with address and contact data mirroring the Customer structure. We map to Nutshell Account with a custom type field or Account category set to Supplier/Vendor. work4all Supplier contact persons become Nutshell Persons linked to the Supplier Account. If the customer's Nutshell instance uses separate Person records for both customers and suppliers, we deduplicate by email address to avoid creating duplicate Person records.

work4all

Item (Artikel)

maps to

Nutshell

Product2

1:1
Fully supported

work4all Items include pricing, descriptions, stock information, and variant structures. We map to Nutshell Product2 records with ProductCode from work4all's article number and Description from the item text. Item variants in work4all (Größen, Farben) require flattening into separate Product2 records or a custom variant field depending on the customer's use case. Standard Pricebook entries are created in Nutshell during the product import phase.

work4all

Sales Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

work4all Opportunities link to a Customer and carry pipeline stage, estimated value, and owner assignment. We map to Nutshell Deal with the Account resolved from the linked Customer, the Person resolved from the contact reference, estimated value migrated to the Deal value field, and stage mapped to the corresponding Nutshell pipeline stage. Owner resolution is by email match against Nutshell Users.

work4all

Invoice and ERP Document (Angebot, Rechnung, Kostennachweis)

maps to

Nutshell

Activity + Note

1:1
Fully supported

work4all ERP documents are header-plus-line-item structures linked to Customers and Items. We export document headers (type, date, amount, currency, reference number) and line items as structured records. In Nutshell, document headers become Notes attached to the Account (with a structured description field or custom fields for amount, date, and document type). PDF attachments require a separate file migration step using ContentDocument upload. ERP document line items are stored as Note body text or custom fields on the Note.

work4all

Telephone Note and Call Log

maps to

Nutshell

Activity (type: Call)

1:1
Fully supported

Phone call logs in work4all are CRM activities linked to a Customer and a contact person. We map to Nutshell Activity with type = Call, preserving the timestamp, duration, caller ID if populated from TAPI, and a free-text notes field. The Activity is linked to the Account and Person resolved from the work4all Customer and contact references.

work4all

Visit Report

maps to

Nutshell

Activity + Note

1:1
Fully supported

Visit reports in work4all are time-stamped CRM records linked to a Customer and an owner. We export the report body as a Note or Activity description, with the visit date as ActivityDate and the owner resolved by email match. Custom fields on visit reports (common in industry extensions) are pre-created in Nutshell as custom fields on the Activity or Note object before migration.

work4all

Open Item (Offene Posten)

maps to

Nutshell

Note or Custom Fields on Account

lossy
Fully supported

Open items represent unpaid or partially paid invoices tied to a Customer. We export the open item with invoice reference, open amount, due date, and currency. Partial payments require either a vendor-assisted export of payment records or reconstruction from invoice minus payment data. In Nutshell, open-item data is stored as structured Note content or as custom fields on the Account (offene_posten_typ__c, offene_posten_betrag__c, faelligkeitsdatum__c). The customer chooses the representation during scoping.

work4all

Time Recording

maps to

Nutshell

Activity or Custom Fields on Account

lossy
Fully supported

Time entries in work4all link to Employees, Projects, or Tasks depending on configuration. We export the entry with project reference, task description, and duration. Nutshell has no native project or time-tracking object, so time entries are mapped to Notes attached to the relevant Account or Person, or to custom fields (project_name__c, task_description__c, duration_minutes__c) on a custom object if the customer requires structured time reporting. The customer selects the representation during scoping.

work4all

Task

maps to

Nutshell

Task

1:1
Fully supported

Tasks in work4all are standalone CRM objects linked to Customers, Contacts, or Documents with status, priority, due date, and owner assignment. We map directly to Nutshell Task preserving Status, Priority, ActivityDate, Description, and Owner resolved by email match. Linked record references map to Account or Person lookups in Nutshell.

work4all

Custom Fields (industry extensions)

maps to

Nutshell

Custom Fields (Companies, People, Leads, Activities)

lossy
Fully supported

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 asking the customer for a field inventory or by schema inspection of exported data. We pre-create each custom field in Nutshell (Company, Person, Lead, or Activity custom fields) before migration. Note: Nutshell's API does not support searching records by custom field values, so we validate custom field migration by retrieving records post-insert and comparing field values rather than by pre-flight query.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

work4all logo

work4all gotchas

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • work4all has no public REST API; vendor-assisted export required

    work4all does not publish a public API reference. Data export is handled through built-in Excel import templates for Customers, Suppliers, and Items, and through custom vendor-scripted exports for other objects including Activities, Tasks, and ERP documents. We coordinate with the work4all vendor to run a database-level export or to provide the standard Excel exports. This adds three to five business days to the discovery and export phase compared to platforms with open APIs. Any custom fields not present in the standard Excel template require a separate vendor engagement to extract, which we scope as an additional work item during discovery.

  • Light licence users cannot export full CRM or ERP data

    work4all's Light licence tier (above €6 per month) is designed for field technicians who only need time tracking and delivery note access. It restricts access to full CRM activities and ERP document detail. During discovery we identify every user with a Light licence and confirm which data objects their accounts can reach. If a technician's call logs, visit reports, or time entries are locked under a restricted account, we request an upgrade to Professional tier or an admin-assisted export before migration scoping is finalised. Without this step, technician activity history is silently excluded from the migration.

  • Nutshell API does not support searching by custom field values

    Nutshell's JSON-RPC API does not support filter conditions on custom field values in its find or search methods. A Stack Overflow community post and Nutshell developer documentation confirm that custom field values can be written and read but cannot be used as query criteria. This means we cannot perform pre-flight validation by querying Nutshell for records matching a custom field value after migration. Instead, we validate custom field migration by retrieving each inserted record individually via its ID and comparing the returned custom field values against the source data. This adds a read-back step to every custom field migration.

  • Open items require reconciliation against payment history before export

    work4all's open items (Offene Posten) track outstanding invoices and credit memos but do not automatically include payment history. If a customer has partial payments, the open amount must be calculated from the original invoice amount minus any recorded payments. We request the customer to confirm whether partial payments exist and, if so, we ask the work4all vendor to include payment records in the export or we reconstruct open amounts from invoice and payment data separately. Without this step, partially paid invoices are exported at the full original amount, overstating open-item balances in Nutshell.

  • German-language data requires encoding consideration during export

    work4all is a German-language platform and stores data in German locale encoding. Excel exports may use Windows-1252 or ISO-8859-1 encoding depending on the export configuration. Nutshell's API expects UTF-8 JSON. We handle encoding conversion as part of the ETL pipeline, but we explicitly request the work4all vendor to provide exports in UTF-8 or standard Excel XML format to minimise encoding risk. Characters with diacritics (ä, ö, ü, ß) and special punctuation are validated after insertion to confirm correct rendering.

Migration approach

Six steps for a successful work4all to Nutshell data migration

  1. Discovery and export capability audit

    We audit the work4all instance across licence tiers (Light, Basic, Professional, Ultimate), active data objects, custom field usage (via customer-provided inventory or schema inspection of trial exports), and open-item and ERP document volume. We identify every Light-licence user and flag which data objects their accounts can reach. We request sample Excel exports from the work4all vendor for Customers, Suppliers, and Items to validate the template coverage of standard fields. We also confirm which ERP document types (Offers, Invoices, Cost Receipts) are actively used and whether open-item partial-payment history exists. The discovery output is a written scope and an export request list submitted to the work4all vendor.

  2. Export coordination and Nutshell schema preparation

    We coordinate with the work4all vendor to deliver the full data export in the agreed format (Excel, CSV, or vendor-scripted database export). While awaiting the export, we prepare the Nutshell destination schema: creating custom fields for all identified work4all custom fields, configuring the sales pipeline with stages mapped from work4all opportunity stages, and setting up Account categories or custom fields to distinguish Suppliers from Customers. We create the Nutshell API integration credentials and validate write access to all target objects.

  3. Data transformation and sandbox migration

    We transform the work4all export into Nutshell-compatible format: splitting Customers into Account and Person records, mapping Supplier type flags, flattening item variants into Product2 records, and structuring open-item and time-recording data according to the representation chosen during scoping. We run a full migration into a Nutshell trial or sandbox environment to validate record counts, custom field population, and relationship integrity (Account-to-Person links, Account-to-Deal links). The customer reconciles 25-50 spot-check records against the work4all source and signs off before production migration begins.

  4. Owner and user reconciliation

    We extract every distinct owner referenced on work4all Deals, Tasks, Activities, and Visit Reports and match by email against Nutshell Users. Any work4all owner without a matching Nutshell User goes to a reconciliation queue for the customer to provision. OwnerId references on Deals, Tasks, and Activities cannot be resolved until the User mapping is complete, so this step gates the production migration.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Product2 records first ( Deals reference Products ), then Accounts (from work4all Customers and Suppliers), then Persons (linked to Accounts), then Deals (with AccountId, PersonId, and OwnerId resolved), then Activities (Calls, Meetings, Notes, Tasks), then ERP document history as Notes or custom fields on Accounts, then open-item data and time recordings in the agreed representation. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and workflow handoff

    We freeze work4all writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of work4all workflows, automations, and ERP configurations that require rebuild in Nutshell, including any work4all industry extension functions. We support a one-week hypercare window for reconciliation issues. We do not rebuild work4all automations as Nutshell workflows inside the migration scope; that is a separate engagement.

Platform deep dives

Context on both ends of the pair

work4all logo

work4all

Source

Strengths

  • Combines CRM and ERP in a single platform with shared master data, eliminating duplicate entry between sales and accounting workflows.
  • Supports both cloud-hosted and on-premise server deployment, giving customers control over where their data resides.
  • Industry-neutral base platform with optional industry extensions, allowing targeted functionality without forcing a vertical-specific tool.
  • Pricing model is proportional to role: Light licences for field technicians at low cost, Professional and Ultimate for power users with full CRM and ERP access.
  • Over 35 years of continuous development with 1,000+ corporate customers indicates stability and domain expertise in SME resource planning.

Weaknesses

  • Limited documented public API constrains automated integrations and migration tooling, making data export largely dependent on Excel templates and vendor-assisted custom imports.
  • Windows desktop-first architecture creates friction for organisations expecting browser-based or mobile-native access to core ERP functions.
  • No widely reviewed tier-specific feature matrix makes it difficult to compare licensing options or understand what is locked behind higher tiers without direct vendor engagement.
  • GDPR compliance tooling is not prominently documented, which may concern customers in regulated industries handling EU personal data.
  • Customer reviews are sparse on public platforms (G2 shows limited verified reviews), making independent evaluation harder for prospective buyers.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across work4all and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    work4all: Not publicly documented.

  • Data volume sensitivity

    B

    work4all doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your work4all to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about work4all to Nutshell data migrations

Answers to the questions buyers ask most during work4all to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your work4all to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most work4all to Nutshell migrations land between four and eight weeks for accounts with fewer than 10,000 customer records, no active ERP document migration, and no large time-recording histories. Migrations with full open-item history, supplier records, ERP document mapping to Notes or Activities, industry-extension custom fields, or large activity histories (over 100,000 engagement records) move to eight to fourteen weeks because of vendor-export coordination, schema inspection for undiscoverable custom fields, and the dependency chain between Account, Person, and Deal inserts.

Adjacent paths

Related migrations to explore

Ready when you are

Move from work4all.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day