Find Shopify Redesign Candidates [Historical Data]

A theme name can identify a migration question; it cannot establish a redesign need. Our March 9, 2026 extraction found 57,594 stores with named legacy-theme matches among 240,429 stored domains. The useful agency workflow is to shortlist those stores, confirm their current architecture and identify a concrete task the merchant cannot perform easily.

A store using Dawn can already have a distinctive, well-maintained storefront. A vintage theme can be customized or partly migrated. Neither a free theme nor a detected Plus label proves neglected design, budget or buying intent.

Some links in this article are affiliate links. We may earn a commission if you purchase through them, at no extra cost to you.

What the March research supports

The retained query used stored theme names/types, traffic tiers, app counts, lead-fit scores and contact counts. It did not measure current storefront appearance, Core Web Vitals, conversion, revenue, project budgets or agency close rates. Extraction date is not the date of every underlying crawl; ages were not retained. Counts below are historical research pools, not a current validated sales list.

Named legacy-theme matches

The returned eleven names total 57,594 (23.95% of this database). The script also searched Launchpad but returned no row for it. Theme names can be renamed, and name matching does not prove the exact code version or its current architecture. Verify the theme identity before offering migration work.

Traffic and query-scope reconciliation

The original higher-traffic legacy table reported 808 matches, including 11 Jumpstart stores. Its filter was any stored traffic tier other than <10k or <50K, not an explicit normalized 50K+ list. Other old or unrecognized labels can satisfy that filter. We therefore call these historical filter matches rather than asserting all 808 were validated above 50K visits.

The segment and app-bucket queries used only ten legacy names, omitting Jumpstart. Their legacy app buckets sum to 797 = 808 − 11. This explains the scope difference; the ten-name segments cannot be presented as complete eleven-theme counts.

For a new list, use explicit recognized tiers (50K–200K, 200K–1M, 1M–5M, 5M–20M and 20M+), include all relevant legacy names, and separately report unclassified traffic. These are proposed validation rules, not a claim that we reran the historical extraction.

The separate traffic distribution can be reconciled directly:

The explicit 50K+ rows contain 3,193 free-theme domains, including 111 at 200K+. They do not imply 3,193 redesign needs. Overall, 109,605 domains were classified free (45.6%), 84,901 paid and 45,923 custom. “Custom” is a stored classification, not an audit confirming a bespoke build.

What vintage architecture actually changes

Shopify distinguishes vintage, Online Store 2.0 and newer theme-block architectures. Its architecture guide says Shopify's free vintage themes receive no updates beyond security fixes. OS 2.0 supports sections across pages and editor-connected dynamic sources; theme-block themes add further customization. Determine the installed version and template support in the theme editor, including any partial migration. Shopify architecture guide. Checked October 10, 2026.

Avoid blanket claims that every app needs manual Liquid edits: app embeds work on vintage themes. Likewise, metafields can be displayed through Liquid even where editor dynamic-source support is absent. The specific task and integration determine whether an architecture change is necessary. Theme app-extension documentation, displaying metafields. Checked October 10, 2026.

A paid theme is not a requirement for Shopify Plus checkout features. Shopify's current B2B documentation describes availability across plans, with additional capabilities on Plus. A free storefront theme does not itself disable those plan capabilities. If pricing is relevant, the current advertised USD Plus starting price is $2,300/month on a three-year term or $2,500/month on a one-year term; a detected Plus flag cannot establish what a particular merchant pays. Shopify Plus pricing, Shopify B2B. Checked October 10, 2026.

Separate visual observations from technical hypotheses

Lead-fit scores are not speed measurements. The March legacy-theme means of roughly 43–60 and Dawn's 57.8 do not establish page performance or conversion loss. Score differences partly follow app/pixel inputs. Use merchant-owned field performance data or a documented page/device/version test when performance is the proposed problem.

A useful observation is specific: a product page has no visible size guide beside its selector, or the merchant cannot add a needed product section in the editor. Record the URL, date, device, interaction and what was actually seen; an absent visible element alone does not prove customers struggle with it.

For example, our October 10 read-only observation of a Gymshark product page found seven size choices, a Size Guide and a four-product Get The Look carousel. Those existing features are reasons to ask about the current merchandising workflow, not evidence that the store needs them added. We did not inspect checkout, submit forms, test mobile performance or measure conversion.

Use the historical patterns to narrow research

Among the five category rows retained in the research summary, free-theme domains in the higher-traffic filter were Fashion 914, Home & Garden 399, Beauty 340, Food & Beverage 224 and Jewelry 222. Beauty's displayed free-theme rate was 9.9%, but category counts do not measure responsiveness to a design pitch. Choose a category where your experience helps you assess the actual storefront requirement.

The app-category query found no tracked email match on 28.6% of free-theme filter matches, no reviews match on 51.2%, no upsell match on 91.1%, no analytics-app match on 90.5% and no loyalty match on 81.3%. The mean was 3.4 unmatched categories out of five, also 3.4 for paid-theme stores and 3.7 for custom-classified stores.

These are detector gaps, not missing capabilities. Native Shopify analytics, theme upsells, custom reviews and backend services can be invisible to the app-category query. Confirm the actual workflow before proposing an additional app or expanding a project.

Popular paid themes are not observed upgrades

Prestige and Impulse each had roughly 8,500 matches; Impulse was below 8,500. Focal's displayed mean score exceeds Turbo's, but neither score proves theme quality. This snapshot has no before/after migration panel, so these are observed footprints, not themes merchants were seen upgrading to. Evaluate a theme against catalog, content, accessibility, integration and maintenance requirements instead of recommending it solely because it is popular.

Build a list, then qualify each store

1. Choose a concrete service requirement. For example, migrating product templates so staff can rearrange content in the editor. Avoid “free theme” as the problem definition.
2. Filter a research pool. Use theme identity, explicit estimated traffic tiers and category in StoreInspect. Inspect current pages and theme evidence for each shortlisted domain. Record snapshot/observation dates.
3. Validate the contact. Having at least one stored contact is only stored availability. Confirm person, role relevance, current employer, email type, verification status and date. A deliverability check does not establish consent or buying authority.
4. Ask about the requirement. Separate what you observed from what you want the merchant to confirm. Agree on scope before suggesting a full migration or new tool stack.
5. Evaluate the proposed change. Compare modifying the existing theme with migrating. Plan content, app compatibility, accessibility and performance verification; estimate effort and benefits from merchant evidence.

A hypothetical message after a verified architecture check: “Your product template appears to use vintage architecture. Are staff able to rearrange the product content in the theme editor? If that is limiting your workflow, I can outline a migration or a smaller template change.”

For a modern free theme: “I noticed [specific observed interaction] on [page]. Is that the intended experience for [customer task]? I can share the steps I used to check it.” Do not invent a broken interaction, budget or payback period. See our qualification guide and email templates for keeping observations distinct from assumptions.

Frequently asked questions

Is a free theme a redesign signal?

It can help organize research, but it does not prove weak design. Current free themes support modern storefront architecture and can be extensively customized. Identify the unmet task first.

Are the 609 contact matches ready to email?

No. They are historical ten-theme query matches with a positive stored contact count. Role relevance, employer, email status, age and applicable outreach requirements still need checking.

Which paid theme should I propose?

Select from verified requirements and a current theme preview. The March popularity table is context, not evidence of migration outcomes, performance or conversion gains.