How To Transfer Webhost to Shopify Safely (2026)

Knowing how to transfer web hosting to Shopify starts with one distinction: Shopify hosts your checkout and commerce back end (and the storefront too, unless you build headless). So the transfer moves structured commerce data rather than raw website files.

For ecommerce businesses, migration decisions can have performance and revenue implications. Deloitte found that a 0.1-second improvement in mobile site speed increased retail conversions by 8.4%; speed that helped tennis brand Slinger grow revenue by more than 40% in four months after migrating to Shopify.

The work falls into four phases: plan, migrate, protect SEO and test the new site, then connect your domain. This guide covers the eight steps within those phases. in order. You’ll learn how to prepare for the migration, test the new site before launch, and connect your domain when you’re ready to cut over.

Step 1: Choose Shopify hosting and a migration support model

The first step is to choose the right Shopify solution for your business. To support business continuity and minimize disruption for your shoppers, keep your current website active with your current web host while you prepare your Shopify store.

Shopify has native capabilities that can be configured and customized for your specific ecommerce requirements. That gives businesses flexibility to use Shopify as a complete commerce platform or extend it with the tools and integrations their stack requires. You can also explore our different pricing packages to compare available plans and capabilities.

Traditional web hosting companies price plans on server resources: shared hosting, VPS hosting, or a dedicated server. Shopify pricing is organized around platform plans and commerce capabilities, and web hosting is part of the platform. That changes what you compare when you choose your Shopify plan and migration approach.

What to look for with enterprise ecommerce hosting

Compare Shopify plans with your current hosting setup using the criteria that affect the migration and your long-term requirements:

• Total cost of ownership (TCO): Add platform fees, app and integration costs, development time, and the hosting costs you’ll no longer incur. Our guide to total cost of ownership for enterprise software has a working model.
• Peak-traffic capacity: Confirm how the platform handles your highest checkout volume without a new server or manual scaling.
• Integration and extensibility: Check which enterprise resource planning (ERP), order management systems (OMS), product information management (PIM), and customer relationship management (CRM) systems connect through prebuilt apps, and which need custom API work.
• Security and compliance: Confirm PCI DSS scope, SOC 2 reporting, and who owns patching once you leave your current hosting environment.
• International selling: Check support for the markets, currencies, and languages on your roadmap.
• Support model: Decide what level of support you need before, during, and after launch.

For a wider comparison framework, see how to choose an enterprise ecommerce platform.

Migration methods

Once you've chosen a plan, choose how the migration itself gets done. Shopify's migration guide lists several migration methods:

• Manual copy: Copy content from the existing site into Shopify. This approach is generally better suited to smaller amounts of content.
• CSV export and import: Export data from your current platform and import it through the Shopify admin. Some data types can't move this way.
• Migration app: Use Shopify's Store Migration app where it supports your source platform, or a third-party app such as Matrixify, to move products, customers, and orders in bulk.
• Shopify Partner: Hire a Partner agency to manage and complete the migration, including integrations, theme build, and cutover.
• Custom migration: Develop, or hire a Partner to develop, a custom migration using the Shopify APIs.

More complex migrations may require a combination of migration tools and additional support. Decide the method now, because it determines who owns each of the steps below.

Once you've signed up for Shopify, the next step is to prepare your existing website for migration.

Step 2: Inventory data, access, and migration prerequisites

Before you migrate anything, take the time to inventory the data, systems, and access your team will need. In most cases, the goal is to completely move off of your existing site so you no longer have to pay two hosting providers. Set aside enough time to review and list all your critical website data, processes, promotions, and integrations. This inventory will help you scope the migration, assign ownership, and validate what moves successfully later.

Before touching data, confirm you have the access and sign-offs the migration needs. Work through this prerequisite checklist:

