Liferay Upgrade Planner
Pick a source and target Liferay version to get an ordered, checkable upgrade plan — breaking changes, deprecated APIs, data-upgrade steps, and commands.
Choose your upgrade path
Liferay 7.1 → Liferay 7.2
(4 steps)Update the liferay.workspace.target.platform.version in gradle.properties so BOM-managed dependency versions resolve against 7.2.
liferay.workspace.target.platform.version=7.2.1-1
Methods deprecated back in 7.0/7.1 are removed in 7.2. Rebuild every module against the 7.2 target platform and fix any unresolved references.
Snapshot the database and document library, deploy 7.2, and complete all module upgrade processes before allowing traffic.
Each release targets a specific Elasticsearch line. Confirm your ES cluster matches the version 7.2 supports before upgrading, and update the search connector configuration accordingly.
Tip: This is a representative checklist of the major steps for each version hop, ordered pre-flight → breaking → deprecated → data upgrade → tooling. Always take a full database and Document Library backup before each hop, and confirm exact requirements against the official Liferay upgrade docs for your edition.
Upgrading Liferay 7.1 to Liferay 7.2
This plan covers the full path from Liferay 7.1 to Liferay 7.2 — 1 version hop and 4 steps in total. Work through each numbered hop in order; every hop runs its own database and module upgrade processes, so they cannot be skipped. Take a full database and Document Library backup before starting each one.
Hops in this path
- Liferay 7.1 → Liferay 7.2 — 4 steps
Before you start
- Back up the database and the Document Library, and test the upgrade on a copy of production first.
- Patch your current version to its latest fix pack before beginning.
- Confirm exact JDK, app server, and Elasticsearch requirements for Liferay 7.2 in the official docs.