Read the launch recap as historical context
Nuxeo LTS 2025 brought changes that deserve explicit upgrade planning, particularly around search and application dependencies. A launch presentation is useful orientation, but the exact release, hotfix level and installed packages determine the work for an existing system.
This page separates those planning concerns from launch-time expectations. Check the LTS 2025 release notes for the maintenance version you intend to deploy.
Search is an upgrade workstream
The new SearchService replaces ElasticSearchService, which was removed in LTS 2025. Custom code and dependencies using the old service require review. Search clients also need to match the intended backend. Search upgrade guide
Inventory custom page providers, direct search integrations and audit queries. For each, identify the expected result shape, permission behavior and freshness requirement. A successful application startup is not enough to accept the search migration.
Review storage and custom dependencies
The LTS 2023-to-2025 upgrade guide documents S3 configuration changes, removed implementations and dependency changes. Existing encrypted content deserves a specific retrieval test, not only a test of newly uploaded files.
Record the current package set and compare it with the target release's compatibility matrix. Review custom Java code, automation, front-end extensions and integrations as separate components with owners.
Turn the upgrade into an acceptance plan
| Workstream | Evidence before cutover |
|---|---|
| Content access | Existing and newly created files can be retrieved with the correct permissions. |
| Search | Representative queries return the expected content, including after recent updates. |
| Processing | Required conversions and asynchronous jobs complete, and failures remain visible. |
| Integrations | External callers handle the selected API and authentication behavior. |
| Operations | Backup, restore, monitoring and rollback procedures are rehearsed. |
Choose a pilot workflow and record its results on the exact target hotfix and package combination. Keep a list of unresolved exceptions with a business owner for each one.
Keep roadmap and support commitments separate
A future interface or AI integration should not be treated as a delivered feature merely because it appeared in a launch discussion. Verify availability, compatibility and licensing for the proposed deployment. Confirm support dates with the applicable vendor agreement before scheduling a migration around them.
For a scoped assessment, see Maretha upgrade services and the performance diagnostic guide.
Work with Maretha
Working through a content platform challenge?
Bring your platform, constraints and questions. Let us help you work through the approach.
Discuss your project ↗