Migrate from JTL-Wawi to Infor CloudSuite Corporate

JTL-Wawi Artikels map to Infor CloudSuite Item Master records. The Artikelnummer becomes Part Number; the Artikelbeschreibung maps to Description. Variationskombinationen (variant combinations) require a 1:N split: the base Stammartikel maps to the Infor item, and each Variationskombination becomes a separate item record with variant-specific attributes linked via MITMAS-MITCTL relationships. Custom fields (Eigene Felder) on Artikeln migrate to Mongoose custom fields or extended data structures depending on whether the customer uses the Mongoose Framework. We resolve cross-references to Stammartikel at migration time using the Artikelnummer as the dedupe key.

JTL-Wawi Kunden map to Infor CloudSuite Customer records. The Kundengruppe (customer group) maps to a Customer Type or Territory code in Infor. Address records (Rechnungsadresse, Lieferadresse) become separate address roles in OCUSMA. Payment terms from JTL (Zahlungsziel) map to Infor's payment term codes. We preserve any custom fields on Kunden in Mongoose-extended fields. Customer merge or duplicate handling requires a reconciliation step before import because Infor enforces referential integrity on customer codes.

JTL-Wawi Aufträge map to Infor CloudSuite Sales Order header and line records. The Auftrag_erstellt, bezahlt, ausgeliefert workflow states map to Infor's order status codes. We preserve the full order lifecycle including partial shipments by mapping each JTL shipping event to an Infor shipment record. Aufträge reference Kunden (customer) and Artikeln (items); both must be loaded first so that customer and item codes are valid at insert time. Infor requires order dates and requested dates to be sequenced within the order lifecycle.

JTL-Wawi Rechnungen map to Infor CloudSuite Accounts Receivable invoice records. Tax codes from the Rechnungen export require mapping to Infor's tax jurisdiction codes, which are region-specific and must be entered manually or mapped from regional VAT configurations during scoping. We preserve line-item tax calculations from JTL as Infor tax amount fields on each invoice line. Rechnungen that reference Aufträge require the parent order to exist before invoice import.

JTL-Wawi Lagerbestände map to Infor CloudSuite inventory records per Lager (warehouse). Aktuelle Bestände (current stock levels) and pending reservations migrate as on-hand quantity and allocated quantity respectively. We capture the exact inventory snapshot at migration cutover time and load it into Infor's warehouse site records. Multi-Lager configurations in JTL map to separate Infor warehouse sites with inter-warehouse transfer records if stock needs redistribution.

JTL-Wawi Lieferanten map to Infor CloudSuite Supplier records. Einkaufspreise (purchase prices) migrate to Infor's supplier price lists if the destination uses standard costing or to purchase order line defaults if using average cost. Rahmenbestellungen (framework orders) require mapping to Infor's Blanket Purchase Agreement records if the destination uses them. Supplier address and contact fields map to Infor vendor address roles.

JTL-Wawi Zusatzkosten (transport, customs, duties) attached to Lieferantenbestellungen map to Infor CloudSuite landed cost or additional charge categories. These are cost types defined per supplier order and must be mapped to Infor's cost category codes during scoping. Infor's landed cost model may require additional configuration if the customer's business relies heavily on duty and freight cost tracking.

JTL-Workflows define event-condition-action chains tied to JTL-Wawi's event-driven automation engine. These do not migrate to Infor CloudSuite because Infor has a different automation model. We document all active JTL-Workflows during scoping with their trigger events, conditions, and actions, and deliver a written audit report for the customer's Infor administrator to rebuild using Infor Process Automation or ION workflows post-migration.

JTL-Connector credentials that synchronize Artikels and Aufträge between JTL-Wawi and storefronts do not migrate because they are JTL-platform-specific. We deliver a connector audit document listing all active storefront connections, the data flows they manage, and recommended approaches for re-establishing integration in Infor CloudSuite (typically via Infor ION or API-based connectors from the storefronts).

JTL-WMS extends JTL-Wawi with pick-and-pack workflows and pack-station configuration. WMS-specific data (Arbeitsstationen, Packtisch-Konfiguration) is not exposed via JTL's REST API and is not part of the standard JTL-Ameise export templates. We handle WMS data via JTL-Ameise where supported and flag any WMS configuration that requires manual documentation. Infor's warehouse management capabilities are covered by CloudSuite WMS if the customer licenses that module.