Your Liferay is out of support. We take it to a version that is not.
Who it is for
For companies and public bodies with a portal or an intranet on a Liferay version that no longer receives patches. Also for anyone several versions behind who does not know where to start.
The problem
The portal works, but the version is out of support. Security patches no longer arrive. The custom code was written by a supplier who is gone, and nobody knows what breaks if you upgrade. Every year that passes, the jump gets bigger and scarier.
How we solve it
Before touching production, we rehearse the migration with a copy of your data. That way you know what breaks and how much work there is before you decide. Then we adapt the custom code, migrate the content and go live with a rollback ready. The portal ends up on a supported version and in shape to keep upgrading.
What it includes
Inventory of what is there
Version, custom code, integrations, content and data. What is used and what can be retired.
Migration rehearsal
A trial upgrade with a copy of your data, to anticipate the problems before the real migration.
Custom code adapted
Modules, themes and integrations brought to the new version. What the platform now ships out of the box stops being custom.
Content and data
Database, documents, users and permissions migrated and checked, and the search index rebuilt.
Go-live
On an agreed date, with a backup beforehand and a rollback ready.
And then, maintenance
The team that migrates can maintain the portal and take it to the versions that follow.
How we work
First we review the portal and give you the risks in priority order, with a fixed-scope proposal. Then we rehearse the migration in a separate environment, without touching production. Your team tests the migrated portal in a test environment and approves the go-live. We work in short deliveries you can see.
Result
We have taken one portal from Liferay 6.2 to version 7.4 over more than ten upgrades, and another from Liferay 7.4 to Liferay DXP 2026.Q2.1 with its custom code rewritten. Both are in the published case studies.
How it is built
The migration is rehearsed in Docker containers with a copy of the database and the document repository. Liferay's upgrade process runs there as many times as needed, until it finishes clean and the portal starts with the real data.
Old custom code is reviewed piece by piece. When it pays off, WAR deployments become React client extensions and Service Builder entities become Liferay Objects, the model Liferay DXP recommends. That makes the next upgrade cheaper than this one.
What sits underneath usually changes with the version: the Java version, the Elasticsearch search engine and the database. We upgrade them in the same project and leave deployments automated with CI/CD on GitLab, across environments and with rollback.
No change reaches production without going through four review agents (security, accessibility, quality and functionality) and a person. The quality gate is the one on all our projects: a minimum of 80 % test coverage and 0 open issues in SonarQube.
Frequently asked questions
My Liferay version is out of support. Where do you start?
By reviewing what is there: architecture, data, access, deployments and technical debt. We give you the risks in priority order and a fixed-scope proposal. Then we migrate.
Can several versions be skipped in one go?
It depends on the starting version and on the custom code. That is why we rehearse first with a copy of your data: the rehearsal shows which path is viable and what has to be adapted.
What happens to the custom code?
It is reviewed piece by piece. Some is adapted to the new version, some is replaced by features the platform already ships, and some is retired because nobody uses it.
Does the portal stop working during the migration?
The work is done in a separate environment. Production is only touched in the final step, on the date we agree, with a backup and a rollback ready.
Do you also migrate from Liferay DXP to Liferay CE?
Yes. We have done it for a public body, keeping the functionality it had. It is among the published case studies.
Also in Portals and development
Liferay maintenance
Patches, incidents, changes and versions, with the same team.
Liferay consulting
Architecture, performance and integrations, to decide with data.
Liferay audit
The real state of the portal, with the risks in priority order.
Liferay training
Tailored Liferay courses for teams, on their own portal.
Public sector
Accessibility, sign-in with Cl@ve and the Spanish National Security Framework (ENS).
The next step
Tell us how you work today and we will tell you where to start.