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.0 → Liferay 7.1
(4 steps)More configuration is exposed as typed OSGi configuration in System Settings / Instance Settings. Review portal-ext.properties for keys that are now managed in the UI or via .config files.
The Lexicon/Clay component set is the standard for 7.1 UI. AlloyUI is on the way out — start migrating custom widgets toward Clay markup and tags.
Compile your modules against 7.1 and address deprecation warnings now; several 7.0-deprecated methods are removed in later releases.
Take a database backup, deploy 7.1, and let the automatic upgrade processes run (or trigger pending ones from Gogo with upgrade:execute). Verify completion before going live.
g! upgrade:list g! upgrade:execute all
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.0 to Liferay 7.1
This plan covers the full path from Liferay 7.0 to Liferay 7.1 — 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.0 → Liferay 7.1 — 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.1 in the official docs.