Liferay Upgrade Program
From the upgrade assessment to go-live. Start with the assessment: identify your version, run the read-only script on your UAT environment and send the report to Liferay.
Why stay up to date with Liferay?
Every release makes your platform safer, faster and easier to build on. Here are the top five reasons to upgrade.
- SecurityThe latest security fixes protect your sites, your users and their data. Liferay security
- Supported and compliantStay within Liferay's support lifecycle, with fixes and help when you need them. Service life policy
- New capabilitiesUse what newer releases bring, such as AI features, Objects, client extensions and low-code tools. Explore the platform
- Performance and compatibilityRun on current Java versions, databases, application servers and browsers.
- Lower cost of ownershipRetire deprecated features and technical debt, and make every future upgrade smaller.
We're here to help. The Liferay upgrade program takes you from assessment to go-live with Liferay Customer Success, the Liferay Upgrade Team and Liferay Support at your side. It starts with a read-only assessment of your installation, which includes a free Liferay DXP architecture health check (best effort, for reference only). You can stop after the health check (step 3), with no obligation.
Start the assessment Contact Liferay- Phase 1 · Steps 0–4AssessmentReport, health check, qualificationLiferay Customer Success
- Phase 2 · Step 5PreparationDeliverables to the Upgrade TeamLiferay Customer Success
- Phase 3 · Step 6Core solution upgradePerformed by LiferayLiferay Upgrade Team
- Phase 4 · Step 7ValidationUAT testing and fixesLiferay Upgrade Team
- Phase 5 · Step 8Go-LiveGo-live, then support for OOTB featuresLiferay Support
Assessment
Steps 0–4Supported by Liferay Customer SuccessIdentify your version
YouFind your Liferay edition and version, then select it below.
- Sign in to Liferay as an administrator.
- Open Server Administration:
Your version Where to find Server Administration 6.1 Go to > Control Panel > Server > Server Administration 6.2 Admin > Control Panel > Configuration > Server Administration 7.0 – 7.3 Product Menu (top left) > Control Panel > Configuration > Server Administration 7.4 and Quarterly Releases Global Menu (grid icon, top right) > Control Panel > System > Server Administration Menu names are shown as in English. If your Liferay is set to another language, look for the same menus in that language.
Or open it directly:
https://<your-server>/group/control_panel/manage/-/server/resources(6.x), orhttps://<your-server>/group/guest/~/control_panel/manage?p_p_id=com_liferay_server_admin_web_portlet_ServerAdminPortlet(7.0 and later). - The version is shown at the top of the page. Examples:
Shown on the page Select Liferay Portal Community Edition 6.2 CE GA6Liferay Portal CE 6.2 Liferay Community Edition Portal 7.4.3.132 CE GA132Liferay Portal CE 7.4 Liferay Portal Enterprise Edition 6.1.30 EELiferay Portal EE 6.1 Liferay Digital Experience Platform 7.4.13 Update 92Liferay DXP 7.4 Liferay Digital Experience Platform 2025.Q1.29 LTSLiferay DXP 2025.Q1 LTS The same text is printed in the server log when Liferay starts (look for
Starting Liferay).
- Copy the read-only version check script:
- Run it in the Script console (step 1 explains how), with language Groovy.
- It prints the script to use, for example
Script: ce_7_4/ce_7_4-all.groovy. Select that version below, or type theScript:line here and it is selected for you:
Run the script on UAT
YouCopy the script for your version and run it in the Script console of your UAT / test environment.
site-1. All counts stay the same.
- Sign in to your UAT environment as an administrator.
- Open Server Administration (see step 0) and select the Script tab.
- Set Language to Groovy, delete the sample code and paste the script.
- Click Execute and wait until the page reloads. On large installations this can take a few minutes; don't click again.
- The result appears in the Output box. It starts with
"Key", "Value", "Description"and ends with lines starting with"uas_.
No Script tab, no Groovy option, or the script is refused?
- Sign in as an administrator of the default virtual instance (the first instance created). Server Administration is only available to these administrators.
- The Script Management setting in System Settings (Liferay DXP 2024.Q2 / Portal 7.4 GA120 and later) only controls scripts in Workflow and Objects. You don't need to change it to run this script.
- Your organization may have switched off scripting for security, for example by disabling the Groovy scripting module. Ask your Liferay administrator to allow it on the UAT environment for the assessment, and to switch it off again afterwards if that is your policy.
- If you still can't run it, tell Liferay your version and what you see; we'll help.
Save the output as a .txt file and send it to Liferay
YouSave the result on your own computer, then send it to Liferay by e-mail or as a support ticket.
Save the output:
- Click inside the Output box, select everything (Ctrl+A / Cmd+A) and copy it (Ctrl+C / Cmd+C).
- Windows: open Notepad, paste, then File > Save As and choose Text Documents (*.txt).
Mac: open TextEdit, choose Format > Make Plain Text, paste, then File > Save. - Name the file
<company>_<liferay-version>_upgrade-report_<yyyy-mm-dd>.txt, for exampleacme_dxp-7.3_upgrade-report_2026-11-02.txt. - Check that the last lines start with
"uas_(for example"uas_end_date"). If some lines containUAS ERROR, send the file anyway: it tells Liferay what could not be read.
Send it, by e-mail or as a support ticket. Send the report only as an attachment; don't paste it into a website or chat.
Option A: e-mail
- E-mail the
.txtfile as an attachment to support@liferay.com. - Put your Liferay customer success contact in CC, if you know who it is.
- Use a subject such as Upgrade assessment report – <company>.
Add your company and customer success contact to the e-mail
Option B: support ticket (Liferay subscribers with a Help Center account)
- Go to the Liferay Help Center and sign in with your liferay.com account.
- Choose Contact Support (or Submit a request) to open a new ticket, and select your project.
- Use the subject Upgrade assessment report – <company>, and in the description say that this is the report for the Liferay upgrade program.
- Attach the saved
.txtfile and submit the ticket. - If you know your Liferay customer success contact, let them know the ticket number.
Liferay replies on the ticket and notifies you by e-mail.
Health check
FREELiferay Customer SuccessLiferay reviews your report and carries out a health check of your installation: version, infrastructure, data volumes, customizations and features that are deprecated in newer releases.
See a sample health check report (PDF, fictitious data)
The health check is provided on a best-effort basis and for reference only. It is based on the output of the read-only script; it is not an audit, a guarantee or a warranty.
Deprecations and breaking changes by release (Liferay Learn)
Qualification and agreement
Liferay Customer Success → YouLiferay validates whether you qualify for the Liferay upgrade program. If you qualify, Liferay shares the contractual terms with you for sign-off.
Preparation
Step 5Supported by Liferay Customer SuccessPrepare the deliverables for the Liferay Upgrade Team
YouPrepare the deliverables for the upgrade and hand them off to the Liferay Upgrade Team. Liferay tells you what is needed.
Core solution upgrade
Step 6Supported by Liferay Upgrade TeamUpgrade execution
Liferay Upgrade TeamAfter the kick-off, Liferay performs the upgrade of your solution.
The Liferay Upgrade Team confirms the timeline and details after the assessment phase.
Validation
Step 7Supported by Liferay Upgrade TeamUAT testing and fixes
You + Liferay Upgrade TeamYou test the upgraded solution in UAT; issues found are fixed.
The Liferay Upgrade Team confirms the timeline and details after the assessment phase.
Go-Live
Step 8Supported by Liferay SupportGo-Live
You + Liferay SupportThe upgraded solution goes live. From then on, support comes from the Liferay Support team.