Migrating from JTL-Wawi: how it works

You currently work with JTL-Wawi and want to switch to allverto? The migration wizard takes over your data completely – with the original numbers of your documents, so that invoices, customer numbers and item numbers continue exactly as before. Until the changeover date you keep working in JTL as usual.

#Before you start

• In allverto you need the permission Carry out migration from JTL-Wawi (take over data). Owners and the Administration role have it.
• You find the wizard under Settings → Data migration → Migration from JTL-Wawi.
• allverto is built for JTL-Wawi 2.1 and 2.2. Older versions (1.5 to 2.0) can usually be read via the database but are not tested – in that case, talk to us beforehand.
• Plan a changeover date (e.g. a Monday). Until then you can do as many trial runs as you like.

#Two routes to your data

allverto can read the data via two equivalent routes. You choose the route in the first step of the wizard.

What the API doesn't deliver (e.g. subscriptions and supplier invoices), jtl-bridge can add from the database if you want. The wizard shows a What does each route provide? table right next to the source. In detail: Setting up the JTL-Wawi REST API and Access via the JTL database.

#Step by step

1. Connect source: choose JTL-Wawi API or JTL database, enter the connection details and click Save source. Optionally set a changeover date – then only documents up to that day are migrated. In a test company you can try out the whole process with Test data (without JTL) and Load test data without connecting a Wawi. In the same step you upload the data: on the right under jtl-bridge helper, generate an import token and start jtl-bridge on a computer in the company network with the command shown. If your Wawi API is reachable from the internet, you can use Fetch data directly instead.
2. Data found: check the quantities per data type – do the item, customer and document counts roughly match your Wawi?
3. Mappings: define where number ranges, tax rates, payment and shipping methods, warehouses, customer groups and platforms go in allverto. Number ranges first – so allverto continues counting seamlessly after the migration.
4. Dry run & migration: start a Dry run (without writing). It calculates everything completely once and writes nothing. When the log is clean, migrate the data in a fixed order: number ranges → master data → customers → stock → documents.
5. Log: for each record you see whether it was newly created, updated, skipped or rejected – filterable and as CSV.
6. Complete changeover: on the changeover date you upload once more and start a delta run. Then click Complete changeover.

#What is migrated?

• Number ranges with prefix, suffix and next number.
• Master data: company data, taxes, payment and shipping methods, customer groups, warehouses, categories, manufacturers, characteristics, attributes, custom fields, suppliers, items with variants, translations, bills of materials, prices, special prices and images.
• Customers with original customer number, addresses, contacts, terms and bank accounts.
• Stock as opening stock per storage bin (posting “Übernahme” (migration) in the stock journal). If you map a JTL warehouse to a Default warehouse (without storage bins), allverto merges its JTL storage bins – storage bins are only created individually in WMS warehouses.
• Documents 1:1: quotes, sales orders, delivery notes, invoices, invoice corrections, payments, dunning levels, purchase orders, returns – with original number and date. Migrated documents are finalised and do not draw a new number from your number ranges.

#The changeover date

1. Stop creating new documents in JTL.
2. Upload one last time with jtl-bridge (or Fetch data directly).
3. Start delta run and check the log.
4. Complete changeover: the import token becomes invalid and the cached JTL data is deleted. Migrated data, mappings and logs are kept.

From now on, allverto is your leading system. Next, connect your shops and marketplaces. If something doesn't work, see Troubleshooting the JTL migration.