CRM migration

Migrate from work4all to Microsoft Dynamics 365 Sales

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

work4all logo

work4all

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

80%

8 of 10

objects map 1:1 between work4all and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from work4all to Microsoft Microsoft Dynamics 365 Sales is a migration from a German Windows-desktop ERP-CRM hybrid to a cloud-native Microsoft CRM with deep Microsoft 365 integration. work4all organises data around Customers, Suppliers, Items, and Business Partners with ERP documents (Offers, Invoices) and CRM activities (Telephone Notes, Visit Reports, Sales Opportunities) linked to those parties, but it exposes no public API for automated export. We coordinate a vendor-assisted database export or reverse-iterate the Excel import templates to extract the data, then map Customer and Supplier records to Dynamics 365 Accounts with a source-type flag to preserve the distinction. Sales Opportunities map to Opportunities with stage probability translation; ERP document headers and line items migrate as structured Opportunity and Quote records where the customer requires them; Open Items require a partial-payment reconciliation step before export because work4all does not automatically calculate outstanding amounts. Workflows, automations, and custom Windows-server configurations do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Dynamics 365.

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How work4all objects map to Microsoft Dynamics 365 Sales

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

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

work4all

Customer (Debitoren)

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

work4all Customer master records (address, contact details, commercial figures, open items) map to Dynamics 365 Account. The Customer record is the primary organisational anchor in work4all, so we export it first and create Account records before any related Contact or Opportunity import to satisfy lookup dependencies. We preserve the original Customer number in a custom field w4a_customer_number__c for audit and cross-reference.

work4all

Supplier (Kreditoren)

maps to

Microsoft Dynamics 365 Sales

Account (with source-type flag)

1:1
Fully supported

work4all Supplier master records mirror the Customer structure with address and purchasing history. We map Suppliers to Dynamics 365 Account with a custom account type field (account_type = 'Vendor') to distinguish them from Customer Accounts. If the destination includes Business Central, the supplier maps to the Vendor table there instead, and the Microsoft Dynamics 365 Sales Account is used as a purchasing Contact organisation.

work4all

Contact Person (Kontaktperson)

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

work4all Contact Persons linked to Customers and Suppliers map to Dynamics 365 Contact records. The Contact is linked to its parent Account via the AccountId lookup. We resolve the parent Account reference at migration time so that Contact insert respects the lookup relationship.

work4all

Sales Opportunity

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

work4all Sales Opportunities track pipeline stage, estimated value, and linked Customer and Contact references. We map them to Dynamics 365 Opportunity with stage translation from work4all's pipeline stage names to the configured Salesforce Opportunity Stage values. Estimated value migrates to Amount; close date migrates to CloseDate; the linked Customer reference becomes AccountId.

work4all

Items (Artikel)

maps to

Microsoft Dynamics 365 Sales

Product2

1:1
Fully supported

work4all Item master records include pricing, descriptions, and stock information. We map Items to Dynamics 365 Product2 with Standard Pricebook entries created during import. The work4all item number becomes Product Code; item description becomes Name. If the customer uses pricing lists in work4all, we create multiple PricebookEntry records per Product.

work4all

Invoices and ERP Documents (Offers, Invoices, Cost Receipts)

maps to

Microsoft Dynamics 365 Sales

Quote or Opportunity Product Line Item

lossy
Fully supported

work4all ERP document headers and line items are exported as structured records. Invoices for closed-won Opportunities map to Opportunity with Closed Won stage and historical line items as OpportunityLineItems. Open offers and quotations map to Dynamics 365 Quote records attached to the Opportunity. We flag that PDF attachments require separate file migration to SharePoint or Dynamics 365 Notes with ContentDocumentLink.

work4all

Open Items (Offene Posten)

maps to

Microsoft Dynamics 365 Sales

Opportunity (configuration)

lossy
Mapping required

work4all Open Items track outstanding invoice and credit memo amounts but do not automatically include payment history. We request partial-payment records from the vendor export to reconstruct the open amount as original_invoice_amount minus recorded_payments. The open item becomes an Opportunity record or a custom open_items object depending on whether the customer wants to track unpaid invoices as pipeline opportunities or as a separate receivables view.

work4all

Telephone Notes and Call Logs

maps to

Microsoft Dynamics 365 Sales

Task (TaskSubtype = Call)

1:1
Mapping required

Phone call logs in work4all are CRM activities linked to Customers and Contacts with free-text summaries, caller ID (from TAPI integration), and timestamps. We map them to Dynamics 365 Task with TaskSubtype = Call, preserving the call summary as Description and the timestamp as ActivityDate. The linked Customer or Contact reference becomes the Regarding (regardingobjectid) lookup.

work4all

Visit Reports

maps to

Microsoft Dynamics 365 Sales

Note or Task

1:1
Mapping required

Visit reports are time-stamped CRM records associated with a Customer and an Owner in work4all. They may contain custom fields from industry extensions. We export the report body as a Note (if primarily narrative) or as a Task with custom fields (if action-oriented). Any industry-extension custom fields require schema inspection to enumerate.

work4all

Tasks

maps to

Microsoft Dynamics 365 Sales

Task

1:1
Fully supported

