Moving from Vero to Vero2

Upgrading is optional. Vero and Vero2 share the same major features, and Vero 1 remains supported. Vero2 is recommended for new stores or a planned redesign. Both versions are included with your Vero purchase under the existing licensing rules.

Treat a Vero-to-Vero2 migration as a new theme setup. Existing theme settings and customizations do not automatically transfer; rebuild the configuration and layouts manually in the Shopify theme editor. The palette system and changed section/block settings mean a copied Vero configuration is not a reliable migration method.

Record your current setup

Duplicate your published Vero theme. Record your navigation, templates, section layouts, typography, colors, app embeds, custom CSS, and product assignments. List the products that exercise uploads, paid options, minimum quantities, accessories, Hat Lab, Bulk Order, Team Stores, and quote requests.

Store products, collections, pages, metafields, and metaobjects remain store data. Their theme display and template assignments still need checking. Theme settings, custom code, and app embed activation must be reviewed in the new theme.

Rebuild on an unpublished theme

1. Install and activate Vero2 without replacing the published theme.
2. Recreate your palette using Colors and styling. Do not paste Vero color scheme IDs into Vero2 controls.
3. Recreate section and block layouts. Match content first, then apply the new styling controls.
4. Configure mobile typography, buttons, forms, drawers, and product card treatments.
5. Re-enable required app embeds and check product templates with the intended products selected in the editor.
6. Port custom CSS and Liquid selectively after checking whether Vero2 already provides the setting or behavior.

The Guided Patch Builder is optional. Installing Vero2 does not assign its product template automatically.

Validate before publishing

Test a simple product and each custom workflow used by your store. Confirm variant pricing and availability, required inputs, minimum quantities, original artwork attachments, linked fee quantities, removal of a parent item, discounts, and checkout totals. Verify Team Store access, catalog/quote behavior, navigation, account links, search, and app integrations.

Check desktop and mobile, keyboard navigation, reduced motion, long labels, and empty states. Preview links do not establish that a template has been assigned correctly on the published theme; check assignments again after a planned switch.

Keep a rollback path

Retain your previous theme and record the time and settings of the switch. If a critical ordering flow fails, restore the previous published theme while the issue is investigated. Review Setup notes and troubleshooting for the support details to collect.

Configure optional new ordering features

If your store needs separate front/back uploads, set up back artwork and its charge product explicitly. If you use brand domains, follow alias-domain setup and test each hostname; a preview on the primary domain does not test those mappings. Review conditional patch designers when artwork should be required only for certain choices.