Commissioner
Migration truth Supported vs planned

Migration tracks stay explicit about what is supported now.

This route distinguishes shipped upgrade paths from tranche-owned and planned migration coverage. It exists to avoid promising import or migration breadth that the pack and site routes have not closed yet.

Supported tracks are called out explicitly. Planned tracks stay marked planned. Migration stories route back into pack and release surfaces.

Migration language stays constrained by pack ownership and release-train truth.

Decision guide

Compare the base subscription with optional add-ons.

Migration language stays constrained by pack ownership and release-train truth.

Compare Base + Add-Ons Browse Add-On Packs See Pricing + Add-On States
1 Supported tracks now
2 Tranche-owned tracks
2 Planned tracks
Migration route map
Migration route map Migration guide is only credible when the route labels supported and planned paths separately.
Truth before breadth
Guide 01
Shipped now

Snapshot-to-snapshot site upgrades

Current release train and rollback drills keep in-platform upgrades explicit and traceable.

  • Current status Shipped now
  • Evidence route Release notes
  • Release notes Snapshot version history remains visible and non-marketing.
  • Status route Operational state stays public-safe and aggregate.
Guide 02
Tranche-owned

Property feed and listing data migration

Listing-heavy tenants can trace migration scope to property-focused pack routes and importer-aware site surfaces.

  • Current status Tranche-owned
  • Primary pack Property Directory Automotive pack
Guide 03
Planned

Editorial CMS consolidation

Content-heavy migrations stay visible as planned scope until the publishing pack site workbench is fully closed.

  • Current status Planned
  • Owning pack Content Publishing
  • Content Publishing The owning pack route for editorial and documentation flows.
  • Reference route Publishing guide remains visible without overclaiming import coverage.
Guide 04
Tranche-owned

Events, bookings, and education migrations

Timed-experience migrations stay tranche-owned and route back to the split 52F industry surfaces instead of an obsolete blended slug.

  • Current status Tranche-owned
  • Owning pack Events Bookings Education pack
  • Events Bookings Education pack The selling surface for timed-experience operators.
  • Events industry Named 52F industry route traced from the shared events-bookings-education surface setup.
  • Bookings industry Named 52F industry route traced from the shared events-bookings-education surface setup.
  • Education industry Named 52F industry route traced from the shared events-bookings-education surface setup.
Guide 05
Planned

Commerce catalog migrations

Commerce migration messaging remains planned until storefront, checkout, billing, and order surfaces close as a full pack.

  • Current status Planned
  • Owning pack Commerce Subscription
  • Commerce pack The future owning surface for commerce migration guide.
  • Compare route Commercial language stays consistent while commerce breadth is still closing.
Guide 06
Tranche-owned

Support, knowledge, and community migrations

Help-center, ticket, incident, and community migrations stay tranche-owned and route back to the named 52G industry and feature surfaces instead of the retired blended support-and-community slug.

  • Current status Tranche-owned
  • Owning pack Support Community Knowledge pack
Guide 07
Tranche-owned

Cross-pack migration and recovery surfaces

52H keeps migration, export, backup, and integration-adjacent ownership visible on named public feature routes instead of collapsing it into one generic guide page.

  • Current status Tranche-owned
  • Feature routes Migrations, Exports And Backups, Integrations
  • Integrations Named 52H feature route traced from the shared cross-pack extra-features surface setup.
  • Migrations Named 52H feature route traced from the shared cross-pack extra-features surface setup.
  • Exports And Backups Named 52H feature route traced from the shared cross-pack extra-features surface setup.
  • Migration guide route The guide route keeps supported-versus-planned claims explicit.
Migration rule Setup truth

What this route must never do

It cannot imply that every upstream CMS, store, or feed is already covered if the owning pack and site import surface are not closed.

  • Allowed Snapshot upgrades, route-family ownership, and planned-state marking.
  • Not allowed Unbounded importer claims or hidden assumptions about data portability.
Validated

validation-1771969452 (beta)

Snapshot-backed release record with module and post-type version governance.

  • Snapshot id 218346347
  • Module versions 119
  • Post type versions 64
  • Built at 2026-02-24T21:46:30.140013
  • Hero Initial release
  • Rich Text Initial release
  • Cta Initial release
  • Split Initial release
Disclosure

Migration disclosure: support claims on this route are intentionally narrower than the eventual catalog universe until the owning packs close.

Keep supported migration truth tied to live selling routes

Keep the supported-versus-planned story grounded in compare, packs, launch-path, and sign-in.

Compare Base + Add-Ons Browse Add-On Packs