• Access: Admin logins for the current hosting account, content management system (CMS), domain registrar, and DNS provider 
• Ownership: Confirmation of who legally owns the domain name registration and the hosting contract, and when each renews
• Backups: A full export of the current site, including database files and media, stored outside the old host 
• Analytics: Baseline traffic, conversion, and revenue figures, plus a list of every pixel and tag on the site 
• Integrations: A list of every connected system, its data flow, and its owner 
• Domain and DNS: Current DNS records, TTL values, transfer-lock status, and the registrar account email 
• Rollback: A written plan for reverting DNS to the previous host if launch fails 
• Launch stakeholders: Named approvers for data, SEO, integrations, and go-live, with dates they're available

Keep this checklist with your migration plan so you can use it again during testing, launch readiness, and migration scoping.

Review and document your website data

Every ecommerce site is unique, so thoroughly review everything you want to transfer to Shopify. Document each asset you need to migrate and how it will move to Shopify. Examples of the types of data that you might want to transfer include:

• Products
• Customers
• Historical orders (orders that have been fulfilled)
• Gift cards
• Certificates
• Store credits
• Discount codes
• Blogs
• Pages (shipping policy, contact, and other webpages)
• Product reviews

Not every asset moves the same way. Map each one to the Shopify-supported path before you export anything. Products, customers, and orders can be imported through the CSV import tools or a migration app.

Historical orders, gift cards, certificates, and store credits need a migration app or a custom API-based migration (using the Order, Transaction, and GiftCard APIs). They can't be recreated from a product CSV. Blog posts and pages move through a migration app or are recreated in the Shopify admin. Product reviews depend on the review app you choose, so check its import format first.

Record the path, the owner, and the record count for each asset. You’ll use those counts later to validate the migration after import.

Prepare product data in a CSV file

Once you’ve identified your datasets, you'll need to download them. Shopify uses CSV files to import products into your new store. Review our instructions for downloading and formatting your CSV file. You can also review our guidance on how to open and edit a CSV file.

Source platforms export in their own column layout, which won't match Shopify's. Adobe Commerce and WooCommerce exports, for example, list attributes and variants differently from the Shopify product CSV.

Export a representative sample of products first. Map each source column to its Shopify equivalent. Pay attention to variants, option names, image URLs, and inventory quantities per location.

Then run a test import into your Shopify store and compare a product page side by side with the original. Fix the mapping before you export the full catalog. Migration apps can handle this mapping for common platforms, which is one reason enterprise teams may use them for large catalogs.

Prepare promotions for migration

Document the active promotions and discount codes on your current site, including rules, expiration, availability conditions, and channels. Decide which promotions you want to transfer directly into Shopify, and which to discontinue. If you are making any changes, plan how you’ll communicate them to shoppers after launch.

Step 3: Plan your storefront and theme

Shopify combines web hosting with commerce capabilities. After you've got your data ready to migrate, it's time to plan your new storefront and select the Shopify theme that will work best for you. Review your current storefront and channel requirements, as well as the tools you need to meet them with Shopify.

Planning your new storefront is also a chance to address limitations in your current store. Depending on your plan and support model, Shopify Support, a Shopify Partner, or our enterprise team can help you with this part of the migration process.

There are two main approaches to building an online storefront on Shopify. This table compares them on the decisions that affect your migration:

Choose an integrated, headed storefront

With a headed approach, the front end and back end of the ecommerce website stay tightly integrated.

With a headed solution from Shopify, back-end tools are preintegrated into the front end. This is a theme-based way to build a fully hosted store to manage and grow a business. Shopify's theme architecture makes it possible for businesses to build pages, adjust the design, and manage the site.

Choose a headless storefront

This approach requires more maintenance and support, especially from technical teams. A headless storefront is where the front end and back end of an ecommerce website are detached from each other, providing more flexibility. Our guide to the benefits of headless commerce covers when the trade-off is worth it. There are three primary ways you can set up a headless storefront with Shopify.

1. Storefront API: You design, build, and host your own front end. Then you use Shopify's GraphQL Storefront API to build custom headless storefront applications.
   
   
2. Hydrogen: Hydrogen is Shopify's React-based framework for headless storefronts. Hydrogen is powered by the Storefront API and built on Hydrogen React, the underlying component library that handles Storefront API integration.
   
   
3. Host a Hydrogen front end on Shopify Oxygen: If you are building your front end with Hydrogen, you can host it on Oxygen, Shopify's hosting architecture optimized for headless ecommerce.

