CRM migration
Field-level mapping, validation, and rollback between work4all and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
work4all
Source
Nutshell
Destination
Compatibility
7 of 11
objects map 1:1 between work4all and Nutshell.
Complexity
BStandard
Timeline
4-8 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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)
Nutshell
Account + Person (split required)
1:manywork4all 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)
Nutshell
Account (with type flag)
1:1work4all 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)
Nutshell
Product2
1:1work4all 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
Nutshell
Deal
1:1work4all 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)
Nutshell
Activity + Note
1:1work4all 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
Nutshell
Activity (type: Call)
1:1Phone 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
Nutshell
Activity + Note
1:1Visit 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)
Nutshell
Note or Custom Fields on Account
lossyOpen 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
Nutshell
Activity or Custom Fields on Account
lossyTime 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
Nutshell
Task
1:1Tasks 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)
Nutshell
Custom Fields (Companies, People, Leads, Activities)
lossywork4all 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.
| work4all | Nutshell | Compatibility | |
|---|---|---|---|
| Customer (Debitor) | Account + Person (split required)1:many | Fully supported | |
| Supplier (Kreditor) | Account (with type flag)1:1 | Fully supported | |
| Item (Artikel) | Product21:1 | Fully supported | |
| Sales Opportunity | Deal1:1 | Fully supported | |
| Invoice and ERP Document (Angebot, Rechnung, Kostennachweis) | Activity + Note1:1 | Fully supported | |
| Telephone Note and Call Log | Activity (type: Call)1:1 | Fully supported | |
| Visit Report | Activity + Note1:1 | Fully supported | |
| Open Item (Offene Posten) | Note or Custom Fields on Accountlossy | Fully supported | |
| Time Recording | Activity or Custom Fields on Accountlossy | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Custom Fields (industry extensions) | Custom Fields (Companies, People, Leads, Activities)lossy | Fully supported |
Gotchas + challenges
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 gotchas
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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
work4all
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across work4all and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
work4all: Not publicly documented.
Data volume sensitivity
work4all doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during work4all to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your work4all to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave work4all
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.