Shopify Replatforming: What to Migrate Before the Redesign

Shopify replatforming should not start as a redesign project.

A redesign changes what customers see. A replatform changes what the business runs on: catalog data, customer records, order history, redirects, checkout settings, fulfillment logic, integrations, analytics, lifecycle marketing, and the internal habits that keep the store moving.

If those pieces are not mapped before design decisions take over, the launch can look better while the operation becomes harder to run.

That is the real risk in a Shopify migration. The team focuses on the new storefront, but the actual business logic stays scattered across the old platform, apps, spreadsheets, custom scripts, warehouse rules, POS workflows, email segments, and undocumented team knowledge.

The better question is not "what should the new Shopify store look like?"

The better question is: "What has to keep working on day one, and what should be improved before we move it?"

Start with the operating map

Before choosing templates, apps, or redesign scope, map the current operation.

Shopify's migration guidance frames the move as a sequence of setup tasks and platform-specific migration paths. That is useful, but for a growing merchant, the checklist should be grounded in how the business already operates.

Map the pieces that affect revenue and execution:

• Product data, variants, bundles, metafields, images, and collection rules.
• Customer records, consent state, tags, segments, loyalty data, and order history.
• Redirects, canonical URLs, priority landing pages, and SEO dependencies.
• Payment, tax, shipping, pickup, returns, and fulfillment rules.
• POS, ERP, warehouse, subscription, marketplace, B2B, and marketing integrations.
• Email and SMS lifecycle logic in Klaviyo or another marketing platform.
• Analytics, pixels, server-side events, attribution, and reporting habits.
• Operational workflows the team uses every week but has never documented.

This map tells you what to preserve, what to clean, and what to rebuild. Without it, replatforming becomes a cosmetic project with hidden operational risk.

Decide what deserves to move

Not every old field, tag, redirect, collection, app, automation, or customization deserves a new life in Shopify.

Migration is a chance to remove operational drag before it becomes part of the new system.

The cleanup questions are practical:

• Which product attributes are reliable enough to drive filters, recommendations, feeds, or AI workflows?
• Which customer tags are still meaningful, and which were one-off campaign leftovers?
• Which URLs still earn traffic, revenue, links, or assisted conversions?
• Which apps are actually used, and which exist because nobody wanted to remove them?
• Which custom features support real buying behavior?
• Which checkout, shipping, or fulfillment rules are exceptions that need to be simplified?

Shopify's migration checklist includes importing store content and data, setting up shipping, taxes, payment, redirects, and testing before launch. The important part is not only completing those tasks. It is deciding what version of those tasks should move forward.

A weak migration copies the old mess into a new platform. A strong migration uses Shopify as the point where the operating model gets cleaner.

Protect the pages that already matter

SEO risk is usually underestimated during replatforming.

The team changes templates, URLs, information architecture, page content, scripts, and performance at the same time. If nobody owns the migration map, important pages disappear into generic redirects or launch with weaker content than before.

Before launch, define the protected page set:

• Top organic landing pages.
• Top revenue pages.
• Top collection and product templates.
• Blog, guide, and resource pages that earn search visibility.
• Pages with backlinks or branded demand.
• Paid landing pages, email landing pages, and campaign destinations.
• Policy, FAQ, support, and post-purchase pages customers rely on.

Each important URL needs a destination, a content decision, a redirect decision, and a validation check. That does not mean every old page should stay. It means the team should make deliberate decisions before launch rather than discovering traffic loss afterward.

Treat integrations as business logic

Most Shopify replatforming projects are not blocked by the theme. They are blocked by the rules around the theme.

Examples:

• A product can only ship from certain locations.
• Wholesale buyers need different pricing, payment terms, or catalog visibility.
• A subscription flow needs to preserve customer expectations.
• Returns depend on product type, location, or order history.
• Klaviyo segments depend on old customer tags or event names.
• POS staff need inventory, pickup, exchange, and customer profile rules to behave consistently.
• Finance or operations needs order data to arrive in a specific structure.

These rules are not decorative. They are business logic. If they are discovered late, launch becomes reactive. The team starts adding emergency apps, manual workarounds, or custom code because the operating model was not translated early enough.

Replatforming should turn those rules into a build plan before design approval.

Build the validation plan before launch week

Testing should not be a final pass where someone clicks around the new site. The validation plan should be written while the migration is being scoped.

At minimum, test:

• High-priority redirects and canonical behavior.
• Key collection, search, filter, and product-page paths.
• Product options, bundles, subscriptions, discounts, and recommendations.
• Checkout, payment, tax, shipping, pickup, and order-confirmation logic.
• Customer account, order history, return, and support paths.
• Email capture, abandoned cart, post-purchase, and lifecycle flows.
• Analytics, pixels, conversion events, and reporting continuity.
• Mobile performance and layout stability on the pages that matter.
• Admin workflows for merchandising, fulfillment, content, and customer support.

Shopify's ecommerce replatforming guide includes testing, SEO audit, launch, and post-launch monitoring as core steps. For a complex merchant, those steps should be owned like a migration workstream, not treated as launch-week cleanup.

Use the redesign to support the migration, not hide it

A redesign can be valuable. It can improve product discovery, brand expression, navigation, content, merchandising, and conversion.

But redesign should follow the operating plan.

If the team has not mapped data, redirects, integrations, fulfillment, lifecycle logic, and analytics, design decisions can accidentally create new problems:

• Beautiful collection pages that need product attributes the catalog does not have.
• Product pages that depend on content fields nobody can maintain.
• Landing pages that remove search intent the old page was ranking for.
• Checkout promises that operations cannot fulfill.
• Lifestyle navigation that makes sense visually but weakens buying paths.

The design system should make the new operating model easier to use. It should not distract from unresolved migration decisions.

What to ask before replatforming to Shopify

Before committing to a migration scope, ask these questions:

• What has to keep working on day one?
• Which parts of the old platform should not be copied into Shopify?
• Which data needs cleaning before import?
• Which URLs, templates, and pages are protected?
• Which integrations carry business logic?
• Which launch risks need a rollback or manual fallback plan?
• Which workflows will the team run differently after launch?
• What will be measured in the first 30 days after launch?

The strongest Shopify replatforming projects are not the ones with the longest checklists.

They are the ones where the team understands what the platform change is supposed to fix.

Lake House Group supports Shopify migration as an operating project, not only a storefront rebuild. If your current platform is limiting catalog management, fulfillment, omnichannel workflows, lifecycle marketing, or team execution, talk to Lake House Group about migrating to Shopify.