When you’re deciding which is right for your business, focus on the requirements that will affect the migration and ongoing ownership:

• What problems are you trying to solve with your website? If your current hosting solution isn't working well, take note of the problems you want to solve by migrating to Shopify. Also consider your budget and timeline, and whether each approach fits those constraints.
  
  
• What is the technological impact of each approach? Consider how each approach will affect your business. Make sure you've chosen a solution that is scalable, secure, and fast. How would changes to your current technology affect the approach?
  
  
• Who will support the website? Identify who will be responsible for operating the online business, who will support the technology, and what skills they have.

Choose the approach before migration work advances so the team can plan for the right level of development and testing. With a headless approach, the migration process will include additional steps, such as architecture design, the creation of a code repository, and user acceptance testing (UAT).

Step 4: Plan plugins, add-ons, and integrations

Once you've identified and collected all the data you want to transfer to Shopify, map the capabilities your new website needs and the systems it must connect to. Plan those integrations before launch so ownership, requirements, and testing are clear.

Map current functionality and required capabilities

To plan the functionality of your new site, map out what plugins, add-ons, and integrations you will need on Shopify. Review your website's existing functionality and identify the capabilities you need to preserve, replace, or add during the migration. 

You can browse our business tools and the Shopify App Store to explore ways to add and extend your website's functionality.

Define integration requirements and owners

Your ecommerce website may also integrate with external tools that help you manage your business. Document which existing integrations need to carry over to Shopify and any new integrations required for the new site. Shopify offers several options for website integrations, including:

• Prebuilt: Visit the Shopify App Store for vendor-built apps that integrate with Shopify.
• Custom: Build an integration using the GraphQL Admin API or webhooks. Our ecommerce API guide explains which API fits each use case.
• Integration partners: You can work with Plus Integration Partners such as Celigo or VL OMNI.
• Integration platforms as a service (iPaaS): Use middleware platforms such as Boomi, Jitterbit, or MuleSoft.

In Flexera's 2026 “State of the Cloud” report, enterprise respondents named understanding app dependencies (54%), assessing on-premises vs. cloud costs (45%), assessing technical feasibility (44%), and migrating the app and data (32%) as their biggest hurdles when moving workloads.

Give each integration a named owner before build starts. The owner documents the data flow in both directions, and the trigger (real time, scheduled, or manual). They should also define the failure behavior and sign off on testing.

For each integration, define test cases based on its role, such as a normal order, refund, inventory update, or failed sync. Run them in a development store first. Then run them again in the production store with live credentials before launch. Use dedicated test SKUs and a documented reversal process so testing doesn't trigger real fulfillment.

Document the owner, data flow, failure behavior, and test plan for each integration before you finalize the transfer process. 

If you have any questions about integrating your new Shopify website, reach out to Shopify Support.

Step 5: Import ecommerce data and content into Shopify

A Shopify migration is not a traditional hosting migration. For example, moving a WordPress site between two WordPress hosting providers means downloading website files with an FTP client and exporting an SQL file. You then create a new database on the new host's server and upload everything to the website's root directory.

None of that applies here. Shopify hosts the web server and database, so there are no website files to upload and no new server to configure.

What moves instead is structured ecommerce data (like products, customers, and orders), content and media (blogs and images), your theme, your apps, and your integrations. Each has its own import path, which is why the inventory you created in Step 2 matters here.

Once you've got all your data exported, and the new store has all the add-ons and integrations you need, you're ready to start importing. Review our instructions for using CSV files to import your products into your new Shopify website.

Once you've completed the import, check that everything transferred correctly. Check each of your product details to make sure product descriptions, images, variants, and meta descriptions are all correct. Compare record counts against the inventory you built in Step 2.

