One-click migration from older systems

Switch to the platform before updating to 26.x

Access to the Update center

• Older 4.6 systems may require activation to access updates. Contact your Lobster representative if the update does not appear in the Update center.

• The legacy portal.lobster.de was shut down on December 31, 2025, and completely replaced by the Update center. There, you can select and download the required Lobster version with the current updates for all supported versions.

Before migration

• Confirm you are running 4.6.14 or later before you can migrate to 25.1.x.

• Work through the entire "Pre-upgrade checklist" (see Before starting an upgrade), including backing up the SAP libraries.

• Merge the _data and pro installations, if both exist. Once the data installation has been migrated, the _pro installation can no longer be imported into the platform.

• If you want to switch database systems (e.g., from MS SQL Server or MySQL to PostgreSQL), perform the switch before migrating to Lobster Data Platform. After migration, a complete switch of the database system is no longer supported. See also Data migration.

• Following the migration to the Lobster Data Platform, _data HA customers will need to share an additional folder in the shared file system: ./PRO/config/files 

• Review whether you have received a renewed dedicated DMZ license, if you have a DMZ.

After migrating to 25.1.x

Clear browser cache

Clear your browser cache before logging in. The initial login after the migration to Lobster Data 25.1 may take a moment.

Database re-encoding

MySQL tables are automatically converted to utf8mb4 during migration. Log messages regarding tables that cannot be migrated due to mixed sorting rules are not uncommon and can be ignored.

Verify start scripts

The updater automatically adjusts the references to classes in the startup scripts. Check if this change has been made:

Previously

• com.ebd.hub.update.UpdateInstaller

Now

• de.lobster.updater.LobsterInstaller

hub.bat (Windows)

If the file looks exactly like this, proceed.

set UPDATE="%JAVA_HOME%\bin\java" -cp bin/updater.jar -Djava.io.tmpdir="%HUB_HOME%\tmpIO" de.lobster.updater.LobsterInstaller

execute.sh (Linux)

If the file looks exactly like this, proceed.

$JAVA -cp bin/updater.jar -Djava.io.tmpdir=$HUB_HOME/tmpIO de.lobster.updater.LobsterInstaller $HUB_HOME

If you see different content in these files and are uncertain about how to fix the file, contact  support for clarification.

Cross-platform migration

If you would like to migrate your installation to a different platform (for example, from Windows to Linux), please contact Support.

Platform GUI configuration

Starting with version 25.1.x, the user interface requires a reference to the HTTP server in order to deploy the web application. Older 4.x data installations with a pro installation do not include this setting. Without it, the user interface will be inaccessible after migration.

Check PRO/config/etc/systemManagers/de.lobster.scm.rest.WebAppManager.xml , to verify that the httpServerName property is present: <Set name="httpServerName">Main Server</Set> .

If this line is missing, add it and restart the service.

Migration of HA Systems from _data to the Lobster Data Platform

The transition from 4.6.x to the Lobster Data Platform requires a full cluster shutdown. This one-click migration automatically migrates the database to support new platform capabilities; however, the entire cluster must remain offline during this process.

Wait until the Node Controller has fully started up and completed its migrations before you begin updating the worker nodes and DMZs. Once the migration is complete, the standard rolling update process applies to future maintenance tasks.

Migration order:

1. Stop all systems.

2. Migrate and restart NodeController and Primary DMZ.

3. Migrate and restart working nodes and Secondary DMZ systems.

Validation

After the migration, perform the following validation checks:

• The platform must start without errors. Check the service logs for errors or stack traces.

  • Windows: ./logs/wrapper.log

  • Linux: ./logs/console.txt

• Test connectivity: Partner channels and communication protocols in use (SFTP, OFTP, AS2, SMB, databases, etc.).

• Test profiles: Run existing test case profiles that cover key functions. Consider using the Profile test manager for a structured validation.

• Review the latest error.log files for anomalies compared to the pre-migration state.

Next step

Do not upgrade to 26.x until 25.1.x is up and running and has been fully validated.

SAP libraries

SAP libraries are no longer distributed with new releases due to licensing restrictions. If your system uses SAP connectivity, manually back up the following files before migration and restore them afterward.

Legacy layouts (existing installations before migration)

For older hubs, both JCo 3 and (optionally) the old RFC library might be present. Use this table for legacy 4.x systems that already have SAP configured in the classic locations:

Troubleshooting the Upgrade from 4.x to 25.1.x

Rollback