Hi, The current strategy for when we introduce new fields for content is that we try (wherever possible) to keep the old fields in place. This is designed to help clients who have lots of applications to have a parallel run period in which to code and check both fields. This isnt always possible when there is a specific venue feed change that means we lose the original data, but in general we do. The issue with this is we tend to them have lots of legacy fields and duplicated data. It is strongly advised to switch to the new fields as soon as you can, especially as we are looking to phase out some of the older fields in the not so distant future.