If you don't have them already, consider creating product collections to organize your products into categories and make them easier for your shoppers to find. You can add collections to drop-down menus and create links to collections on your storefront.

This is also a good time to review Shopify's product inventory andtransfers to keep track of the products that you have available in your store. You can browse Shopify's inventory apps to learn what additional inventory management resources are available.

Step 6: Protect SEO during migration

When you transfer your website hosting to Shopify, your new website will run on a platform designed with search engine optimization (SEO) in mind. Shopify's platform automatically generates several SEO elements, including tags and sitemaps.

During migration, you’ll still need to protect the search visibility your existing site has built. Once your data is imported and functionality is configured, review the following before launch.

Review new URL structure and set up redirects

With Shopify, your new website's URL structure will follow standard patterns that are preoptimized for SEO. (Other options allow for greater URL control, such as our headless ecommerce solutions.) Start by creating a list of all URLs on your current site. Then prioritize these URLs based on their existing value to your SEO traffic and strategy.

If the URL is different on your new Shopify site, add the corresponding redirect URL on Shopify. You will want to create a URL structure that contains your desired keywords. Create one-to-one redirects and use 301 permanent redirect logic.

A 301 tells search engines the move is permanent, so ranking signals pass to the new URL. Build the redirect map in a spreadsheet with the old URL, the new URL, and the source of each old URL's value. That source could be organic traffic, backlinks, or paid campaigns.

Redirect each old URL to the single closest equivalent page, not to the homepage. Avoid chains, where an old URL redirects to another old URL before reaching the destination. Include image URLs and PDFs that have backlinks, not only pages.

Shopify supports bulk upload of redirects through a CSV in the admin. Keep high-value redirects in place for the long term, particularly URLs with backlinks or paid-campaign traffic, because those links don't expire. Before launch, test the top 100 URLs by traffic and every URL with external backlinks.

Update meta titles and meta descriptions

As part of the migration, review your meta titles and meta descriptions to make sure they transfer correctly or are intentionally updated. Make sure your titles and descriptions contain your target keywords. For more information, visit Shopify's pages for homepage SEO metadata and adding keywords to metadata and on-page content.

Check page speed

The speed at which your website loads affects both SEO rankings and how likely your shoppers are to make a purchase. Shopify's server response time is up to 3.9 times faster than other commerce platforms, and 2.8 times faster on average. For additional performance guidance, review Google's documentation and Shopify's performance resources. The Web Performance dashboard in the Shopify admin reports Core Web Vitals from real shopper sessions, so you can compare post-launch performance against the baseline you captured before migration.

Review sitemaps, robots.txt, and structured data

With Shopify, you get many features that help with SEO, including an automatically generated sitemap.xml file that is updated whenever new pages and images are added to a store. After your site launches, verify the new property in Google Search Console and submit your sitemap.xml file to Google Search Console if it isn't already submitted. If you need granular control over how your site is crawled, Shopify automatically creates a robots.txt at the root directory of a Shopify store's primary domain that you can customize.

Finally, review your structured data markup to help search engines understand your site's content, such as information about products, recipes, books, and more. Many Shopify themes already include Schema.org for product data in their templates.

Monitor SEO performance after launch

SEO performance can change after a hosting migration. You can review Shopify's SEO apps to see what might be helpful after your website launches.

Set a monitoring cadence for the first 90 days and check these items against the baseline you captured in Step 2:

• Indexing: In Google Search Console, watch the pages report for a drop in indexed pages and a rise in "not found" or "redirect error" URLs.
• Crawl errors: Export 404s weekly and add redirects for any old URL that still receives traffic.
• Organic traffic and rankings: Compare sessions and conversions for your top landing pages and keyword positions for your priority terms, week over week.
• Google Core Web Vitals: Track the Web Performance dashboard for regressions after theme or app changes.
• Backlinks: Confirm that the most-linked old URLs resolve with a single 301 to a live page.
• Sitemap status: Confirm the new sitemap is processed and its URL count matches the live site.

