CRM migration

Migrate from work4all to Freshsales

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

work4all logo

work4all

Source

Freshsales

Destination

Freshsales logo

Compatibility

58%

7 of 12

objects map 1:1 between work4all and Freshsales.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Migrating from work4all to Freshsales is a cross-architecture move: work4all is a Windows-desktop ERP-CRM hybrid with no published REST API, while Freshsales is a cloud-native AI-powered CRM with a fully documented API and CSV import tooling. The primary migration constraint is export access. work4all does not publish a public API; data export relies on built-in Excel import templates reversed in collaboration with the vendor, or on a vendor-scripted database export. We add a discovery step to every project enumerating which licence tiers (Light, Professional, Ultimate) can access which objects, because Light-tier technicians cannot export full CRM activity history. We map work4all Customers and Suppliers to Freshsales Accounts, Sales Opportunities to Deals, and time recordings and visit reports to Activities. Open items require a separate reconciliation pass because partial payments must be computed from invoice and payment data separately. We do not migrate workflows, automations, or the work4all time-tracking configuration; we deliver a written inventory of these for the customer's admin to rebuild in Freshsales.

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

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How work4all objects map to Freshsales

Each row shows how a work4all object lands in Freshsales, 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

Freshsales

Account

1:1
Fully supported

work4all Customer master records with address, commercial figures, and open-item totals map directly to Freshsales Account. The Customer number becomes the Account's external ID for dedupe. We use Account as the destination because work4all's customer-supplier distinction (Debitor/Kreditor) maps to the Account's industry_type or a custom account_type field rather than separate objects. If the customer uses both customer and supplier roles for the same business partner, we create a single Account with both roles flagged in the custom field.

work4all

Supplier (Kreditor)

maps to

Freshsales

Account

1:1
Fully supported

work4all Supplier master records mirror the Customer structure and map to Freshsales Account with a supplier_type flag. Where the same legal entity appears as both a Customer and Supplier in work4all, we create one Account record and use the custom field to indicate dual status rather than duplicating the record.

work4all

Contact Person (Ansprechpartner)

maps to

Freshsales

Contact

1:many
Fully supported

work4all Contact Persons linked to a Customer or Supplier map to Freshsales Contact records with a lookup to the Account. The primary contact flag, department, phone, and email transfer. If a Contact Person has multiple roles within the same business partner, we create separate Contact records linked to the same Account.

work4all

Item (Artikel)

maps to

Freshsales

Product2

1:1
Fully supported

work4all Item master records including pricing, descriptions, stock status, and variants map to Freshsales Product2. The work4all item number maps to Product Code. Item variants are flattened into individual Product2 records with a parent_product reference where the Freshsales plan supports it.

work4all

Sales Opportunity

maps to

Freshsales

Deal

1:1
Fully supported

work4all Sales Opportunities linked to a Customer and Contact map to Freshsales Deal with the Contact lookup and Account lookup resolved at migration time. Pipeline stage maps to Freshsales Deal stage. Estimated value and close date transfer directly.

work4all

Invoice and ERP Document (Angebot, Rechnung, Kostenbeleg)

maps to

Freshsales

Deal + Custom Object or Attachment

lossy
Fully supported

work4all ERP documents (Offers, Invoices, Cost Receipts) do not have a native equivalent in Freshsales CRM. We export document headers and line items as structured records and attach the original document as a file to the corresponding Deal or Account. For customers requiring invoice history as queryable records, we recommend a custom Invoice object (available from Freshsales Pro and above) or a post-migration AppExchange install such as Conga or an ERP connector.

work4all

Telephone Note (Telefonnotiz)

maps to

Freshsales

Task

1:1
Fully supported

work4all Telephone Notes linked to a Customer and Contact map to Freshsales Task with the activity timestamp preserved. The free-text note body transfers as the Task description. TAPI caller-ID data transfers as a custom field if the customer requires call log reconstruction.

work4all

Visit Report (Besuchsbericht)

maps to

Freshsales

Task or Event

lossy
Fully supported

work4all Visit Reports are time-stamped CRM records linked to a Customer and an Owner. We map them to Freshsales Task (if the report is summary-only) or Event (if it carries a scheduled start and end time). Custom fields on visit reports discovered during enumeration are recreated as Freshsales custom fields before migration.

work4all

Open Item (Offener Posten)

maps to

Freshsales

Deal or Custom Field on Account

lossy
Fully supported

work4all Open Items tracking unpaid invoices and credit memos require a separate reconciliation step because partial payments must be calculated from invoice amount minus any recorded payments. We export open-item records with invoice reference, open amount, due date, and currency. In Freshsales, open amounts are represented as a custom currency field on Account or as Deal records in a special 'Accounts Receivable' pipeline. The customer chooses the representation during scoping.

work4all

Time Recording (Zeiterfassung)

maps to

Freshsales

Task

1:1
Fully supported

work4all Time Entries linked to Employees, Projects, or Tasks map to Freshsales Task records. Light-licence users have restricted time-entry access only; we confirm during licence audit whether time recordings are accessible under the customer's current licence tier or require an upgrade or vendor-assisted export before migration scope is finalised.

work4all

Task

maps to

Freshsales

Task

1:1
Fully supported

work4all standalone Tasks linked to Customers, Contacts, or Documents map to Freshsales Task with status, priority, due date, and owner resolved. Owner resolution uses email matching against Freshsales User records. Any Task without a resolvable owner is held in the reconciliation queue for the customer's admin to provision the corresponding Freshsales user.

work4all

Custom Fields

maps to

Freshsales

Custom Fields

lossy
Mapping required

