Migrate from JTL-Wawi to Dolibarr ERP

JTL-Wawi Artikels map to Dolibarr Product records with type set to Product (not Service). The JTLArtikel.cArtNr (article number) maps to Product.ref; Artikelname maps to Product.label; Grundpreis (base price) maps to Product.price. Variationskombinatione (variant combinations) are decomposed into separate Product records or handled via Dolibarr's optional Variants module if the customer activates it. JTL custom fields (Eigene Felder) migrate to Dolibarr ExtraFields on Product. We export via JTL-Ameise Artikelstamm CSV template and import via Dolibarr's Products import tool or REST API.

JTL-Wawi Kunden map to Dolibarr ThirdParty records with Type = Customer. The Kunden.kndNr (customer number) maps to ThirdParty.code; Name maps to ThirdParty.name; address fields map to standard address fields. Payment terms and customer-specific pricing from JTL map to Dolibarr's payment term and price level ExtraFields. Kunden with Lieferantenstatus = true also generate a corresponding Supplier ThirdParty if the customer uses Dolibarr's dual-role ThirdParty model. We export via JTL-Ameise Kunden export and import via Dolibarr's ThirdParty CSV import or API.

JTL-Wawi Lieferanten map to Dolibarr ThirdParty records with Type = Supplier. The Lieferanten.lfrNr maps to ThirdParty.code; Lieferantenname maps to ThirdParty.name. Einkaufspreise (purchase prices) from JTL map to Dolibarr Product Supplier Ref/Price entries via the Product-Linked Suppliers table. Rahmenbestellungen (framework purchase orders) do not have a direct Dolibarr equivalent and are documented as open PO records requiring manual re-entry in Dolibarr if they remain active at cutover.

JTL-Wawi Aufträge map to Dolibarr Order records. The Auftrag.angNr (order number) maps to Order.ref; Auftrag_erstellt/bezahlt/ausgeliefert status maps to Dolibarr status values (Draft, Validated, Shipped, Closed). Order date and delivery date migrate. Line items reference Artikels via Product ref lookup. Partial shipment handling is preserved through multiple Order line items or by splitting into separate Dolibarr shipments. We export via JTL-Ameise Aufträge export template and import via Dolibarr Orders import.

JTL-Wawi Rechnungen map to Dolibarr Invoice records with type = Customer Invoice. Rechnungsnummer maps to Invoice.ref; invoice date and due date migrate. Line items carry tax calculations from JTL; tax codes map to Dolibarr VAT rate ExtraFields. Regional VAT configurations (19% Germany, 20% Austria, etc.) require field-level mapping during transform. JTL's Rechnungen export template does not include archived PDF content; we flag that invoice PDFs must be exported separately from JTL's document archive and re-imported into Dolibarr's document management.

JTL-Wawi Lagerbestände map to Dolibarr Stock (Warehouse) records. Aktuelle Bestände (current stock) per Lager (warehouse) map to Dolibarr stock_warehouse_product entries. Pending reservations migrate as open stock movement records if the customer activates Dolibarr's Stock module. Dolibarr warehouse locations map to JTL Lager locations. If the customer uses multiple Lager in JTL, we configure corresponding warehouses in Dolibarr before stock import. Stock snapshot is taken at migration cutover time to avoid mid-migration discrepancies.

JTL-Wawi Versand data (DPD, Hermes, iloxx exports) maps to Dolibarr Shipment records if the customer activates Dolibarr's Expedition (Shipment) module. Tracking IDs are stored in Dolibarr's shipment tracking field. Note: Dolibarr has no native carrier-specific label printing; DPD/Hermes/iloxx integrations require re-establishment post-migration via Dolibarr's carrier module configuration or third-party shipping modules. We export JTL shipping export templates and import tracking IDs into Dolibarr Shipment records but do not rebuild carrier API credentials.

JTL-Wawi Zusatzkosten (transport, customs, duties on Lieferantenbestellungen) are named cost types per purchase order. Dolibarr has no native Zusatzkosten equivalent; we map these to ExtraFields on Supplier Invoice (lignes_facture_fournisseur) with cost type categories (Transport, Customs, Duties) defined during schema setup. The customer's admin assigns cost type values post-migration.

JTL-Workflows define event-condition-action chains (e.g., Auftrag created -> send email -> update status). Dolibarr core has no native workflow automation engine. We document all active JTL-Workflows during scoping with their triggers, conditions, and actions, and deliver a written workflow audit report for the customer's admin to evaluate third-party Dolibarr workflow modules (e.g., module_workflowmanagers or custom PHP development). Workflows do not migrate as code.

JTL-Connector links between JTL-Wawi and Shopware, PrestaShop, or WooCommerce synchronize Artikels and Aufträge in real time. Dolibarr has no JTL-Connector equivalent and no native Shopware or PrestaShop integration in core. We deliver a connector audit document listing all active storefront connections, their sync scope (items, orders, customers), and recommended Dolibarr alternatives (Dolibarr's WooCommerce module, custom API integration, or a middleware like Celigo). The customer reconnects storefronts post-migration with our documented specification.

JTL-WMS Arbeitsstationen (workstations) and Packtisch-Konfiguration (packing table settings) are JTL-WMS-specific and not exposed via JTL-Wawi REST API or JTL-Ameise exports. We extract what is available via JTL-Ameise exports (stock levels, pending shipments) and document the JTL-WMS configuration in a separate WMS audit report. Pick-and-pack workflows, pack station assignments, and worker management settings cannot be migrated and require manual rebuild in the destination WMS or Dolibarr's optional warehouse module.

Custom SQL views in JTL-Wawi 'Eigene Übersichten' are stored in the JTL-Wawi database and are not exposed via API or standard export. We flag these during scoping and recommend manual documentation by the customer's database administrator. These views reference JTL-specific table structures that will not exist in Dolibarr and require complete rewrite against Dolibarr's llx_* table schema.