Online Store 2.0 Theme Migration: Moving a Vintage Theme

Many Indian Shopify stores still run a theme built years ago: the homepage has sections, but product, collection and cart pages are fixed templates only a developer can change. Every new banner, comparison table or FAQ block turns into a ticket, or into another app.

Online Store 2.0 theme migration fixes that by moving the theme to JSON templates and sections. This guide explains when it is worth doing, which route to take, how a manual migration works step by step, and what usually breaks, so you can plan it without putting live sales at risk.

What is Online Store 2.0, and what is a vintage theme?

A vintage theme is a Shopify theme built on the original architecture, where only some pages, usually the homepage, support sections. An Online Store 2.0 theme uses JSON templates, so sections and blocks can be added to most pages from the theme editor.

Shopify's help centre on theme architecture versions lists three types: vintage, Online Store 2.0, and themes that support theme blocks, such as the Horizon family. It also notes that Shopify's free vintage themes do not receive updates beyond security fixes, which is one reason older stores slowly fall behind.

What do you gain from migrating?

You gain sections on every page, app blocks, dynamic sources, and the ability to create new templates in the editor. According to Shopify's comparison table, these features are not available in vintage themes:

For a D2C brand the practical result is that marketing can add a size guide, delivery note or ingredient panel to a product page without a developer. If you use metafields for that content, our metafields and metaobjects guide shows how to structure it.

When should you not migrate?

Do not migrate when the store is stable, the theme meets your needs and nobody asks for changes. Shopify's migration assessment states that upgrading to Online Store 2.0 isn't mandatory and merchants can continue using a vintage theme.

A migration also costs money and carries risk, so the case is weaker if you sell a small catalogue, rarely change page layouts and have no plans to run campaigns. If you are unsure, an audit of your current theme will tell you what you are missing before you commit to a rebuild.

Which migration path should you choose?

Choose by how happy you are with the current theme and how many customisations it carries. Shopify's assessment describes three routes, and the right one depends on your answers:

Installing a new theme is the cheapest route, but you will rebuild homepage content and re-apply customisations. Manual migration keeps your design and custom Liquid, but it is the most technical. Shopify notes that apps and manual customisations cannot be migrated automatically, so heavily customised themes are the hardest to move.

How does a manual migration work? A step-by-step process

A manual migration converts one template at a time. Shopify's migration guide uses product.liquid as the example, and the same pattern applies to every template:

1. Back up the theme. Duplicate it and keep the copy unpublished. If you work locally with Shopify CLI, run shopify theme pull first.
2. Find and remove {% section %} tags. Note which sections the template includes, then delete the tags, because section files cannot reference other section files.
3. Move the template code into a section. Paste it above the {% schema %} tag of an existing section, or create a new file in /sections.
4. Delete the Liquid template. A product.liquid and a product.json cannot sit in /templates together.
5. Create the JSON template. Add product.json with a main entry whose type is the section file name, plus an order array.
6. Test in the theme editor. An Add section button should appear in the sidebar on that page.
7. Re-add the other sections. Declare sections such as product recommendations in the JSON file and set their order.
8. Support app blocks. Add a block of type @app to the section schema so merchants can place app blocks without code.
9. Repeat for every template. Do the same for collection, cart, blog, article, page and search.

Once the main section works, make it modular. Split fixed fields such as vendor or price into blocks, so the merchant controls their order. Our guide to building custom Shopify sections with Liquid and schema covers settings, presets and limits.

What usually breaks during migration?

Third-party scripts, app injections and hard-coded layout assumptions break most often. These are the problems we plan for in a vintage-to-OS 2.0 move:

• App code pasted into templates. Old review, wishlist or upsell apps often inject Liquid snippets that no longer render. Reinstall them using app blocks where the app supports it.
• Duplicate or missing JSON-LD. Product and breadcrumb schema can be dropped or doubled when markup moves. Compare structured data before and after.
• Theme settings that no longer map. Settings used by moved code must still exist in the new schema.
• Section limits. A JSON template can render up to 25 sections, each with up to 50 blocks, according to Shopify's JSON templates documentation.
• Page speed regressions. Adding sections everywhere makes it tempting to stack heavy modules. Review images and scripts as you go, and read our Core Web Vitals checklist alongside this work.

Run Theme Check on the migrated theme, and test product, collection, cart, search and blog pages on mobile, with real products and empty states.

How much does migration cost in India?

Cost depends on the number of templates, custom code and apps, not on store size. The ranges below are indicative estimates from project experience, not quotes:

Theme licences, paid apps and GST are extra. For the wider picture, see our Shopify store development cost guide.

How Arham Technology approaches Online Store 2.0 migration

Our Shopify Liquid development service follows a change-control process so the live store stays stable while the theme changes:

• Theme audit: we map the active theme's templates, section references, app injections and performance hotspots, and recommend install, update or manual migration.
• Section spec: we define which settings, blocks and content models each migrated template needs, so marketing can self-serve afterwards.
• Development theme build: work happens on a copy, with Theme Check and regression passes across product, collection, cart and homepage contexts.
• Merchant preview: your editors build a real campaign on the migrated theme and flag friction.
• Publish and guardrails: we document the settings, leave rollback notes and monitor storefront health after publishing.

Deliverables include Online Store 2.0 sections with merchant-friendly schema, reusable snippets, metafield-driven content and theme code clean-up. If you also need new features or a rebuild, our Shopify development service covers the wider store.

Next step

If your store still runs a vintage theme, the first step is an audit, not a rebuild. Send us your store URL and the pages you want to change through the contact page, and we will recommend whether to install, update or migrate, with an estimate. You can also read more about our Shopify Liquid development service before you reach out, or start with our Shopify Liquid development guide.