Migration from legacy Content Feed

You can use the following table to determine the data usage when migrating from legacy Content Feeds to Content 2.0.

Legacy Content Feed	Content 2.0 equivalent
Feed_id 1: Continents	Reference Data API > `continent` entity
Feed_id 2: Countries	Reference Data API >`country` entity
Feed_id 3: Cities	Reference Data API > `city` entity
Feed_id 4: Area within Cities	Reference Data API >`area` entity
Feed_id 5: Hotel	Properties API
Feed_id 6: Room types per Hotel	Properties API > `rooms` data
Feed_id 7: Picture per Hotel	Properties API > `media` data
Feed_id 8: Premium Picture	Properties API > `media` data
Feed_id 9: Facilities per Hotel	Properties API > `facilityIds` data
Feed_id 10: Other info per hotel	Properties API > `propertyDetails` and `highlights`
Feed_id 12: Reviews	Will be available soon in the Reference Data API >`review` entity
Feed_id 13: Languages and Codes	TBD
Feed_id 14: Facilities per Roomtype	Properties API > `rooms.facilityIds` data
Feed_id 15: Hotel Chains	Reference Data API >`chain` entity
Feed_id 16: Hotel per Hotels Brand	Not a direct mapping. You may refer to the Properties API > `propertyDetails.companyTraceabilityInfo` data
Feed_id 17: Hotel Description	Properties API > `propertyDetails.description` data
Feed_id 18: Hotel Address	Properties API > `propertyDetails.address` data
Feed_id 19: Full Hotel Information	Properties API
Feed_id 20: Hotel Brands	Reference Data API >`brand` entity
Feed_id 21: States/Provinces	Reference Data API >`state` entity
Feed_id 22: Benefits	Not a direct mapping. You may refer to the Properties API > `highlights` data for per-property benefits
Feed_id 30: Agoda Preferred Hotel	TBD
Feed_id 31: Local Information	TBD
Feed_id 32: Hotel Change	CDS API