Liferay is powerful enough for a government portal, a banking intranet, and a Fortune 500 digital experience platform. For the organizations paying Java developer rates just to move a paragraph, that power has a price that no longer makes sense.
The Java Stack and the Cost of Staying
Liferay runs on Java and requires a Java application server (typically Apache Tomcat or WildFly). Every custom portlet, theme extension, and integration component is written in Java. Every meaningful change to the site structure involves a Java developer. That is not an accidental architectural choice. It is the platform’s defining characteristic, and it has real financial consequences.
Liferay DXP (the commercial version) carries enterprise licensing costs that can reach tens of thousands of dollars per year before you add server infrastructure, a dedicated Java development team, and the operational overhead of running a JVM-based application under load. Liferay Community Edition is free, but the developer skills required to run it are not. The talent pool for Java CMS work is both smaller and more expensive than the pool for WordPress, where virtually every web agency has staff, and where competent content editors can make updates without developer involvement at all.
Content Editors Locked Out of Their Own Website
The problem is not just cost. It is the operational dynamic that Liferay creates inside every organization that runs it. Liferay was designed as a portal platform for IT departments. It was built to give developers control over every aspect of a complex, role-based, multi-audience digital environment. That is exactly the right tool for some organizations. But it is the wrong tool when the people who need to publish content, update landing pages, and respond to search trends are the marketing team, and the ticket queue to IT is the only way anything changes.
The old Liferay platform required an outside developer to maintain the content, making it hard for the Anderson team to update content frequently and in real-time. When this became too cumbersome and too expensive to manage, Anderson wanted to review options, and we determined that migration to WordPress would achieve the following objectives.
Shero Commerce, Anderson Center for Autism case study, February 2025
Marketing and content teams often feel locked out, relying on IT for routine updates. Limited agility is one of the primary reasons organizations choose to migrate from Liferay to WordPress.
Dellos.in, Liferay to WordPress Migration Guide, April 2026
Liferay’s main drawback lies in its complexity and steep learning curve, hindering quick implementation and customization for non-technical users. Additionally, its extensive features can overwhelm smaller projects, leading to resource-intensive maintenance.
Capterra verified review, Liferay DXP, 2024
The only problem in Liferay is the licence cost is too high compared to other products in the market. The support community is very small so I have faced problems regarding coding.
Senior Bid Manager, Capterra verified review, Liferay DXP
Anderson Center for Autism is a documented real-world example: a nonprofit whose Liferay site delivered measurable value (35% increase in donations, 20% improvement in conversion rate after a previous refresh) but whose ongoing content management dependency on external developers eventually made the platform untenable. The decision to migrate to WordPress was driven not by the platform failing, but by the platform being the wrong tool for an organization that needed to move independently.
Liferay Portlets and Their WordPress Equivalents
Every piece of functionality in Liferay is delivered through portlets: self-contained Java web applications that run inside the Liferay portal container. When migrating to WordPress, portlets cannot be ported. Each one must be mapped to a WordPress plugin, theme component, or custom-built feature. The table below maps the most common Liferay portlets to their WordPress counterparts, including the community feature that matters most: the Liferay Message Boards moving to wpForo 360° AI.
| Liferay Portlet | What It Does | WordPress Equivalent | Cost |
|---|---|---|---|
| Web Content Portlet | Structured content creation with templates and versioning | WordPress Posts + Pages + ACF Pro custom fields | Free + Pro |
| Document Library | Centralized file management with metadata and access control | WordPress Media Library + WP File Manager | Free tiers |
| Message Boards | Community forum with categories, threads, replies | wpForo 360° AI (full forum with AI features) | Free + Pro |
| Form Builder | Multi-step forms with workflow and notifications | Gravity Forms / WPForms / Fluent Forms | Free tiers |
| Blog Portlet | Multi-author blog with comments and tags | WordPress native blogging (built in) | Built in |
| Calendar Portlet | Event scheduling and display | The Events Calendar (700k+ installs) | Free core |
| Wiki Portlet | Collaborative documentation and knowledge base | WP Pages + custom CPT / Echo Knowledge Base | Free tiers |
| Announcements Portlet | Time-limited notice and alert system | WordPress Posts / custom CPT | Built in |
| Polls Portlet | Voting and survey tools | YOP Poll / WP Polls | Free |
| Navigation Portlet | Hierarchical menus and breadcrumbs | WordPress Menus (built in) | Built in |
| Liferay Commerce | Product catalogues, cart, and checkout | WooCommerce (8M+ active installs) | Free core |
| FreeMarker Theme | Java/FreeMarker template files for site design | Custom WordPress PHP theme | Custom dev |
| Roles and Permissions | Granular site-wide and page-level access control | WP User Roles + MemberPress / Ultimate Member | Free core |
A note on the Message Boards migration. Liferay Message Boards store discussion threads, categories, and subscriber data in the portal database. gConverter migrates this content directly into wpForo 360° AI, mapping Liferay categories to wpForo categories, threads to wpForo topics, and replies with full author and timestamp data. The result is a fully populated AI-powered community forum with search, subscriptions, and member rank features that Liferay Message Boards never provided.
What a Proper Liferay Migration Involves
Migrating Liferay to WordPress is not a content export and import. Liferay stores content, users, files, and portal configuration across dozens of database tables with a Java-specific schema. A proper migration reads the source database directly and handles each layer explicitly. Here is how each component is handled.
Web content and structured content
Liferay Web Content is stored in the JournalArticle table with content versions and structure definitions. Each Web Content structure (the equivalent of a content type) has associated templates (the equivalent of theme templates) that define how content is rendered. A proper migration reads every JournalArticle record, maps the structured field values to ACF Pro custom field groups in WordPress, and creates posts or custom post types that match the original content hierarchy. Content versioning and author attribution are preserved.
Document Library files
Liferay Document Library stores files in the DLFileEntry table with metadata and access permissions stored separately. All documents, images, and media files are exported and imported to the WordPress Media Library with their original filenames, alt text, and folder hierarchy preserved. File references within web content are updated to point to the new WordPress media URLs.
Message Boards to wpForo
Liferay Message Boards data is spread across MBThread, MBMessage, and MBCategory tables. Categories become wpForo 360° AI categories. Threads become topics. Messages become replies, nested correctly under their parent threads. User attribution is cross-referenced with the Liferay user system to correctly assign authorship throughout the forum history. Thread view counts and reply counts are preserved as metadata.
Users and roles
Liferay users are stored in the User_ table with roles managed through UserGroupRole and Role_. All registered users are imported to WordPress with role mapping: Liferay Administrator maps to WordPress Administrator, Content Publisher to Editor, and Guest roles map to Subscriber. Custom roles are created in WordPress with equivalent permission structures. User profile fields from Liferay‘s expando attributes system are imported as WordPress user meta. Password hashes use different algorithms between the two systems, so users receive a secure reset link on first login.
FreeMarker theme to WordPress theme
Liferay themes are built with FreeMarker templates that cannot be ported directly to WordPress. A proper migration delivers a custom WordPress theme that replicates the visual output of the original Liferay theme exactly: every header and footer variant, every layout column configuration, every section style, and every component used across the portal. The result is visually identical to the original site but built on native WordPress PHP templates with no dependency on the Liferay portlet framework.
Pages and navigation
Liferay pages (stored as Layout records) define the portal page hierarchy and the portlet instances placed on each page. Each page is mapped to a WordPress page or template. The portlet layout configuration (sidebar, main content area, header zone) is replicated in the WordPress theme template structure. Navigation menus are rebuilt programmatically preserving all levels of the original site hierarchy.
SEO and URL structure
Liferay uses friendly URL patterns configured per page. Where these can be replicated in WordPress permalink settings, they are preserved exactly. Where the structure must change, 301 redirects are created for every affected URL. SEO metadata from Liferay‘s SEO settings per page is imported to Yoast SEO. No page goes live without its SEO titles and descriptions intact.
What Bad Liferay Migrations Look Like
- Web Content structure ignored. Generic migration tools pull the raw HTML output of rendered Liferay pages but miss the structured data in JournalArticle fields entirely. Product specs, team bios, event details, and any other structured content arrive as unformatted text blocks or are dropped entirely.
- Document Library not migrated. Files stored in the Liferay Document Library are not imported to the WordPress Media Library because generic tools do not know how to extract them from the DLFileEntry schema. All document download links become 404s after launch.
- Message Boards abandoned. Liferay forum content is skipped entirely because no standard WordPress importer handles the MBThread/MBMessage table structure. Years of community discussion are lost.
- FreeMarker template copy-pasted. Some migration providers attempt to convert the FreeMarker template directly to PHP. The result is broken layouts, missing template variables, and a theme that works on the homepage but fails on every other page type.
- User accounts dropped. The Liferay User_ table with expando attribute fields is not handled by generic tools. All user profile data beyond basic account information is lost, and content authorship is broken throughout the migrated site.
- No URL redirects. Liferay friendly URL patterns are replaced by default WordPress slugs with no redirects. All inbound links and search rankings for specific pages break immediately after launch.
GDPR and Your Data
A Liferay database contains the personal data of every registered user of your portal: names, email addresses, hashed passwords, user profile attributes, Message Boards post history, and in enterprise deployments often role-based access records tied to sensitive internal content. For financial institutions, healthcare organizations, and government agencies running on Liferay, this data may be subject to GDPR, HIPAA, or sector-specific regulations that govern how it can be transferred and processed.
Migrating this database to WordPress is a personal data transfer that requires a Data Processing Agreement before any provider accesses your data. gConverter is US-registered with full EU GDPR compliance. We sign a DPA before any access is granted. All credentials are stored in AES-256 encrypted vaults, transmitted over TLS 1.3, and deleted within 24 hours of job completion. All customer data is permanently deleted within 30 days. Read the full GDPR documentation →
What Clients Say
Went FAR above and beyond to help us work through this project. We are thrilled with the final result and they were professional, great to work with, and responsive every step of the way. Would highly recommend.
Anna P., Wilmington NC – Customer Lobby, January 2026
Very few conversion issues on the first pass, and they cleaned it right. Very Impressive.
Stacy C., Katy TX – Customer Lobby, November 2025
The Bottom Line
Liferay is genuinely enterprise-grade software. For a government agency running a citizen portal with hundreds of user groups and dozens of custom portlet applications, it may still be the right tool. For the vast majority of organizations that landed on it because it sounded serious enough for their requirements, it is several orders of magnitude more than they need, at a total cost of ownership that compounds painfully over time.
WordPress is where 60% of the web lives, where every content editor already knows how to work, where the plugin ecosystem covers every business requirement, and where a marketing team can publish, optimize, and iterate without waiting for Java developers. Every Liferay page, web content record, document, forum thread, and user account can be migrated cleanly.