work4all custom fields on CRM activities and ERP documents (particularly those from industry extensions) require enumeration by the customer because no metadata API exposes them. We ask the customer to provide a field inventory or screenshots. If the customer cannot enumerate them, we inspect the exported data schema to detect non-standard fields. Custom fields are recreated in Freshsales Admin Settings before migration; plan limits apply: Blossom (10), Garden (100), Estate (300), Forest (300). We flag during scoping if the customer's custom field count exceeds the target plan limit.

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

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Light-licence users cannot export full CRM activity history

    The work4all Light licence tier is designed for field technicians who only need time tracking and delivery-note access. It restricts access to full CRM activities including sales opportunities, telephone notes, and visit reports. When scoping a migration, we audit every user account to identify which records are locked behind Light-licence restrictions. If a technician's time entries or visit reports are trapped in a restricted account, we request a licence upgrade or vendor-assisted export to prevent silent data loss in the technician activity history. This step adds three to five business days to the discovery phase.

  • 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 (iterated in reverse for Customers, Suppliers, and Items) and through custom vendor-scripted exports for CRM activities, ERP documents, and open items. We coordinate with the work4all vendor to obtain a database-level export or to run targeted queries. Any custom fields not visible in the standard Excel template require a separate vendor engagement to extract. This adds a minimum of three to five business days compared to platforms with open APIs, and any delay in vendor response directly extends the migration timeline.

  • Lead conversion field mapping required to avoid data loss

    Freshsales' Lead-to-Contact conversion process requires explicit field mapping for custom fields. If a work4all Contact Person maps to a Freshsales Lead during the initial migration, any custom fields not explicitly mapped in the Conversion Settings will be discarded at the moment of conversion. We recreate the full set of custom field definitions under Contacts and Deals before migration, then configure the lead field mapping in Freshsales Admin Settings to point source custom fields to their destination equivalents. This prevents silent data loss during Lead conversion after cutover.

  • Open-item partial-payment reconciliation adds a discovery step

    work4all 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 vendor to include payment records in the export or we reconstruct open amounts from invoice and payment data separately. The reconciled open amounts then transfer as custom currency fields on the corresponding Freshsales Account or as Deal records in a designated pipeline.

  • Custom field plan limits may require plan upgrade

    Freshsales custom field limits are plan-gated: Blossom (10 custom fields), Garden (100), Estate (300), Forest (300). work4all supports custom fields across CRM and ERP objects without a documented limit. During the custom field enumeration step, if we discover more custom fields than the customer's target Freshsales plan supports, we flag the deficit and recommend a plan upgrade before migration begins. Migrating to a lower plan than required would result in truncated custom fields or a second migration to a higher plan post-enumeration.

Migration approach

Six steps for a successful work4all to Freshsales data migration

  1. Discovery and licence-tier audit

    We audit the work4all instance across all licence tiers (Light, Basic, Professional, Ultimate) to identify which users can access which data objects. We enumerate the full list of objects in scope: Customers, Suppliers, Items, Sales Opportunities, Telephone Notes, Visit Reports, Tasks, Time Recordings, Open Items, and any ERP documents the customer wants migrated. We also request the customer to enumerate or screenshot any custom fields they have created in industry extensions. We assess the Freshsales target plan (Growth, Pro, Enterprise) against the discovered custom field count and open-item complexity.

  2. Export coordination with work4all vendor

    Because work4all has no public API, we coordinate a vendor-assisted export. For Customers, Suppliers, and Items, we use the built-in Excel import templates iterated in reverse. For CRM activities, ERP documents, and open items, we request the vendor to run database-level queries or custom scripted exports. We define the export format (CSV or structured JSON) and the field mappings upfront to minimise revision cycles. We flag any export that cannot be delivered within the agreed timeline and escalate to the customer's project manager.

  3. Schema design and custom field creation

    We design the destination Freshsales schema before any data moves. This includes creating all required custom fields (within the target plan limit), configuring Account types and Deal stages to match the customer's pipeline, setting up the conversion settings to map any Lead-source custom fields to their Contact and Account equivalents, and creating the migration user with the appropriate permissions. The schema is deployed into a Freshsales sandbox for validation before production migration begins.

  4. Sandbox migration and reconciliation

    We run a full trial migration into the customer's Freshsales sandbox using production-like data volume. The customer's project lead reconciles record counts against the work4all source export (Customers in, Suppliers in, Contacts in, Deals in, Activities in), spot-checks 20-30 records for field-level accuracy, and validates that open-item amounts match the source reconciliation. Any mapping corrections are documented and applied to the production migration plan. The customer signs off the sandbox results before production cutover is scheduled.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from work4all Customers and Suppliers), Contacts (linked to Accounts), Products (from Items), Deals (from Sales Opportunities with Account and Contact lookups resolved), Activities (Telephone Notes, Visit Reports, and Tasks via CSV import or API), and Open Items (as custom fields on Accounts or as Deals in a designated pipeline). Owner resolution uses email matching against Freshsales User records; unresolved owners are held in a queue for the customer's admin to provision. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and automation rebuild handoff

    We freeze work4all writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver a written inventory of work4all workflows, automations, and time-tracking configurations that do not migrate, with a rebuild guide for the customer's admin to reference in Freshsales. We support a five-business-day hypercare window where we resolve any data quality issues raised by the customer's team. We do not rebuild work4all automations as Freshsales workflows inside the migration scope; that is a separate engagement or an internal admin task.

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.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

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

  • 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 Freshsales 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 Freshsales data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 10,000 Customers, 2,000 Suppliers, and 1,000 open-item records with no complex custom field enumeration required. Migrations with multiple Light-licence accounts requiring upgrade coordination, large visit-report or time-recording histories, or open-item partial-payment reconciliation move to six to ten weeks because of the additional discovery rounds and vendor coordination for the export step.

Adjacent paths

Related migrations to explore

Ready when you are

Move from work4all.
Land in Freshsales, 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