Hotel Catalog Migration Guide

• Centralized features: The enhanced catalog infrastructure receives all new platform features, so all hotel advertisers automatically receive these going forward.
• Unified catalog management: Advertisers and partners who manage catalogs for the Hotels vertical benefit from a single, consistent API surface.

• Access to the hotel catalogs you manage — directly, through a third-party platform, or via the Marketing API
• The ability to update the API integrations that reference catalog, product set, and feed IDs
• Your Meta partner contact, who shares your specific migration schedule and delivers the asset ID mapping file
• Familiarity with the catalog and ad endpoints you currently use (Catalog Batch API or Feed URL uploads, ad creation, and reporting)

• Catalog IDs — each legacy hotel catalog maps to a new catalog
• Product set IDs — product sets are recreated in the new catalog
• Feed IDs — feed configurations are recreated for the new catalog

• legacy_asset_id — the asset’s ID in the legacy Hotels vertical
• new_asset_id — the corresponding ID on the enhanced catalog infrastructure
• asset_type — one of CATALOG, PRODUCT_SET, or FEED
• legacy_catalog_id — the legacy catalog the asset belongs to (equals legacy_asset_id on CATALOG rows)
• business_id — the business that owns the asset, included for reference

legacy_asset_id,new_asset_id,asset_type,legacy_catalog_id,business_id
486201975530148,991034728165092,CATALOG,486201975530148,782451093366120
634829107744201,358017442299863,PRODUCT_SET,486201975530148,782451093366120
129574863320907,704412295583061,FEED,486201975530148,782451093366120

• Feed format remains the same — CSV, TSV, and XML are all supported, with no change to file format
• Field names remain the same — no change to any feed fields, such as hotel_id, name, and address
• The endpoint changes — the feed URL endpoint must reference the new catalog ID
• POST /{new_catalog_id}/batch replaces POST /{legacy_catalog_id}/batch
• POST /{new_catalog_id}/items_batch replaces POST /{legacy_catalog_id}/items_batch

• Campaign promoted_object.product_catalog_id — new catalog ID
• Ad set product_set_id — product sets within the new catalog

• GET /{new_catalog_id}/product_sets replaces GET /{legacy_catalog_id}/product_sets
• Product set filter rules and product counts carry over to the new catalog
• Dynamic product set filters (based on product attributes) continue to work with the same filter syntax

• During the transition period (approximately 90 days after cutover), expect duplicate reporting in Ads Manager — both legacy and new assets can show impressions
• API reporting via /act_{id}/insights includes both — filter by product_catalog_id to separate legacy versus new metrics during the migration phase
• After the transition period, only new catalog data is active
• Recommendation: Track performance by retailer or advertiser ID rather than catalog ID during migration so that metrics can be combined across both

• Meta automatically mirrors any changes from the legacy catalog to the new catalog
• You can continue writing to legacy catalogs during this transition — changes propagate automatically
• Once cutover completes, Meta stops the double-write system. The new catalog becomes primary, and the legacy catalog becomes read-only
• After the double-write period ends, writes to the legacy catalog fail — send all updates to the new catalog

• Feed file format — CSV, TSV, and XML formats are unchanged
• Feed field names — such as hotel_id, name, description, url, image_url, address, and price
• Creative template syntax — such as {{hotel.name}} and {{hotel.price}}
• Optimization goals — all campaign optimization objectives remain the same
• Pixel and Conversions API (CAPI) events — event names and parameters for hotel events remain the same
• Ad formats — carousel, single image, and collection ads all continue to work
• Audience targeting — retargeting, broad audience, and lookalike targeting remain unchanged

1. In the Developers portal, open the app that manages your hotel catalogs.
2. Open your Marketing API settings or Catalog API settings. If you have eligible hotel catalogs, you see a card titled Migrate your hotel catalogs to new asset IDs marked Action required.
3. Select Manage catalog migration to open the migration dialog. The dialog lists your eligible hotel catalogs.
4. Select the checkbox for each catalog whose mappings you want.
5. Select Download mappings. The button shows the number of catalogs selected — for example, Download mappings (3).