Online Store 2.0 Migration: Moving an Old Shopify Theme Without Losing Sales

Open your theme editor, pick Products > Default product, and look under the section list. No “Add section” button? Then your store is still on a vintage theme, and every new landing page, upsell widget or metafield-driven spec table goes through a developer. That is the moment most brands start asking about an online store 2.0 migration.

The short answer: an online store 2.0 migration moves your storefront from Liquid templates to JSON templates, so sections, app blocks and metafields work on every page. You can get there three ways: switch to a current theme, rebuild a custom one, or port your old theme file by file. None of them touches your products, customers, orders or URLs. What can cost you sales is the stuff hiding in your old theme: pasted app scripts, tracking code, alternate templates and SEO markup that nobody wrote down. This guide is how we handle that part.

What a Shopify 2.0 theme changes, and what it leaves alone

A Shopify 2.0 theme stores each page layout as data (a JSON template) instead of hard-coded Liquid, which is what lets you add, remove and reorder sections on any page in the editor. Shopify lists the core features in its Online Store 2.0 developer overview: JSON templates, sections on every page, dynamic sources for metafields, and app blocks.

JSON templates and sections everywhere

On a vintage theme, templates/product.liquid is a fixed file. Sections can exist, but only where the developer hard-wired them, usually the homepage. On 2.0, templates/product.json is a list of sections plus their settings. According to Shopify’s JSON template reference, a template can hold up to 25 sections with up to 50 blocks each, and a theme can have up to 1,000 JSON templates. That is why “sections everywhere” changes how marketing works: a launch template becomes an editor job, not a ticket.

App blocks and app embeds

Apps built on theme app extensions add their UI as blocks you place in the editor, and Shopify says those apps “don’t edit theme code.” Older apps did the opposite: they injected snippets or asked you to paste a script into theme.liquid.

Metafield dynamic sources

You can connect a text, image, rich text or product list setting straight to a metafield. The dynamic sources docs cap it at 100 connections per JSON template. On catalog-heavy stores this alone can justify the move: size charts and care notes stop living in product descriptions.

What does not change: your catalog, customer accounts, order history, checkout, Shopify Payments, domains, and the URL structure of products, collections and pages. Those belong to the platform, not the theme.

The feature gaps in that table come from Shopify’s Help Center page on theme architecture versions, which also lists theme blocks and the Planet app as unavailable on vintage themes.

How to tell whether you need a vintage theme migration

The fastest check takes 30 seconds: go to Online Store, click Edit theme on your live theme, open Products > Default product, and look for an “Add section” button in the left sidebar. If it’s there, you’re on 2.0 or later. If it isn’t, you have a vintage theme. That is Shopify’s own test from the versions page linked above.

We also check the code, because the editor test can mislead on half-migrated themes. Open Edit code from the theme’s three-dot menu and expand Templates:

• Mostly .json files (product.json, collection.json, page.json): a 2.0 theme.
• Mostly .liquid files (product.liquid, collection.liquid): vintage.
• A mix: someone started a port and stopped. It is the hardest state to maintain.
• An empty Sections folder: a non-sectioned vintage theme, the oldest kind. Expect a rebuild rather than a port.

One more trap: premium themes from 2019 and 2020 often had a vintage major version and a later 2.0 major version under the same name. A store running “Prestige” or “Impulse” might be several major versions behind. Compare the version on your theme card with the one in the Theme Store first.

Do you need an online store 2.0 migration at all?

Not strictly. Shopify says plainly in the same developer overview that upgrading isn’t mandatory, and a vintage theme can keep selling. Our position is firmer: if anyone on your team edits the storefront more than once a month, migrate within the next two quarters.

Shopify’s theme update documentation says vintage themes have been sunset and aren’t updated by Shopify anymore. New apps increasingly ship only as app blocks. Every year you stay adds another layer of one-off code to move later.

When we’d tell you to wait:

• You’re mid-replatform or planning a full rebrand in the next 6 months. Do it once.
• Nobody touches layouts (say, a B2B parts catalog).
• Peak season starts in under 8 weeks. Never launch a theme into Black Friday traffic. Start in January.

The three paths for a Shopify theme upgrade

You have three ways to do a Shopify theme upgrade: install a current Online Store 2.0 theme and rebuild your customizations on it, build a custom 2.0 theme, or port your existing theme by converting templates to JSON.

Path A: move to a Dawn-based, Horizon or premium theme

This is our default. You start from a theme that is maintained, accessible and already fast, then rebuild only the customizations that earn money. Dawn and the newer Horizon family are free and made by Shopify. Premium themes add merchandising features (mega menus, quick buy, richer product media). We compare the current options in our roundup of the best Shopify themes.

The trade-off: the store will look different unless you pay to match the old design.

Path B: port your existing theme

Porting means converting each Liquid template to a JSON template and moving its markup into sections. Shopify’s template migration guide walks through product.liquid as the example. At its simplest, the new templates/product.json just points at the section that now holds your old markup:

{
  "sections": {
    "main": { "type": "main-product" },
    "recs": { "type": "product-recommendations" }
  },
  "order": ["main", "recs"]
}

Then you add {"type": "@app"} to the section’s blocks schema so app blocks can sit inside it. Two rules from the guide catch people out: a template can’t exist as both product.liquid and product.json at the same time, and app blocks aren’t supported in statically rendered sections.

