Licensed commands failing after moving to Liquibase 5.x

Applies to

Liquibase Secure (Pro)

Conditions

Upgrading or installing Liquibase 5.x

Issue Summary

After upgrading from Liquibase 4.x to 5.x, you may encounter errors related to licensed features:

Licensed commands such as `flow` return an error indicating that a valid Liquibase license key is required.
An upgrade appears to install successfully, but previously working Secure/Pro functionality is no longer available.

These symptoms often occur when an existing upgrade process assumes the same packaging and distribution model as Liquibase 4.x.

Error Message

Error parsing command line: Using '<command>' requires a valid Liquibase license key. Get a free Liquibase license key and trial at https://liquibase.com/trial.

Root Cause

Liquibase 5.0 introduced changes to how Liquibase is packaged and distributed.

As a result:

The installation layout is different from earlier 4.x releases.
Files that may have existed in previous installations, such as `liquibase-core.jar` in an expected folder, may no longer be present in the same way.
Secure (formerly Pro) functionality depends on using the correct 5.x distribution.
Automation that depends on the old directory structure or directly references internal JAR files may break after upgrade.

If the OSS package is installed instead of the Secure package, commands that require a license can fail with license-related errors even if they worked previously in 4.x.

Resolution

To resolve these upgrade issues:

Confirm which Liquibase 5.x distribution was installed
- If you use licensed features, make sure you have installed the Liquibase Secure distribution rather than an OSS distribution.
- Check the guidance in New Distribution Channels for Liquibase Secure 5.0 and verify that your installation method matches the intended Secure deployment model.
Update automation and scripts
- If your scripts reference `liquibase-core.jar` directly or expect the 4.x installation structure, update them.
- Recommended: Use the provided Liquibase executable/CLI rather than relying on internal JAR paths from older versions.

Summary

If Liquibase 5.x behaves differently after upgrading, first verify that you are using the correct distribution and not relying on the old 4.x file layout. Most 5.x upgrade issues are caused by packaging and distribution changes introduced in Liquibase 5.0.