Quality Assurance and Testing
This part of the migration process is absolutely critical. A structured QA process reduces risk of downtime, emergencies or firefighting. The goal is to implement safeguards to ensure the new store works as intended - for customers and the people managing the site post-launch. Here are a few reasons why QA and testing is so important.
Protecting Revenue
Even a small issue in the checkout, payment or cart flow can prevent customers buying from you (and they’ll be heading to a competitor website in less than 10 seconds.)
Incorrect product pricing, discount logic or shipping rates can lose you sales or cost you more than intended.
Faulty integrations with fulfilment systems can lead to shipping delays, problems with returns, unhappy customers and reputational damage.
Preserving the Customer Experience
You need to ensure the navigation, search, product pages, and checkout all work as expected across all devices - particularly mobile, as it’s likely most of your traffic comes from here.
Avoiding SEO or Traffic Loss
URL redirects - we covered this in more detail in part 5, but you need to ensure that old URLs correctly point to your new Shopify URLs to avoid 404 ‘page not found’ errors.
Indexability and crawlability, including your XML sitemap and canonicalisation, need to be validated before you launch.
Reducing Operational Risk
Now is the time to check customer data, product data, and order histories have all been migrated successfully.
Apps, payments gateways, analytics and email platforms all need end-to-end testing.
Types of testing
Functional testing
As listed above, this refers to how the site actually works, so making sure browsing, search, add-to-cart, checkout flow etc are all as expected.
Cross-browser testing
Customers access ecommerce sites using a range of browsers, devices, and operating systems. Cross-browser testing ensures that layouts, functionality, forms, navigation, and checkout experiences perform consistently across Chrome, Safari, Edge, Firefox, and other commonly used browsers.
Mobile testing
Testing should focus on usability as well as functionality. This includes touch interactions, navigation menus, product image galleries, forms, checkout journeys, and page performance across different screen sizes and devices.
Payment testing
Payment failures have an immediate impact on revenue. Every payment method should be tested using real-world scenarios to confirm successful authorisation, order creation, refunds, cancellations, and payment status updates within Shopify and any connected systems.
User acceptance testing (UAT)
UAT provides an opportunity for key stakeholders to validate the site before launch. Teams from merchandising, marketing, customer service, operations, and ecommerce can test day-to-day business processes and confirm the platform meets both functional requirements and commercial objectives.
Ecommerce-specific scenarios
Discounts
Discount logic should be tested across a wide range of scenarios, including discount codes, automatic promotions, free gifts, loyalty rewards, bundle offers, and free shipping thresholds. Particular attention should be paid to situations where multiple promotions interact with one another.
Shipping rules
Complex shipping configurations often contain exceptions based on geography, weight, product type, delivery method, or order value. Testing should verify that customers are presented with the correct shipping options and charges throughout the checkout process.
Tax calculations
Incorrect tax calculations can create compliance issues and customer dissatisfaction. QA should confirm that tax rules are applied accurately across different jurisdictions, customer types, shipping destinations, and product categories.
Subscriptions
Where recurring purchases are offered, testing should validate the complete subscription lifecycle. This includes initial purchase, recurring billing, customer account management, subscription amendments, cancellations, and renewal communications.
Multi-currency
For international brands, testing should ensure that currency selection, exchange rates, pricing display, checkout calculations, and payment processing all function correctly. The customer experience should remain consistent regardless of the selected market or currency.
Customer accounts
Customer account functionality should be reviewed from both a user and operational perspective. Testing should cover registration, login, password recovery, order history, saved addresses, subscription management, loyalty programmes, and account updates.
SEO testing
We talk about this in part 5, but as a reminder, here are some key things to test.
Redirect testing
We’re mentioning it again here as it’s so key - you must verify that legacy URLs redirect to the most relevant new destination, avoiding redirect chains, loops, and broken links that could negatively impact search visibility.
Crawl testing
A full crawl of the pre-launch site can help identify technical issues before go-live. This process highlights broken links, duplicate content, missing metadata, redirect issues, orphaned pages, and other factors that may affect organic performance.
Metadata validation
Titles, meta descriptions, canonical tags, heading structures, image alt text, and structured data should all be reviewed to ensure important SEO signals have been retained during the migration and are implemented consistently across the site.
Analytics testing
GA4
Analytics validation should confirm that page views, ecommerce events, customer journeys, and conversions are being recorded accurately. Particular attention should be paid to purchase tracking, attribution data, and custom events used for reporting.
Meta Pixel
The Meta Pixel should be tested to ensure key ecommerce events such as View Content, Add to Cart, Initiate Checkout, and Purchase are firing correctly. This helps maintain audience building, campaign optimisation, and advertising performance after launch.
Conversion tracking
All marketing platforms should be reviewed to confirm conversion tracking remains intact following migration. This includes paid search, social advertising, affiliate platforms, email marketing tools, and any third-party attribution systems.
Server-side tracking
Many brands now use server-side tracking to improve data accuracy and reduce reliance on browser-based tracking methods. Testing should verify that events are passed correctly between Shopify, tracking servers, analytics platforms, and advertising channels while avoiding duplication or data discrepancies.
Capturing Benchmarks Before Migration
Before migrating to Shopify, it's important to establish a clear picture of your current ecommerce performance. Benchmarking key metrics allows you to accurately measure the impact of the migration, identify any unexpected issues after launch, and demonstrate the return on investment from the project. Without reliable baseline data, it can be difficult to determine whether changes in traffic, conversion rates, revenue, or customer behaviour are the result of the migration itself or broader market factors.
Metrics to capture pre-launch
Organic traffic
Record current levels of organic search traffic, including overall sessions, landing page performance, and key traffic-driving content. This provides a benchmark for monitoring SEO performance and identifying any post-migration visibility issues.
Conversion rate
Document your overall ecommerce conversion rate as well as performance by device, channel, and key customer journeys. This will help assess whether the new Shopify experience is improving the efficiency of the purchase process.
Revenue
Capture total revenue figures alongside channel-specific performance data. Monitoring revenue before and after launch helps quantify the commercial impact of the migration and identify any unexpected fluctuations.
AOV
Average order value provides insight into customer purchasing behaviour and basket size. Tracking this metric can help determine whether new merchandising strategies, upsell opportunities, or checkout improvements are delivering value.
Site speed
Measure page load times and Core Web Vitals across key templates such as the homepage, collection pages, product pages, and checkout. Performance improvements are often a key objective of a replatforming project and should be measured accordingly.
Bounce rate
While bounce rate should be interpreted carefully alongside other engagement metrics, it can provide a useful indicator of landing page quality and user experience. Significant changes after launch may highlight usability or content issues.
Indexed pages
Record the number of pages currently indexed by search engines and review which URLs are generating organic traffic. This benchmark helps identify indexing issues, missing content, or crawlability problems following migration.
Keyword rankings
Track rankings for your most valuable commercial, category, product, and informational keywords. This provides an early warning system for SEO performance changes and helps prioritise optimisation efforts after launch.
Checkout completion
Measure the percentage of customers who successfully complete checkout after initiating the purchase process. Any significant changes post-launch could indicate issues with payment methods, shipping configuration, or checkout usability.
Returning customer rate
Understanding how often customers return to make additional purchases provides a useful benchmark for customer retention and loyalty. This metric can help assess the impact of account functionality, customer experience improvements, and post-purchase journeys.
Tools to use
Google Analytics 4
GA4 provides a comprehensive view of traffic sources, customer behaviour, ecommerce performance, and conversion data. It should be the primary source for capturing baseline commercial and behavioural metrics.
Search Console
Search Console provides valuable SEO insights including organic clicks, impressions, indexed pages, keyword visibility, and crawl performance. Exporting this data before migration creates an important reference point for post-launch monitoring.
Ahrefs/Semrush
SEO platforms such as Ahrefs and Semrush can be used to benchmark keyword rankings, backlink profiles, organic visibility, and competitor performance. Historical ranking data is particularly valuable when assessing migration success.
Heatmaps
Platforms such as Hotjar, Microsoft Clarity, or Contentsquare provide insight into how users interact with the site. Capturing behavioural benchmarks before migration can help validate UX improvements after launch.
Launch Day Planning
A successful Shopify migration doesn't end when development is complete. Launch day is the culmination of months of planning, design, development, testing, and data migration, making it one of the most critical phases of the project. Having a structured launch plan helps minimise risk, ensures stakeholders are aligned, and enables teams to respond quickly should any issues arise once the new site goes live. A lot of the work will have been undertaken during QA and testing, but there are a couple of other things to add to your list before you go live.
Pre-launch
DNS preparation
DNS changes are often the final step in making a new Shopify store publicly accessible. Ahead of launch, teams should review DNS settings, lower TTL values where appropriate, and confirm access to domain management platforms. Proper preparation can help reduce propagation delays and minimise the risk of downtime during the transition.
Inventory sync confirmation
Where Shopify integrates with ERP, warehouse, fulfilment, or inventory management systems, a final synchronisation check should be completed before launch. This helps ensure stock levels, product availability, pricing, and order routing remain accurate from the moment customers begin placing orders.
Launch day activities
Defined stakeholders
Every launch should have clearly identified stakeholders and decision-makers. Representatives from ecommerce, development, marketing, customer service, operations, and key technology partners should be available throughout the launch window to support rapid issue resolution if required.
Live monitoring
Performance should be monitored closely from the moment the site goes live. Key areas include site availability, page speed, checkout performance, analytics tracking, order processing, inventory updates, and customer-facing functionality. Early detection allows issues to be addressed before they have a significant commercial impact.
Escalation channels
A clear communication and escalation process helps teams respond efficiently when issues arise. Dedicated launch-day communication channels, agreed points of contact, and defined severity levels ensure the right people are involved quickly and decisions can be made without unnecessary delays.
Rollback planning
While every effort should be made to ensure a smooth launch, contingency planning remains essential. A rollback plan should outline the steps required to revert critical systems, redirect traffic, or temporarily restore previous functionality if a major issue threatens customer experience or business operations.
Soft or Hard Launch?
Soft Launch
A soft launch involves releasing the new Shopify store to a limited audience before making it fully available to all customers. This may involve launching during a quieter trading period, gradually increasing traffic, or restricting access to specific user groups.
The primary advantage of a soft launch is reduced risk. Teams can monitor performance, validate integrations, and address issues using real customer interactions before significant traffic volumes arrive. The downside is that operating both old and new environments simultaneously can increase complexity and require additional management.
Hard Launch
A hard launch involves switching all traffic to the new Shopify store at a defined point in time. This approach provides a clean transition and allows the business to immediately begin benefiting from the new platform, functionality, and customer experience.
However, a hard launch also carries greater risk. Any issues that emerge will affect the entire customer base from day one, making thorough testing, launch preparation, and stakeholder readiness even more important. For this reason, hard launches are often accompanied by intensive monitoring and dedicated support teams during the initial post-launch period.
Choosing the Right Approach
The most appropriate launch strategy will depend on factors such as business complexity, traffic volumes, integration requirements, and risk tolerance. High-growth brands with extensive integrations or international operations may benefit from a phased approach, while smaller stores with simpler requirements may find a traditional hard launch more practical. Regardless of the chosen approach, careful planning and robust testing remain the foundations of a successful migration.
