Sulu Webspace XML Compatibility: Upgrading from 2.5 to 3.2

When moving a production Sulu instance from 2.5 to 3.2, the team must preserve the existing multi‑site configuration that lives in the webspace.xml files. These files define the base URL, supported locales, and theme mapping for each webspace.

In 3.2 the XML schema for locales and themes has been updated to support new features such as locale fallbacks and theme inheritance. The current configuration uses the legacy <locale> tags and a flat <theme> element, which may no longer be accepted by the new parser.

To avoid breaking the site, the team needs to understand:

• Which parts of the XML structure are still valid in 3.2?
• What concrete changes are required for the <locale> elements and theme definitions?
• Is there an automated migration tool or script provided by Sulu to convert legacy webspace.xml files to the 3.2 format?