Moving to Shopify: A Store Migration and SEO Checklist

01

Start with the reason for moving

Write down three specific problems with the current store. Updating products may take too long, shoppers may struggle to choose a size on mobile, or the team may be unable to see where paid visitors abandon their journey. These are different problems. A new theme will not, by itself, fix inaccurate product information or an unclear operating process.

Consider whether the existing platform could meet the requirement with a reasonable change. Migration creates work of its own, so compare that work with the problem it solves. Assess Shopify against the catalogue, integrations, markets and everyday tasks of the people who will manage the store. A competitor’s attractive storefront is a reference, rather than evidence that the same setup suits your business.

A one-page decision brief is enough to begin: what works now, what creates friction, what should become easier and how you will check it. Prefer observable acceptance criteria to broad ambitions. A customer finding the right collection, a stock status appearing correctly and an employee updating a product without assistance are all more useful than an undefined request for a better website.

02

Define the scope through the order journey

Draw the route from finding a product to receiving a delivery update. Include search, collections, product options, cart, payment, order records and fulfilment. Name the system responsible for each step. This reveals which connections need to be rebuilt and which operational decisions the business needs to make before the website can be considered ready.

Products, collections, content pages and images do not necessarily move through the same method. Historical orders, customer accounts, discount rules, gift cards and application data need separate assessment. Information existing in the source platform does not establish that every field will behave identically in the destination. Ask about the limits of the chosen migration method before approving the scope.

Describe each deliverable as something that can be checked. For example, the selected size should show the correct availability, and an old collection link should reach its relevant replacement. Record exclusions too. If nobody knows who supplies translations, product photographs or accounting requirements, the delivery schedule still contains unresolved dependencies.

03

Find the pages worth protecting before you build

Do not create the old URL list from the main menu alone. A guide, collection or product that is absent from navigation may still receive search visits or appear in a campaign. Review the sitemap, Search Console landing pages, Analytics reports and advertising destinations together. Record the dates covered by each source; an address missing from one report is not automatically unimportant.

Use a working table with the old URL, page type, new destination, proposed action and verification result. Include discontinued products. A product becoming unavailable does not mean that the visitor’s question has disappeared. Decide whether the page should remain useful, whether a relevant replacement exists or whether the original content has genuinely been removed.

Prioritise widely used pages without limiting the inventory to them. Social profiles, printed QR codes, saved email links and partner references may also lead to old addresses. The goal is an informed decision about each journey. Preserving a large number of irrelevant pages is not the objective; helping a visitor reach the expected information is.

04

Clean the catalogue before importing it

Begin with a representative product group. Check names, descriptions, stock codes, options, prices, weights, image order and image descriptions together. Inconsistent size labels or duplicated colour names can become confusing filters and product choices after import. Agree on the naming system before repeating the same inconsistency across the new catalogue.

Consider an illustrative clothing store using S, Small and another language’s equivalent for the same option. A consistent label can help, but products from different manufacturers should not be treated as identical merely because the labels look similar. Check real measurements and source information before applying a bulk correction. This is a planning example, not a reported client outcome.

Build collections around the language customers use while shopping. Internal warehouse categories may be meaningful to the team and unclear to buyers. Approve a small sample migration before expanding it. Matching the number of imported rows is useful, but also open products with unusual options, missing information and different image arrangements. These cases often expose a problem earlier than a random inspection of standard products.

05

Map each old URL to a relevant destination

Someone following an old product link should find that product or a genuinely relevant replacement. Sending every old address to the homepage does not meet that expectation. Build the redirect plan at page level, check that destinations work and explain the decision where no equivalent page exists.

Shopify’s URL redirect documentation describes the conditions and exceptions that affect redirects. Compare those rules with the actual store. A successful import of a redirect file does not prove that every journey works. Open the original address and verify the final destination, including its relevance to the visitor’s intent.

Record chains, loops and unrelated targets as different issues. Link directly to final destinations inside the new store wherever possible. Review canonical URLs, sitemap entries and language alternatives against the published structure. After launch, monitor Search Console for crawling and indexing changes. Google may need time to process the move, so a few days of movement in a small report cannot establish that the migration succeeded or failed.

06

Make the new storefront easier to use

Look at a product on a small screen as a first-time customer. Can you understand what it is, see the price, choose the right option and identify the next action? Can you find delivery and returns information when you need it? Assess a theme through these tasks. A striking opening image cannot compensate for missing product information.

Give each photograph a job: overall view, material detail, scale or use. Repeated crops of the same image add less information than genuinely different views. Clearly identify illustrative imagery, and do not use a stock photograph as proof of the actual product’s characteristics. Optimise image delivery for the space in which it appears, while keeping useful detail visible.

For a long guide or collection explanation, use an immediate answer, section links and relevant further reading. A visitor should be able to take the useful part and continue naturally. Apply the same principle to menu labels, filters and contact links. Verify the mobile menu, option selection and cart action with real catalogue content rather than approving an empty theme demonstration.

07

Check payment and shipping against the business

Do not select a payment arrangement solely from the country of the intended customer. The company’s location, business category, provider eligibility and supported currencies also matter. Shopify’s supported-country list is the starting point for checking Shopify Payments eligibility. Where it does not apply, assess the available third-party providers separately.

For shipping, document product weights, packaging, delivery areas and exceptions. A single free-delivery rule may not produce the right result for every product and address. The business also needs an operating decision for returns, failed delivery and orders fulfilled from different locations. Website configuration should reflect that decision rather than quietly invent it.

The acceptance plan should name an appropriate test environment, an owner and a clear expected result. A test-mode success is different from confirmation that real payments are accepted. Any real transaction required for acceptance should be handled separately by the store owner under the provider’s conditions. This guide helps identify the decisions; it does not initiate a payment or replace the business’s operational approval.

