Solution · SAP ↔ Microsoft Dynamics
Between SAP and Business Central, in either direction.
The same eight steps of vise DMW, with the target structure of Navision / Business Central — or of S/4HANA when the move goes the other way. Scattered customer records become golden records; production BOMs are transformed, not retyped.
01 · The problem
Why this move is a data project, not an export.
Business Central is deliberately simpler than SAP. The data still has to arrive complete, consistent and in the target’s structure — and it has to arrive four times.
- 01 Customers scattered and duplicated Records spread across several systems and duplicated within one — often differing by a space or a comma. A copy carries every duplicate into the new ERP.
- 02 Roles become structures SAP customer roles such as payer and ship-to party have no 1:1 counterpart in Navision / Business Central. The right target structure depends on the value of specific fields — transformation, not mapping.
- 03 BOMs carry the logic Production bills of materials hold the most structure and business logic in SAP, and the most risk in either direction.
- 04 Four environments, no spare people DEV, QA, UAT and PROD each need a full delivery. The team knows its data but has neither the capacity nor the tooling to redo the work four times.
02 · The approach
The same discipline, whichever way the data moves.
Five moves, run in vise DMW, repeated on demand for every environment and company. The direction changes the target structure, not the method.
- 01 Workshops on both sides With the implementation partner on the target’s technical requirements and field mappings; with your team on business rules, cleansing criteria, deduplication logic and validation.
- 02 Extract and consolidate Automated retrieval from every source system — several SAP systems in the Karlsberg case — into one working set in vise DMW.
- 03 Cleanse to golden records Format-standardisation rules and matching that catches duplicates despite notation differences. One golden record per customer, with the merge decision recorded.
- 04 Transform by rule Rules keyed on the fields that decide the target structure — how roles and attributes are created in Business Central, or how material master fields resolve in S/4HANA. Previewed before anything is delivered.
- 05 Deliver on demand Once defined, the same run produces the files for every test cycle, environment and company. Your partner loads them into Business Central; into S/4HANA, vise DMW loads through standard interfaces.
Going the other way? Dynamics NAV / BC → S/4HANA, step by step → · Field mapping with AI drafts and human approval: vise FieldMap →
03 · The result
What it looked like at Karlsberg.
Scattered, duplicated customer records and complex production BOMs were cleansed, deduplicated into golden records and transformed to the Navision structure. Rules built for the first German entity were reused for the French one.
- 5 → 1
- FTE-equivalent of work handled by one Visehub specialist
- 1.5 yrs
- iterative deliveries across DEV, QA, UAT and PROD
- 2 objects
- customer master and bills of materials
- DE → FR
- rules reused across entities
“A simple briefing combined with a deadline was enough to receive a high-quality result on time.”
Material master mapped from Business Central to SAP S/4HANA with vise FieldMap: the AI drafts field pairs and transformation rules, the consultant approves every line in a target-driven view. First production use of FieldMap.
vise FieldMap04 · FAQ
The questions we get on this move.
- 01Does vise DMW load into Business Central directly?
- For the SAP → Navision / Business Central direction we deliver load-ready, validated files in the target structure; the implementation partner loads them with their tooling, as at Karlsberg. For the Business Central → S/4HANA direction vise DMW loads through standard SAP interfaces (BAPI, IDoc, OData) or feeds Migration Cockpit — never a direct database write.
- 02Which objects does this cover?
- Customer master and bills of materials in the SAP → Navision move; material master in the Business Central → S/4HANA move, mapped with vise FieldMap. Vendor master and other master-data objects follow the same eight steps.
- 03Can rules built for one company be reused for the next?
- Yes. At Karlsberg the cleansing and transformation rules built for the German entity were reused for the French one. Rules, mappings and dictionaries are versioned, so the second company starts from the first one’s work.
- 04What does the team on our side have to do?
- Attend the workshops, decide the business rules and sign off per object. The extraction, cleansing, transformation and repeat deliveries are run by a Visehub specialist — one person covered the work of about five in the Karlsberg project.
- 05How do we start?
- A 30-day proof of concept on one object — customer master is the usual pick for this move. You get the cleansed, mapped, simulated result and an effort estimate for the rest.
One object, 30 days, your data.
Customer master is the usual start for an SAP ↔ Business Central move. You get the cleansed, mapped, simulated result and an estimate for the rest.