Migrate from JTL-Wawi to Microsoft Dynamics 365 Business Central

JTL-Wawi Artikels map to Dynamics 365 Items with an Item type distinction: Artikels with Lagerbestand (stock tracking) become Inventory Items, while non-stocked Artikels become Service Items or Products depending on the Business Central configuration. We export via JTL-Ameise Artikelstamm CSV, map cArtNr (SKU) to Dynamics 365 Item No., and preserve cross-references to Stammartikel (base items) and Variationskombinationen (variant combinations) as Dynamics 365 Product Variants with the appropriate product dimensions (Size, Color, or custom dimension sets).

JTL-Wawi variants stored as Variationskombinationen with dimension-specific Artikelnummern map to Dynamics 365 Product Variants linked to a base Product Master. The dimension values (Größe, Farbe, or custom) migrate as Product Dimension records. We preserve the JTL cross-reference field as a custom field on the Product Variant for audit.

JTL-Wawi Kunden map to Dynamics 365 Customer with the distinction between Debitor (customer account for AR) and Kunde split handled by the Customer Posting Group assignment. Address records (Lieferadresse, Rechnungsadresse) map to Customer Addresses with Address Type codes. We preserve payment status fields and map the German Anrede (Mr./Mrs./Company) to the Contact's salutation and gender fields.

JTL-Wawi Aufträge map to Microsoft Dynamics 365 Sales Order. The workflow state (Auftrag_erstellt, bezahlt, ausgeliefert) maps to Sales Order Status (Draft, Released, Shipped, Invoiced). Partial shipment handling is preserved as separate Sales Order Shipping Lines. We map the JTL order number to Dynamics 365 External Document No. and the customer-facing order reference to the Document No.

JTL-Wawi Rechnungen map to Microsoft Dynamics 365 Sales Invoice. Tax codes and regional VAT configurations require field-level mapping: the German MwSt (Umsatzsteuer) rate of 19% or 7% maps to the corresponding VAT Product Posting Group and VAT Business Posting Group combination. We export via the Rechnungen template and preserve line-item tax calculations against the original Auftrag where applicable.

JTL-Wawi Lagerbestände per Lager (warehouse) map to Dynamics 365 Item Ledger Entries with the appropriate Location Code. We capture aktuelle Bestände (current stock levels) and pending reservations as separate entries. The inventory posting group assignment determines the valuation method (FIFO, Standard, Average) in Dynamics 365. Multiple Lager require Location records created before inventory import.

JTL-Wawi Lieferanten map to Dynamics 365 Vendor with Vendor Posting Group assignment. Einkaufspreise (purchase prices) and Rahmenbestellungen (framework orders) migrate as Purchase Lines and Blanket Purchase Orders. We preserve the supplier's payment terms and map German bank details (IBAN, BIC) to the Vendor's bank information fields.

JTL-Wawi Zusatzkosten (transport, customs, duties on Lieferantenbestellung) map to Dynamics 365 Direct Costs or Indirect Costs depending on whether they are line-attributable or invoice-level. We preserve the named cost type definitions and map them to the corresponding Item Charge or Invoice Header Charge in Dynamics 365, which requires the Vendor Invoice to be posted before the cost allocation is applied.

JTL-Wawi shipping data per logistics partner (DPD, Hermes, iloxx) maps to Dynamics 365 Shipment Method codes. Tracking IDs from JTL-Wawi exports migrate to the Dynamics 365 Warehouse Shipment lines and are linked to the outbound Sales Order Shipment. We preserve the shipping method assignments and recommend creating Shipment Method records for each active carrier before migration.

JTL-Connector credentials for Shopware, PrestaShop, and marketplace APIs do not migrate. We document every active connector (shop URL, API key scope, synchronization frequency) in a Connector Audit document that the customer's IT team uses to re-establish connections in the destination system. New API credentials must be generated in each shop admin panel and entered into Dynamics 365 or the middleware (Shopify Connector, WooCommerce Connector) being used post-migration.

Custom SQL views built in JTL-Wawi 'Eigene Übersichten' are stored in the database and not exposed via API or standard export. We flag these during scoping and recommend documenting the view logic manually. The equivalent in Dynamics 365 is a custom report built in Report Designer or a Power BI dataset connecting to Dataverse. We provide a Custom View Audit document listing the view name, table references, filters, and a recommended Dynamics 365 equivalent.

JTL-Workflows define event-condition-action chains that cannot be imported into Power Automate or Dynamics 365 business events. We deliver a Workflow Audit Report listing every active workflow with its trigger (event type), conditions, actions, and recommended Power Automate equivalent. The customer's admin rebuilds workflows in Power Automate using the audit as a blueprint. This is outside the migration scope and is a separate rebuild engagement.