All posts
Liferay · 10 min read · Jun 12, 2026

When not to customize Liferay

When not to customize Liferay

The most expensive line of code in an enterprise portal is the one you did not need to write. Liferay ships with content management, workflow, permissions, search, page building, and headless APIs out of the box. Yet many teams reach for a custom module the moment a requirement appears, before checking whether the platform already solves it. Knowing when not to customize is a senior skill, and it usually saves more time than any clever implementation.

Customization is a long-term liability

A custom module is not a one-time cost. It has to be rebuilt against every Liferay release, retested after every patch, documented for every new developer, and migrated whenever an API it depends on changes. A small customization that takes a day to write can cost weeks across a multi-year upgrade cycle. Before writing code, it helps to weigh that full lifecycle cost rather than the initial effort.

Check the platform first

Most requirements that look custom map onto an existing capability if you know where to look. Run through the platform options before deciding anything is missing:

  • Content and structure: web content structures, templates, and fragments cover most layout and editorial needs without code.
  • Data: Liferay Objects model custom entities, relationships, and REST APIs through configuration instead of Service Builder modules.
  • Logic: workflow definitions, expressions, and Objects actions handle approvals and side effects declaratively.
  • Integration: headless APIs and the OAuth2 framework connect external systems without custom servlets.

A decision ladder

When a requirement arrives, climb the ladder from cheapest to most expensive and stop at the first rung that satisfies it. Each step up adds maintenance and upgrade cost, so the goal is to stop as early as possible.

OptionUpgrade costUse when
ConfigurationNoneThe behavior exists and only needs settings
Objects / web contentLowYou need custom data or editorial content
Client ExtensionLow to mediumYou need custom UI or front-end logic
Custom OSGi moduleHighDeep server-side logic with no supported alternative
Core override / fragmentVery highLast resort; avoid whenever possible
Climb from the top and stop at the first row that solves the problem.

Signs you are over-customizing

Some patterns reliably indicate that customization has gone too far: overriding core JSPs to change small details, duplicating features the platform already provides, hardcoding behavior that should be configurable, or maintaining modules nobody fully understands. When upgrades routinely take months because of accumulated custom code, the customization strategy itself is the problem.

When customization is the right call

None of this means customization is bad. Genuine business differentiators, integrations with proprietary systems, and complex domain logic often justify custom modules. The point is to make that choice deliberately, with the full lifecycle cost in view, rather than as a reflex. The best Liferay teams treat every customization as a decision they will have to defend at the next upgrade.

Contact

Let’s connect

Have a Liferay or Backend project you’d like to talk through? Fill in the form and I’ll get back to you.

Book Calendar