Migrate your JTL-Wawi data
German e-commerce ERP built around merchandise management and multi-channel selling. JTL-Wawi orchestrates inventory, orders, and fulfillment for SMB retailers across marketplaces, shops, and warehouses.
In its favor
Why people choose JTL-Wawi
The signal that keeps JTL-Wawi on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Extensive German-language knowledge base and community forum with 72,000 posts means teams can self-solve common configuration problems quickly.
Integrated ecosystem (JTL-Wawi, JTL-Shop, JTL-eazyAuction) unifies item management, order processing, and marketplace selling across eBay and Amazon without third-party middleware.
JTL-Workflows automate repetitive business logic using event-driven triggers, reducing manual intervention in daily order and shipping operations.
Free and Basic support tiers lower the entry cost for small e-commerce teams evaluating the platform before committing to a paid tier.
Direct RDP hosting via JTL Cloud or third-party providers allows teams to run JTL-Wawi without maintaining on-premises Windows infrastructure.
Support costs escalate significantly when issues require Bronze or Silver tier assistance, and the tariff model means simple questions can become billable support tickets.
English documentation remains incomplete with many pages still showing German screenshots and links, creating friction for non-German-speaking administrators.
Cloud hosting was discontinued by JTL, forcing customers to either self-host on-premises or find third-party RDP providers, disrupting existing deployment patterns.
Customer satisfaction scores are modest (G2 3.8, Trustpilot 2.4) with reviewers citing feature gaps and support responsiveness as recurring frustrations.
Reasons to switch
Why people leave JTL-Wawi
The recurring reasons buyers give for replacing JTL-Wawi. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where JTL-Wawi fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
JTL-Wawi pricing overview
JTL-Wawi itself has no publicly published per-seat or per-tier pricing. Support is organized into Free and Basic (no cost) tiers plus paid Bronze and Silver tiers. Most direct costs come from JTL-Connector add-ons, JTL-Shop licensing, and third-party hosting fees for RDP deployments.
Free
Tier 1 of 4
Free
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on JTL-Wawi's schedule — see our quote-based pricing →
What gets migrated
JTL-Wawi object support
Object-by-object support for JTL-Wawi migrations. Per-pair details surface during scoping.
Artikels (Items/Products)
Fully supportedItems are the core JTL-Wawi object with a well-documented schema. We export Artikels via JTL-Ameise CSV or REST API, preserving cross-references to Stammartikel (base items) and Variationskombinationen (variant combinations). Custom fields are supported via the dedicated customfields endpoint.
Kunden (Customers)
Fully supportedCustomer export is a standard JTL-Ameise template. We map Kunden to the destination's contact model, preserving address records and payment status fields. Merged or duplicate customer handling is configurable per migration scope.
Aufträge (Sales Orders)
Fully supportedOrders link Artikels to Kunden and carry workflow state (Auftrag_erstellt, bezahlt, ausgeliefert). We preserve the full order lifecycle including partial shipments and order modifications during migration.
Rechnungen (Invoices)
Mapping requiredInvoices reference Aufträge and contain line-item tax calculations. We export via the Rechnungen export template. Tax codes and regional VAT configurations may require field-level mapping when migrating to non-German ERPs.
Lagerbestände (Inventory/Warehouse Stock)
Fully supportedStock levels are maintained per Lager (warehouse) and can be exported as CSV. We capture aktuelle Bestände and pending reservations to reconstruct the exact inventory snapshot at migration cutover time.
Lieferanten (Suppliers/Vendors)
Mapping requiredSupplier records link to purchasing workflows. Name and address export is straightforward; Einkaufspreise (purchase prices) and Rahmenbestellungen require value mapping if the destination uses different currency or UOM conventions.
JTL-Workflows (Automated Workflows)
Mapping requiredWorkflows define event-condition-action chains. We document all active workflows during scoping. Migration requires recreating them in the destination system; we provide a workflow audit report as part of every JTL-Wawi migration package.
Zusatzkosten (Additional Costs on A/P Invoices)
Mapping requiredAdditional costs such as transport, customs, and duties are defined as named cost types per Lieferantenbestellung. We preserve these definitions and map them to equivalent cost categories in the destination ERP.
JTL-Connector Links (Shopware, PrestaShop, etc.)
Mapping requiredConnectors synchronize Artikels and Aufträge between JTL-Wawi and storefronts. Migration requires re-establishing connector credentials in the destination system. We provide a connector audit documenting all active channel links before cutover.
Versand (Shipping/Package Export)
Mapping requiredShipping data is exported as CSV per logistics partner (DPD, Hermes, iloxx). Tracking IDs can be fed back via import template. We preserve the shipping method assignments and export templates during migration.
JTL-WMS (Warehouse Management)
Mapping requiredJTL-WMS extends JTL-Wawi with pick-and-pack workflows. WMS-specific data (Arbeitsstationen, Packtisch-Konfiguration) is not part of the core REST API; we handle it via JTL-Ameise exports where supported.
Benutzerdefinierte Ansichten (Custom SQL Views)
Not in this platformCustom SQL views built by users in '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 or SQL-level export as a fallback.
| Object | Support | Notes |
|---|---|---|
| Artikels (Items/Products) | Fully supported | Items are the core JTL-Wawi object with a well-documented schema. We export Artikels via JTL-Ameise CSV or REST API, preserving cross-references to Stammartikel (base items) and Variationskombinationen (variant combinations). Custom fields are supported via the dedicated customfields endpoint. |
| Kunden (Customers) | Fully supported | Customer export is a standard JTL-Ameise template. We map Kunden to the destination's contact model, preserving address records and payment status fields. Merged or duplicate customer handling is configurable per migration scope. |
| Aufträge (Sales Orders) | Fully supported | Orders link Artikels to Kunden and carry workflow state (Auftrag_erstellt, bezahlt, ausgeliefert). We preserve the full order lifecycle including partial shipments and order modifications during migration. |
| Rechnungen (Invoices) | Mapping required | Invoices reference Aufträge and contain line-item tax calculations. We export via the Rechnungen export template. Tax codes and regional VAT configurations may require field-level mapping when migrating to non-German ERPs. |
| Lagerbestände (Inventory/Warehouse Stock) | Fully supported | Stock levels are maintained per Lager (warehouse) and can be exported as CSV. We capture aktuelle Bestände and pending reservations to reconstruct the exact inventory snapshot at migration cutover time. |
| Lieferanten (Suppliers/Vendors) | Mapping required | Supplier records link to purchasing workflows. Name and address export is straightforward; Einkaufspreise (purchase prices) and Rahmenbestellungen require value mapping if the destination uses different currency or UOM conventions. |
| JTL-Workflows (Automated Workflows) | Mapping required | Workflows define event-condition-action chains. We document all active workflows during scoping. Migration requires recreating them in the destination system; we provide a workflow audit report as part of every JTL-Wawi migration package. |
| Zusatzkosten (Additional Costs on A/P Invoices) | Mapping required | Additional costs such as transport, customs, and duties are defined as named cost types per Lieferantenbestellung. We preserve these definitions and map them to equivalent cost categories in the destination ERP. |
| JTL-Connector Links (Shopware, PrestaShop, etc.) | Mapping required | Connectors synchronize Artikels and Aufträge between JTL-Wawi and storefronts. Migration requires re-establishing connector credentials in the destination system. We provide a connector audit documenting all active channel links before cutover. |
| Versand (Shipping/Package Export) | Mapping required | Shipping data is exported as CSV per logistics partner (DPD, Hermes, iloxx). Tracking IDs can be fed back via import template. We preserve the shipping method assignments and export templates during migration. |
| JTL-WMS (Warehouse Management) | Mapping required | JTL-WMS extends JTL-Wawi with pick-and-pack workflows. WMS-specific data (Arbeitsstationen, Packtisch-Konfiguration) is not part of the core REST API; we handle it via JTL-Ameise exports where supported. |
| Benutzerdefinierte Ansichten (Custom SQL Views) | Not in this platform | Custom SQL views built by users in '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 or SQL-level export as a fallback. |
Gotchas
What to watch for in JTL-Wawi migrations
Issues we've hit on past JTL-Wawi migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
SCX API per-endpoint rate limits return HTTP 429
UNC paths required for all file-based imports and exports
JTL Cloud hosting discontinued forces third-party RDP reliance
Incomplete English documentation with untranslated content
| Severity | Issue |
|---|---|
| Medium | SCX API per-endpoint rate limits return HTTP 429 |
| High | UNC paths required for all file-based imports and exports |
| High | JTL Cloud hosting discontinued forces third-party RDP reliance |
| Low | Incomplete English documentation with untranslated content |
Leaving JTL-Wawi?
Where JTL-Wawi customers move next
6 destinations JTL-Wawi can migrate to.
How a JTL-Wawi migration works
Four steps, JTL-Wawi-specific
Connect
API key (SCX APIs and REST API) into JTL-Wawi. Scopes limited to read-only on the data we move.
Map
We translate JTL-Wawi-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate JTL-Wawi quirks before production.
Migrate
Full migration with JTL-Wawi rate-limit handling. Rollback available throughout.
FAQ
JTL-Wawi migration FAQ
Answers to the questions buyers ask most during JTL-Wawi migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your JTL-Wawi migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate JTL-Wawi.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your JTL-Wawi setup and destination — written quote back within a business day.