Troubleshooting the JTL migration

Here you find solutions for the most common stumbling blocks when migrating from JTL-Wawi.

#Connection

#jtl-bridge reports “Die Wawi-API … ist nicht erreichbar” (the Wawi API is not reachable)

jtl-bridge cannot reach the REST server. Check: Is the REST server running? Are the computer name, port and database name in the address correct (http://wawi-server:<port>/api/eazybusiness)? Does the Wawi computer's firewall allow the port on the internal network? Is jtl-bridge really running on the same network?

#“Die Wawi-API lehnt den API-Schlüssel ab” (the Wawi API rejects the API key)

The key was copied incorrectly or the app registration was removed in the Wawi. Run jtl-bridge register again, confirm in the Wawi and enter the new key in allverto. Details: Setting up the REST API.

#I can't find the app registration in the Wawi

According to our documentation, the menu item in Wawi 2.2 is called Admin → App-Registrierung (app registration). In other versions it may be named differently – search the admin menu for “App” or “API”. The request only appears after jtl-bridge register has sent it.

#“Nur HTTPS ist erlaubt” (only HTTPS is allowed)

For security reasons, jtl-bridge only uploads via https://. Check the allverto address in the command.

#“Fetch data directly” fails

This only works if your Wawi API is reachable from the internet – which is usually not the case (and doesn't need to be). Use jtl-bridge in the company network.

#Data and dry run

#The quantities under “Data found” don't match my Wawi

If you entered a changeover date, only documents up to that day are taken into account. With the API route, subscriptions and supplier invoices are missing if you started jtl-bridge without --fill-from-db.

#What do the results in the log mean?

For each record you see whether it was newly created, updated, skipped (unchanged or not supported) or rejected – with the reason. Filter by result and data type and download the log as CSV if needed.

#Why are some attributes “skipped”?

The Wawi API only delivers item attributes as an ID without a name. With --fill-from-db and a stored database, jtl-bridge adds the names.

#Will data be created twice if I migrate several times?

No. For every JTL record, allverto remembers what it became. Unchanged records are skipped, changed ones are updated.

#Why don't migrated invoices draw a new number?

Documents are taken over 1:1 with their original number from JTL. That's why you migrate the number ranges first – so numbering continues with the next free number after the migration.

#Completion

#Can I sync again after completing?

No. After Complete changeover, the import token is invalid and the staging area is deleted. So on the changeover date, first start a delta run and check the log.

#Are the logs kept?

Yes. Migrated data, mappings and logs are kept even after completion.