08

Plan markets and languages together

Selling into the UK, Europe or another market involves more than displaying a different currency. Decide which products are available, how product information is written, what delivery statements apply, which support channel is offered and which store URL the customer uses. A language is not the same as a country; English content can serve several markets with different commercial conditions.

Shopify’s Markets SEO documentation explains how market and language configuration is presented to search engines. Choose the URL structure, then inspect the resulting language alternatives and canonical information on representative product pages. The platform offering a feature does not prove that every combination in a particular store has been configured correctly.

Review measurements, care information, delivery wording and support instructions carefully in translation. Avoid copying one promise across markets where the operation differs. Confirm tax, customs and legal requirements with the relevant advisers. Completing a credible customer journey for one market can be more manageable than launching many unfinished language versions at once.

09

Agree on measurement before launch

Write down the questions the reporting needs to answer. Where do visitors arrive, do they inspect products, do they add items to a cart and is an order actually created? Combining all these actions into a single conversion total makes it harder to identify where the journey needs attention.

When comparing the old and new store, check the date range, currency, consent settings and event definitions. A telephone or WhatsApp click is an expression of intent, not a completed conversation. An order record and an analytics event are separate sources that need reconciliation. Explain how cancellations and returns affect the figures rather than silently treating every recorded purchase as retained revenue.

Do not send names, email addresses, telephone numbers or message text into analytics events. Check whether multiple integrations report the same action. A technical setup can be completed while real-world acceptance remains outstanding; describe those states separately. WeAreMedia’s analytics and tracking service is the relevant place to discuss account ownership, data flows, conversion definitions and consent checks.

10

Use one launch plan with named responsibilities

Decide when product and stock information will be updated for the final time before switching. If the old store continues receiving orders while the new one uses a different stock snapshot, the operations team may have conflicting records. The data cut-off and order-reconciliation process therefore require the business’s participation, not just a developer’s decision.

For each launch step, record its owner, starting condition and verification result. Agree on the circumstances that would pause the switch and on who decides what happens next. Recovery involves more than restoring a theme: orders placed and stock changed during the transition also need an explicit plan. A useful recovery process is one the team understands before it becomes urgent.

Keep the immediate published-store checks manageable: homepage, key collections, representative products, old links, search, cart, contact details and reporting. Shopify’s migration guide provides the platform’s broader sequence. Adapt the checks to the store’s actual scope instead of treating a generic checklist as evidence that an implementation is complete.

11

Write an acceptance scenario before the final review

Select products that represent meaningful differences in the catalogue: a simple item, a product with several options, an unavailable variant and an item with different delivery conditions. Describe what a visitor should see and which operating record the team will check. Include the device, expected behaviour, observed result and the person responsible for a correction.

Have the future store operator practise updating a product and arranging its images. Record unclear steps as training or interface work. Keep one list of open issues, distinguishing launch blockers from work explicitly agreed for later. Complete the handover with account ownership, theme changes, licences, applications and continuing support responsibilities. This makes acceptance a reviewable process rather than a general statement that the website looks finished.

12

Understand what changes the migration cost

Product count alone is a poor basis for comparing migration quotes. A large, well-structured catalogue may require less preparation than a smaller catalogue with inconsistent fields. Languages, image work, old URL quality, integrations and post-launch support all affect the work. Ask the proposal to identify these dependencies explicitly.

Separate one-off work from ongoing costs. Discovery, design adaptation, data preparation, migration and verification form one group. Platform plans, theme or application licences and continuing support form another. Current charges depend on the provider and scope, so this guide does not supply an invented fixed price or universal delivery time.

Compare equivalent deliverables. One proposal may assume that the client supplies approved product copy while another includes editing it. Revision allowances, acceptance methods and training should also be visible. Instead of relying on an all-inclusive label, ask which files, checks and operating instructions will be delivered, and what happens when an integration requires work outside the initial scope.

13

Prepare for the first conversation with an agency

For the first enquiry, share the store URL, current platform, approximate product and variant count, target markets and the reason for considering a move. Say which decisions remain open. You do not need to produce a technical specification before speaking; the initial conversation should help arrange the unknowns into a useful sequence.

Ask how a sample import will be approved, who prepares the URL mapping, how application dependencies are reviewed and who checks the store after launch. Clarify account ownership, the access required and the handover at the end of the engagement. Look for a reviewable delivery process as well as attractive examples.

You can review WeAreMedia’s Shopify setup and migration service and inspect the scope of existing work in the project archive. A project example shows an implementation; it does not establish a sales or traffic result for your business. Your scope should be determined from the current store, operational requirements and the outcomes that can actually be verified.

EXPLORE AN IMPLEMENTATION

Maison Harleen

Review the storefront and product presentation on the project page. This example makes no claim about migration results or sales growth.

maisonharleen.com

View the project scope ↗

14

Review the first weeks without reacting to every fluctuation

After launch, check the customer journey first. Can someone find a product, choose the correct variant, understand delivery and follow an old link to the right destination? A concrete usability failure should be fixed when it is identified; there is no reason to wait for a monthly traffic report to address it.

For search and commercial performance, use completed, comparable periods. Seasonality, advertising changes, product availability and revised measurement definitions can all affect the comparison. Do not attribute every difference to migration. A handful of visits or orders is insufficient for a confident growth claim, and a technical check is not the same as business-performance evidence.

Changing several campaigns and design elements simultaneously also makes interpretation difficult. Maintain a prioritised issue list and make changes whose effect can be assessed. Complete the team’s training in adding products, arranging collections and handling orders. A useful outcome is a store the business can operate competently, with clear responsibilities for the support it still needs.

Frequently asked questions