CRM migration
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
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
8 of 10
objects map 1:1 between work4all and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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.
Source platform
work4all platform overview
Scorecard, SWOT, gotchas, and pricing for work4all.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
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 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)
Microsoft Dynamics 365 Sales
Account
1:1work4all 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)
Microsoft Dynamics 365 Sales
Account (with source-type flag)
1:1work4all 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)
Microsoft Dynamics 365 Sales
Contact
1:1work4all 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
Microsoft Dynamics 365 Sales
Opportunity
1:1work4all 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)
Microsoft Dynamics 365 Sales
Product2
1:1work4all 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)
Microsoft Dynamics 365 Sales
Quote or Opportunity Product Line Item
lossywork4all 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)
Microsoft Dynamics 365 Sales
Opportunity (configuration)
lossywork4all 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
Microsoft Dynamics 365 Sales
Task (TaskSubtype = Call)
1:1Phone 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
Microsoft Dynamics 365 Sales
Note or Task
1:1Visit 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
Microsoft Dynamics 365 Sales
Task
1:1Standalone 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.
| work4all | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Customer (Debitoren) | Account1:1 | Fully supported | |
| Supplier (Kreditoren) | Account (with source-type flag)1:1 | Fully supported | |
| Contact Person (Kontaktperson) | Contact1:1 | Fully supported | |
| Sales Opportunity | Opportunity1:1 | Fully supported | |
| Items (Artikel) | Product21:1 | Fully supported | |
| Invoices and ERP Documents (Offers, Invoices, Cost Receipts) | Quote or Opportunity Product Line Itemlossy | Fully supported | |
| Open Items (Offene Posten) | Opportunity (configuration)lossy | Mapping required | |
| Telephone Notes and Call Logs | Task (TaskSubtype = Call)1:1 | Mapping required | |
| Visit Reports | Note or Task1:1 | Mapping required | |
| Tasks | Task1:1 | 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
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
work4all
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Microsoft Dynamics 365 Sales .
Object compatibility
1 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 Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave work4all
Other ways to arrive at Microsoft Dynamics 365 Sales
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.