LIFERAY MIGRATION · SILVER PARTNER

From any 6.x or 7.x version to 2026.Q1 LTS.

Portalworks migrates Liferay portals from 6.1, 6.2 and all 7.x versions to Liferay DXP 2026.Q1 LTS, as well as from Community Edition to DXP. It starts with an assessment that gives you a reliable effort estimate. Content, users and URLs are carried over.

Schedule an initial call → View migration projects
LIFERAY SILVER PARTNER
Official Liferay Silver Partner
Partner of Liferay Inc. for the development, migration and operation of Liferay DXP.
We have been working with Liferay since 2008: more than 50 portal projects, from version 6.1 to 2026.Q3.
STARTING VERSIONS

What needs to be done, depending on your starting version

View migration projects →
6.1 · 6.2
Plugins SDK, portlets built the old way. Usually a rebuild of the business logic rather than a port.
7.0 – 7.3
OSGi modules already in place. Upgrade via 7.4, modules are brought up to date.
7.4
The core task is the Jakarta EE conversion of custom code. Liferay’s scripts automate roughly half of it.
2026.Q1 LTS
Three years of premium support, new CMS, MCP server. The current target for migrations.
Since 2026.Q1, only a license key separates free use from commercial use. The license question is independent of the upgrade and can be settled at any time.
PROCESS

Five steps to go-live

Every migration runs on a test environment first. You see the result before the production portal is switched over.

01
Assessment
Version, custom development, integrations, database and operations. Result: effort in person-days, risks, recommended approach.
02
Test migration
Upgrade of a copy of the database and documents on a separate environment.
03
Code and data
Modules, themes and fragments brought to the new version, Jakarta EE in custom code, replaced by standard features where possible.
04
Testing
Functions, interfaces, permissions and URLs. Existing URLs remain reachable or are redirected.
05
Go-live and aftercare
Switchover in the agreed maintenance window, followed by support in operation.
MIGRATION PROJECTS

Migrations from our projects

Lufthansa Technik

Migration of an intranet that has grown over many years from Liferay 6.2 to Liferay DXP 2026.Q3, with a redesign, login via Keycloak and operation on OpenShift.
SINCE 2024 · 6.2 → 2026.Q3 · KEYCLOAK · OPENSHIFT

PME Familienservice GmbH

Migration of familienservice.de from Liferay 7.3 via 7.4 to Liferay DXP 2026.Q3, with a database move, new reporting and a custom theme.
2024–2026 · 7.3 → 2026.Q3 · MYSQL → POSTGRESQL

Industry association

Portal with its own taxonomy platform, currently on Liferay DXP 2025.Q1. The AI features from 2026.Q3 are being integrated.
SINCE 2014 · 2025.Q1 → 2026.Q3

Car manufacturer

Building a group-wide portal system and migrating existing portals to a shared Liferay base.
2017–2020 · 6.1 → 7
All references →
FREQUENTLY ASKED QUESTIONS

Liferay migration

Which versions does Portalworks migrate to Liferay DXP 2026.Q1?

From Liferay 6.1, 6.2, 7.0, 7.1, 7.2, 7.3 and 7.4 to the current DXP versions. Also the switch from Community Edition to DXP and migrations from other systems such as TYPO3, WordPress or Adobe Experience Manager.

How does a Liferay migration with Portalworks work?

It starts with an assessment of the existing portal: Liferay version, custom modules, integrations, data volume and operating environment. This is followed by migration on a test environment, testing of content and interfaces, and the planned go-live.

What does Jakarta EE change for custom Liferay modules?

With Liferay DXP 2026.Q1 the platform moves from Java EE to Jakarta EE. All imports of javax.servlet and related packages are switched to jakarta.servlet. The step is mechanical, but it affects every custom module.

Can we switch from Liferay CE to DXP?

Yes. Liferay has discontinued the Community Edition; since 2026.Q1, only a license key separates free use from commercial use. Technically, the switch is a version upgrade.

How long does a Liferay migration take?

It depends on the version gap and the amount of custom development. Jumps within the 7.x line are completed much faster than a migration from 6.2, where portlets and themes also need to be modernized. We give you a reliable schedule after the assessment.

Can we keep working during the migration?

Yes. The migration runs on a separate environment, the production portal remains untouched. For the switchover we agree on a maintenance window and a short content freeze.

Which version is your portal running on?

Initial call with Marc Hermann. We get back to you within 24 hours with a first assessment.

Schedule a call →