If you need help with post-migration SEO, Shopify's Professional Services can help you with the SEO steps you need to take when transferring your web host to Shopify.

Step 7: Test your website before launch

Before transferring your domain and launching, thoroughly test and review your new website.

Test checkout, data, integrations, and redirects

Run the launch-readiness checklist below in the week before cutover. Do it on the production store, not a development or staging site. Each item needs a named owner and a pass or fail result:

• Checkout: Place test orders for each payment method, shipping zone, and tax scenario that applies to your business. Include other checkout scenarios such as discount codes, gift cards, refunds, or partial fulfillment.
• Store setup: Confirm shipping rates, tax settings, payment provider, and staff permissions are configured, and review the customer notification emails each test order sends.
• Data: Spot-check a sample of each data type against the source platform, and confirm total counts match the Step 2 inventory.
• Integrations: Run each integration's test cases end to end with live credentials, including the relevant failure scenarios defined in Step 4. 
• Redirects: Crawl the redirect map and confirm every old URL returns a single 301 to a live page. 
• Pixels and analytics: Confirm each pixel fires at every stage of a test order, from page view through to purchase (setup guidance is in the sections below). 
• Domain and DNS: Confirm the domain is connected and DNS TTL values are lowered. If you're transferring, confirm the registrar transfer lock is off. 
• Rollback: Confirm the previous host is still live and the DNS revert steps are documented, so the team can revert if the launch needs to be rolled back. 
• Communications: Confirm launch timing with every team that touches an order, from support to fulfillment.

Configure analytics pixels

If you have existing tools for reporting, analytics, or retargeting, make sure their pixels are properly configured on your new Shopify site. Shopify supports integrations with many common analytics providers, including:

• Google Analytics 4
• Google Tag Manager
• Meta Pixel
• Google Ads conversion tracking
• Bing Ads conversion tracking

Many of these apps already have pixel configuration built in when you install their prebuilt integration via Shopify. These apps use the Shopify Web Pixels API, which provides secure, reliable pixels. You first need to install the app, and then go through the setup process to configure a pixel.

Configure custom pixels

If you need to track and manage custom events, you can add a custom pixel from the Customer events page in your Shopify admin (go to Settings > Customer events). Examples include clicking a link or adding a product to a cart. Each custom pixel is added, connected, and disconnected from that page.

Custom pixels are written in JavaScript and run in a sandboxed environment, so implementation is developer work. Have a developer write the pixel and subscribe it to the right customer events. They should also verify it in a test order. If you're migrating tags from a tag manager on your previous host, budget time to rebuild them rather than copying the scripts across.

Step 8: Connect or transfer your domain name

Once everything is set up, migrated, optimized, and tested, it's time to point your domain name at the new website. There are three separate actions to clarify here:

• Connecting a domain points your existing domain at Shopify by changing domain name system (DNS) settings at your current DNS provider. Your domain registrar doesn't change.
• Changing DNS records is the mechanism behind connecting. You edit the A, AAAA, and www CNAME records so they resolve to Shopify, while keeping MX and TXT records for email and verification in place.
• Transferring registrar ownership moves the domain registration itself to Shopify, so domain management, renewals, and DNS all live in the Shopify admin. This is the domain transfer. It includes a required one-year renewal and can take up to 20 days, though Shopify lists a five-day maximum for many common extensions, including .com, .net, and .org.

You can connect without transferring, for example to keep the registrar that holds your wider domain portfolio. Connecting is the step that points your domain to your Shopify site; transferring the domain is optional and can happen separately. If you do transfer, connect first. Below is an overview of the steps you'll need to take.

Connect your domain to Shopify

To avoid any interruption in service, you need to connect your domain to Shopify. If you don't connect your domain before you transfer it, then visitors to your domain might experience connection errors during the transfer process.

Review Shopify's current DNS record requirements before you edit anything. At the time of writing, they cover an A record, an AAAA record for IPv6, and a www CNAME record, and the values can change. Set the records exactly as documented, and keep any existing MX records for email in place. If the domain uses custom or external name servers, make sure you’re editing the DNS records with the provider that manages your domain’s authoritative DNS. Otherwise the changes you make with your domain provider might not take effect.

