Migration issue from Liferay 7.4 to 2026.Q1

Development Upgrades
1

Issue encountered after migrating Liferay from version 7.4-ga132 to 2026.Q1.6 involving Site Templates and page import/export behavior.

After migration, pages associated with a migrated Site Template are no longer properly created or imported.

Scenario 1 — Site creation from migrated Site Template

Steps to Reproduce

  1. In Liferay 7.4:
    • Create a Site Template
    • Add several pages to the template
    • Create a site from this template
    • Verify that pages are correctly created
  2. Upgrade/migrate the portal to Liferay 2026.Q1
  3. In Liferay 2026.Q1:
    • Create a new site from the migrated Site Template

Expected Result

The new site should be created with all pages inherited from the Site Template.

Actual Result

The site is created successfully, but no pages are created.

The created site is empty.

Scenario 2 — LAR export/import issue after migration

Steps to Reproduce

  1. In Liferay 7.4:
    • Create a site from the Site Template
    • Export the site as a .lar
  2. Upgrade/migrate the portal to Liferay 2026.Q1
  3. In Liferay 2026.Q1:
    • Create an empty site
    • Import the .lar exported from 7.4

Expected Result

All pages from the exported site should be imported successfully.

Actual Result

The import completes, but pages are not imported.

The target site remains empty.

Additional Information

During import, the following exception is observed:

com.liferay.segments.exception.SegmentsExperienceNameException

Stack trace indicates the issue occurs during page experience (SegmentsExperience) validation:

SegmentsExperienceLocalServiceImpl._validateName

Why not run proper upgrade rather than export/import? Have seen quite number of issues arise during cross-version imports. Btw, Segments is one of the features that has been deprecated in 2026.q1, probably that is what the exceptions is about.

 –

We actually performed a proper full upgrade of the environment from 7.4 to 2026.Q1, and globally the migrated sites are working correctly. The issue we reported is related to a specific feature in our project that performs site cloning through export/import mechanisms. We use this process to duplicate existing sites/templates dynamically. The problem appears when importing pages created originally in 7.4 after the platform has been upgraded to 2026.Q1. During the page creation/import process, a SegmentsExperience is created for the new page with a null name. This later triggers a validation

 –

Yep, that is probably due to the deprecation of Segments in the latest version. You can still enable it in the feature flag section (at least for now, until they remove in the future versions)

 –