Dawn to Horizon Migration: An Honest Guide for 2026

Shopify launched Horizon at Editions Summer ’25 in May 2025. It is now the default theme for new Shopify stores. Three things make it different from Dawn, and only one of them is cosmetic.

First: theme blocks, nested deeply. Dawn builds a page by stacking sections. Horizon uses theme blocks that live in their own /blocks folder, are reusable across sections, and nest up to eight levels deep. This is the whole reason there is no automatic migration — a Dawn homepage is a list, a Horizon homepage is a tree. Second: web components on the front end. Horizon’s interactive parts are built as self-contained web components rather than shared monolithic Liquid. Third: AI block generation in the editor, where you describe a block in plain text and Shopify generates the Liquid, styles and schema.

No, and this matters for the decision. Dawn still ships, still receives updates, and Shopify’s help documentation still lists it as a supported Online Store 2.0 theme. Shopify classifies themes that support theme blocks — the Horizon family — as the newest architecture version, but Online Store 2.0 themes remain a supported architecture, distinct from the older vintage themes that only get security fixes.

Dawn is not deprecated. It is no longer the front of the queue. New theme capability will land on the block architecture first, and that gap widens over time. So the question is not “is Dawn dying.” It is “when does the gap cost me more than the rebuild.”

Every template and every page layout — homepage, product, collection, cart, blog, all custom landing pages. Rebuilt, not ported. Custom Liquid sections do not drop into Horizon and work. Sections and theme blocks have different schemas and different composition rules. Custom sections are re-authored as blocks.

App embeds and front-end apps are the surprise item. Apps that manipulate the DOM — sticky add-to-cart, upsell widgets, swatch apps, some review apps — often hook the variant picker or cart drawer with selectors written for Dawn. In Horizon those are web components, and encapsulation blocks the old approach. List every installed app, check each for Horizon support, and test on the unpublished theme before you touch anything else.

Move to Horizon if: you are launching a new store, you are already redesigning, your marketing team lives in the theme editor and keeps hitting Dawn’s limits, or your Dawn theme is heavily hacked and fragile. If a rebuild is happening anyway, do it on Horizon — the marginal cost over another Dawn redesign is small, and you buy years of relevance.

Stay on Dawn if: your store is performing and the design is fine, mobile speed is your primary lever right now, you have deep custom development with no budget for re-authoring, or your critical apps do not support Horizon yet. There is no prize for moving early. The theme is not the business.

Anyone quoting a Horizon migration without seeing your theme is quoting a template, not your project. The two variables that move the number are the amount of custom Liquid in your current theme, and the number of front-end apps that need reworking. A near-stock Dawn store with five standard apps is a straightforward rebuild.

A four-year-old Dawn theme with twenty custom sections and a bespoke bundle builder is a different project with a different price. The one thing we will say without seeing the store: if a four-hour fix on Dawn gets you the outcome you actually want, we will tell you that instead. Not every store needs Horizon this year.

Shopify’s Dev MCP server exposes current Shopify documentation and schemas to AI coding tools, which makes AI-assisted section-to-block conversion meaningfully more accurate than working from a model’s training data. It speeds the work. It does not replace review, and it does not replace Theme Check.

Speed assumptions matter too. Third-party testers publishing Dawn vs Horizon comparisons in 2026 consistently report that Horizon’s out-of-the-box mobile scores trail Dawn’s, while desktop is competitive or better. Run PageSpeed on a real Horizon build with your real images and apps before you commit. AiSalesQ tracks platform changes like this one closely so your quiz keeps running through any theme migration.