Support Import/Export of Redirect Rules in CSV Format

Product Ideas
1

What is the problem you are trying to solve?

Organizations operating websites and portals for many years often accumulate thousands of URL redirect rules, especially after multiple platform migrations (e.g., WordPress → SharePoint → Liferay).

Currently, Liferay Redirects can only be managed individually through the user interface. This creates significant operational challenges when administrators need to review, update, migrate, audit, or maintain large numbers of redirect rules. Manual management is time-consuming, error-prone, and does not scale well for enterprise environments.

Typical scenarios include:

  • Bulk updates of destination URLs.
  • Cleanup and standardization of existing redirect mappings.
  • Migration of redirects between environments.
  • Migration from legacy CMS or portal platforms.
  • Backup and restore of redirect configurations.
  • Audit, reporting, and governance of redirect repositories.
  • Sharing redirect configurations between teams.
  • Maintaining redirect mappings under version control outside of Liferay.

What is your project about? (e.g. Intranet, Partner Portal, Enterprise Website, etc)

Enterprise public-facing website (banking sector).

The platform has undergone multiple migrations over the years and contains a large repository of redirect rules that must be maintained to preserve SEO, user experience, and backward compatibility of legacy URLs.

What is your proposed solution? (optional)

Add native Import/Export functionality for Redirect Rules in a CSV (Excel-compatible) format.

The enhancement could include:

  • Export all redirect rules to CSV.
  • Import redirect rules from CSV.
  • Support bulk creation of redirect rules.
  • Support bulk updates of existing redirect rules.
  • Allow offline review, validation, and mass editing before re-import.
  • Enable migration of redirect configurations between environments.
  • Provide an efficient way to backup and restore redirect settings.

This functionality would significantly reduce administrative effort, improve data quality, and simplify large-scale website migration and maintenance projects.

PATTERN;TARGET;APPLICATION;PRIORITY;STATUS_CODE;NOTE

^/legacy-page\.asp$;/new-section;portal;0;MOVED_PERMANENTLY;Legacy CMS migration

^/old-product-page([./])?([\?#].*)?$;/products/new-product-page$2;portal;1;MOVED_PERMANENTLY;Content restructuring

^/campaign-summer-2026([./])?([\?#].*)?$;/campaigns/summer-offer-2026$2;portal;1;MOVED_PERMANENTLY;Marketing campaign URL

^/mobile-banking([./])?([\?#].*)?$;/personal-banking/mobile-app$2;portal;1;MOVED_PERMANENTLY;Product page relocation

^/documents/old-brochure\.pdf$;/documents/new-brochure.pdf;portal;1;MOVED_PERMANENTLY;Document repository migration

^/products/(type-a|type-b)/detail/([A-Z]{2}\d{10})$;/investments/detail/$2;portal;1;MOVED_PERMANENTLY;Regex-based dynamic redirect

^/online-banking$;https://online.example.com;portal;1;MOVED_PERMANENTLY;External application redirect

^/customer-survey$;https://survey.example.com/form;portal;1;MOVED_PERMANENTLY;Temporary business campaign

^/app-deeplink$;myapp://open/dashboard;portal;1;MOVED_PERMANENTLY;Mobile deep link

^/old-category(/.*)?$;/new-category$1;portal;1;MOVED_PERMANENTLY;Site structure reorganization

2

In the meantime, have you considered using the JSONWS endpoints i.e. /api/jsonws?contextName=redirect or RedirectEntryLocalServiceUtil via a groovy script to manage the Redirects