We only recommend porting when the current design converts well, is heavily custom, and the code is reasonably clean. Porting a theme with five agencies’ worth of edits preserves the mess.

Path C: custom rebuild on 2.0

A bespoke theme built from design files, usually on a clean base. It costs the most and takes the longest. It makes sense when a redesign was due anyway. If that’s you, our guide on running a Shopify store redesign safely covers the design side, and our Shopify store revamp service is built around exactly this kind of project.

Clean up app snippets in theme.liquid first

Before any migration, audit every script tag and snippet include in layout/theme.liquid, because that file is where years of app installs leave code behind. Uninstalling an older app rarely removes the script someone pasted into the layout.

Pull a copy of the live theme locally with Shopify CLI, then search it:

shopify theme pull --theme 123456789 --path ./old-theme
grep -nE "<script|{%-? ?(include|render) " old-theme/layout/theme.liquid
grep -rlE "https://[a-z0-9.-]+.(js|css)" old-theme/snippets old-theme/sections

Then sort every hit into one of four buckets:

1. Active app, now has an app embed or app block. Delete the pasted code and switch on the embed under Theme settings > App embeds in the new theme. Per Shopify’s app embed docs, embeds target the head or body, start switched off, and work on vintage and 2.0 themes alike.
2. Active app, still needs pasted code. Ask the vendor for their 2.0 install method before you copy anything across.
3. Uninstalled app. Don’t carry it over. Note the file names so nobody “restores” them later.
4. Tracking code (GA4, Meta, TikTok pixels pasted by hand). Move it to Settings > Customer events or the official channel app, so the next theme change can’t break it.

Keeping URLs and SEO safe on an online store 2.0 migration

An online store 2.0 migration doesn’t change your product, collection, page or blog URLs, so you usually need no redirects at all. SEO risk comes from what the theme outputs on those URLs. These are the items we diff between the old and new theme before launch:

• Title tags and meta descriptions. Many vintage themes build titles in theme.liquid with custom logic (appending the store name, adding page numbers).
• Structured data. Product JSON-LD is often hand-coded in the old theme or injected by an SEO app. Make sure exactly one source outputs it in the new theme, then run the Rich Results Test on a product page.
• Alternate templates. Products assigned to product.preorder.liquid fall back to the default template if no product.preorder.json exists. Recreate every alternate template with the same suffix before you publish.
• Collection filter URLs. Older themes often filtered by tag with links like /collections/shoes/red. If those pages earn traffic, keep them linked or redirect them on purpose.
• Heading structure. Some themes demote the product title from H1 or add extra H1s.
• robots.txt.liquid. If you customized it, copy it over. It stays a Liquid template even on 2.0 themes, as do gift_card and the newer llms.txt and agents.md templates, per the JSON template reference.

If handles do change during the project (people often tidy product names at the same time), add redirects under Online Store > Navigation > URL redirects, ideally in a separate release from the theme. We cover the rest of the on-page basics in our Shopify theme customization guide.

What an online store 2.0 migration costs, and how long it takes

Expect 40 to 130 hours to move to a new theme, 80 to 200 to port an existing one, and 200 to 450 for a custom rebuild. These are our own planning ranges. Multiply by your team’s rate: using the agency bands we sourced in our Shopify development cost guide ($25 to $50 an hour in India, $120 to $200 in the US or Australia), the table below shows what that comes to.

Add a theme licence if you pick a paid theme. Real quotes vary wildly. In one Shopify Community thread from December 2023, a merchant had a $15,000 quote and a $650 quote (9 hours) for the same 2.0 upgrade of a custom theme. Partners replying doubted the 9 hours. We agree: 9 hours buys a theme install, not a migration.

Worked example: a customized vintage theme to a premium 2.0 theme

Here is a hypothetical, but typical, Path A project. Say an apparel brand runs a heavily edited Debut theme with 450 products, three alternate product templates, and 11 installed apps, four of which pasted code into theme.liquid. They pick a premium 2.0 theme and want six custom features rebuilt.

1. Audit, app inventory and feature list: 10 hours
2. Theme setup and brand styling: 24 hours
3. Six custom features rebuilt as sections or blocks: 36 hours
4. Three alternate templates plus metafield connections: 14 hours
5. App cleanup and reinstall as embeds or blocks: 12 hours
6. SEO parity checks (titles, JSON-LD, headings): 8 hours
7. QA across devices and checkout: 16 hours
8. Launch and two weeks of monitoring: 6 hours

That’s 126 hours, about six weeks. At $45 an hour it costs $5,670; at $150, $18,900. Cutting the custom features to three saves about 18 hours.

QA and launch checklist for a vintage theme migration

Build the new theme unpublished, test it in preview against a written checklist, publish in a low-traffic window, and keep the old theme as a one-click rollback. Here’s our list.

For 14 days after launch, compare conversion rate, add-to-cart rate and organic clicks daily against the previous four weeks. A day-one dip is noise. A dip that holds for a week on one device type usually means a broken app block, not bad design.

Frequently asked questions

What we’d do first

This week, run the 30-second editor check, then open theme.liquid and count the script tags. That count tells you more about the size of your online store 2.0 migration than anything else. List every customization, mark the ones that earn money, and pick the path. For most brands it’s Path A.

Then pick a launch date at least two months away from peak, build on an unpublished theme, and don’t publish until the checklist above is green. If you’d like a team that has done this on stores for brands like Kerbholz, Maker & Moss and Medcline, our Shopify store revamp team can scope it with you.