Standalone Tasks in work4all carry status, priority, due dates, and owner assignments linked to Customers, Contacts, or Documents. We map them to Dynamics 365 Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the work4all owner reference to the corresponding Dynamics 365 User by email match.

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

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • work4all has no public API; exports require vendor coordination

    work4all does not publish a public REST API reference. Data export is handled through built-in Excel import templates for Customers, Suppliers, and Items, and through custom vendor-scripted database exports for CRM activities and ERP documents. This adds 3-5 business days to scoping compared to platforms with open APIs. Any custom fields not visible in the standard Excel template require a separate vendor engagement to enumerate. We coordinate directly with the work4all vendor to schedule and execute the export, and we validate the extracted data against the source before beginning transformation.

  • Light licence users cannot export all data types

    The work4all Light licence tier restricts access to full CRM activities and ERP document detail. If field technicians or other Light-licence users have created time entries, call logs, or visit reports under restricted accounts, those records may be inaccessible without a licence upgrade or admin-assisted export. We audit every user licence tier during scoping, identify which data objects are reachable under each licence, and request a temporary upgrade or vendor-assisted export for any restricted accounts before migration begins.

  • Open items require partial-payment reconciliation before export

    work4all Open Items (Offene Posten) track outstanding invoices and credit memos but do not automatically include payment history. If the 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 ask the vendor to include payment records in the export, or we reconstruct open amounts from invoice and payment data separately. This step adds one to two days of reconciliation work per migration.

  • Custom fields are not discoverable via a metadata endpoint

    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 schema inspection of the exported data to detect fields not in the standard object list. This discovery step adds one to two weeks to scoping.

  • Workflows and automations do not migrate to Dynamics 365

    work4all workflows and any custom Windows-server configurations (including TAPI integration settings, industry extension behaviour, and any custom document templates) do not have a direct Dynamics 365 equivalent and cannot be migrated as code. Microsoft Dynamics 365 Sales uses Power Automate for workflow automation and model-driven Power Apps for custom extensions, which are architecturally different from work4all's automation model. We deliver a written inventory of every active work4all workflow and automation for the customer's admin to rebuild using Dynamics 365 workflow tools or a Microsoft partner.

Migration approach

Six steps for a successful work4all to Microsoft Dynamics 365 Sales data migration

  1. Discovery and licence audit

    We audit the source work4all instance across all licence tiers (Light, Basic, Professional, Ultimate), identifying which data objects are accessible under each licence and which require vendor-assisted export. We catalogue Customer, Supplier, Item, Sales Opportunity, ERP document, and CRM activity record counts. We request a sample vendor export to validate field coverage and identify any custom fields not present in the standard Excel templates. We pair this with a Microsoft Dynamics 365 Sales edition review (Professional at 65 euros per user per month covers standard CRM; Enterprise at 105 euros per user per month adds AI and advanced customisation if required). The discovery output is a written migration scope document and a Dynamics 365 edition recommendation.

  2. Vendor export coordination

    We coordinate directly with the work4all vendor to schedule the database export or custom query export for CRM activities, ERP documents, and open items. We provide the vendor with a structured export specification listing every object and field required, including any custom fields identified during discovery. We validate the export against a sample of 50-100 source records before accepting it as the migration dataset. If the vendor requires more than five business days to deliver, we negotiate an interim data freeze date.

  3. Schema design and mapping specification

    We design the destination Dynamics 365 schema based on the export data. This includes provisioning any required custom fields on Account, Contact, Opportunity, and Task objects, mapping work4all's opportunity stages to Dynamics 365 Opportunity Stage values, and configuring the Account source-type flag for Supplier records. If the customer also plans Business Central for ERP, we coordinate the Account-Vendor split so that the CRM Account and the ERP Vendor reference the same organisation record.

  4. Sandbox migration and reconciliation

    We run a full migration into a Dynamics 365 Sandbox using production-like data volume. The customer's admin reconciles record counts (Accounts in, Contacts in, Opportunities in, Activities in), spot-checks 25-50 random records against the work4all source, and reviews the Opportunity stage mapping. Any field-level corrections and mapping adjustments happen in the Sandbox before production migration begins.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (Customers and Suppliers with source-type flag), Contacts (with AccountId resolved), Opportunities (with AccountId and OwnerId resolved, stage translation applied), Products and Pricebook entries, Activity history (Tasks, Notes via Bulk API), Open Items (with partial-payment reconciliation applied). Each phase emits a row-count reconciliation report before the next phase begins. We coordinate with the work4all vendor to set a data-freeze date for the final delta migration.

  6. Cutover, validation, and handoff

    We freeze work4all writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the workflow and automation inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild work4all workflows as Dynamics 365 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.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. 1 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 Microsoft Dynamics 365 Sales .

  • Object compatibility

    B

    1 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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during work4all to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your work4all to Microsoft Dynamics 365 Sales 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 15,000 Customers and 3,000 Sales Opportunities with no complex ERP document history. Migrations with large ERP document histories (over 10,000 invoice line items), extensive custom field sets, or partial-payment open-item reconstruction move to eight to twelve weeks because of vendor coordination time, reconciliation steps, and schema inspection for custom fields.

Adjacent paths

Related migrations to explore

Ready when you are

Move from work4all.
Land in Microsoft Dynamics 365 Sales , 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