Shopify's requirements say the default time to live (TTL) works for connecting a domain. For a high-traffic cutover with a rollback plan, lowering the TTL in advance to the shortest value your DNS provider allows is still worth doing (Cloudflare, for example, defaults to 300 seconds, or five minutes). A record's TTL controls how long resolvers cache it, which affects how long an update takes to reach shoppers. A low TTL means the new DNS settings propagate quickly and a rollback is equally fast.

Lowering the TTL is itself a record change, and resolvers won't see it until their existing cached copy expires. So make the change at least as far ahead of cutover as the current TTL value. If the A record has a 24-hour TTL, lower it at least 24 hours before launch. By launch, every cached copy carrying the old 24-hour TTL will have expired, and resolvers will pick up the new address within the shorter window.

Raise the TTL again once the launch is stable. Once all the steps have been taken to change the records, propagating the new site across the internet can take up to 48 hours to complete. Make sure that the connection process is complete before you begin the transfer.

Check domain eligibility and transfer locks

You can check whether your domain is eligible for transfer inside of your new Shopify account. Eligibility depends on the extension: .co.uk, .de, and .jp are among those that can't be transferred, while .ca can. Check the current list in the Help Center. Only apex domains such as johns-apparel.com can be transferred to Shopify, not subdomains such as shoes.johns-apparel.com.

Once the apex domain is transferred into Shopify, you can recreate any subdomains you had in use.

Registrars apply a transfer lock to prevent unauthorized moves. Under ICANN's Transfer Policy, a registrar can deny a transfer within 60 days of registration or a previous transfer. It must also apply a 60-day lock after a change of registrant details, unless you opt out at the time of the change. This applies to generic top-level domains such as .com; country-code domains follow their own registry rules.

Outside those windows, log in to your registrar account and disable the lock (labeled "transfer lock," "registrar lock," or "domain lock," depending on the provider).

Then request the AuthInfo code, also called the EPP code or authorization code.

Registrars send it to the admin contact email on the domain. That address must be current, and it must not be hosted on the domain you're transferring. Request it when you're ready to start, because codes can expire, and keep the domain unlocked until the transfer shows as complete in your Shopify admin.

Before you start, save a copy of every custom DNS record on the domain, including MX and TXT records. Shopify doesn't copy those records during a transfer, so you'll recreate them in the admin afterward.

Complete the domain transfer to Shopify

After you prepare your domain for transfer, you can start the domain transfer process from your Shopify admin. Follow Shopify’s domain transfer instructions. A domain transfer can involve multiple providers, authorization codes, and time-sensitive emails, so follow each step closely. Contact Shopify Support if you need help during the transfer.

After the transfer is complete, Shopify sends a confirmation email. To update any settings or configure subdomains, visit the Domains page in your Shopify account. Your website is already live on the connected domain; the completed transfer moves its management to Shopify.

Plan your next migration step with Shopify

Bring your migration inventory, integration map, redirect map, and launch-readiness checklist into a scoping conversation with a Shopify enterprise account executive or solution engineer. The conversation works through catalog size, order history, integration count, storefront approach, and target launch date, then matches the migration to one of three support models:

• Self-serve: Your team runs the migration using the Help Center, the migration apps, and Shopify Support. This model keeps migration ownership with your internal team.
• Partner-led: A Shopify Partner agency scopes and delivers the migration, including integrations, theme build, and cutover. Our guide to choosing a Shopify migration partner covers engagement models and the questions to ask before you sign.
• Professional Services: Shopify's Professional Services team works alongside yours or your partner's, with launch consultants covering discovery, migration planning, integration, and post-launch support for the most complex builds.

Whichever model fits, the scoping conversation ends with clear ownership, key dates, support needs, and the launch risks that still need to be addressed. Naming an owner for every integration and redirect beforehand makes that list accurate from the start.