Well supplying your own custom revision entity definition rather than using or extending the supplied ones is a supported configuration from Envers perspective and one which the Spring Data Envers wrapper should honor as well. Can you supply more information such as stack-trace, error, and your custom mapping to showing the problem?