GoLand Configuration Directory Migration and Version Compatibility

GoLand maintains a dedicated configuration directory separate from the application binaries to ensure settings persist across version upgrades. When updating the IDE, the system typically prompts to import settings from the previous installation to maintain user preferences and keymaps.

While global settings are handled by the IDE's import mechanism, project-specific configurations stored in the .idea folder are managed independently. There is a potential conflict when migrating between major versions where XML schema changes in the configuration files may occur, potentially leading to parsing errors if a manual rollback of the configuration directory is attempted.

What is the documented behavior for resolving XML schema mismatches when manually restoring a configuration ZIP archive from an older version into a newer GoLand installation? Does the IDE provide a mechanism to selectively revert specific configuration modules without performing a full 'Restore Default Settings'?