Moving a Store Between Shopify and WooCommerce: What Transfers, What Does Not, and How to Keep Your SEO

Should you move at all?

A migration is worth it when the platform itself is the limit, and not worth it when the problem would travel with you. Moving a live store costs weeks of attention, a short period of risk to orders and a temporary wobble in search. That is a fair price for removing a real ceiling. It is a bad price for a problem a new theme, a faster host or a cleaner plugin list would have solved.

I build on both platforms and I am not tied to either, so I start every migration call by trying to talk the owner out of it. If you have not settled the platform question itself, read Shopify vs WooCommerce in Israel first. If your doubt is whether the current store can be fixed where it stands, the rebuild or redesign tool takes a few minutes. The reasons I accept, and the ones I do not:

• A good reason to leave Shopify: you need checkout or pricing logic the platform does not allow, such as price lists by customer type, quotes, or a live connection to a system that has no app.
• A good reason to leave Shopify: the fee Shopify adds on each sale, on top of your payment provider, has grown with your revenue into a number worth acting on.
• A good reason to leave WooCommerce: nobody maintains the store. Updates are skipped, a plugin breaks every few months, and there is no developer you can call.
• A good reason to leave WooCommerce: the catalog and checkout are standard, and you would rather pay a monthly plan than think about servers.
• Not a reason: the site is slow. Speed is usually the theme, the images and the apps or plugins, and all three can be fixed without moving.
• Not a reason: the design looks dated. A redesign on the same platform keeps your addresses, your accounts and your order history where they are.
• Not a reason: sales are down. A new platform does not bring traffic, and the move itself costs some for a while.

What transfers and what does not

Data moves; behavior does not. Products, customers and orders are rows in a table, and both platforms can export and import them. The design, the apps or plugins and every automation are code written for one platform, and they are rebuilt on the other. The table at the top of this article lists each item for both directions.

Product images are the first surprise. A Shopify product export is a CSV file that does not contain the images themselves, and Shopify notes that images are created in the new store only if they remain viewable on a public address. WooCommerce works the same way from its side: its built-in product importer pulls each image from a directly accessible URL into the media library. In both directions the old store has to stay online and untouched until the import has finished and been checked.

Orders are the second. Shopify's own guide says to import products first, then customers, then historical orders, so that each order can be tied to its product and its customer. WooCommerce's guide warns of the same thing from the other side: the link between an order and its customer can break when customer IDs do not match, and payment details such as the transaction ID and the payment method do not come across. Past orders arrive as a record you can read and search. They are not a ledger you can refund from.

How the data is carried is a choice, not a given. Shopify lists copy and paste, CSV files, a migration app from its app store, a Shopify Partner, or a custom solution on its API. WooCommerce lists manual CSV work, free plugins for customers and orders, or a paid migration extension; its built-in CSV tool covers products. A small catalog with simple products goes through CSV. A store with variants, years of orders and customer accounts needs a tool or a script, and a person who checks the result line by line.

Customer passwords and accounts

Passwords do not move, in either direction, and no tool changes that. Shopify states that customer passwords cannot be migrated from another store with a CSV file, and that after the import you invite customers to create new ones. WooCommerce states that passwords cannot be exported from Shopify, so customers reset theirs after the move. The accounts themselves do move: name, email, addresses and, when the import is done in the right order, the order history attached to them.

When the destination is Shopify, the problem is smaller than it sounds. In Shopify's current customer accounts a customer enters an email address, receives a one-time six-digit code and signs in without a password. When the destination is WooCommerce, customers use the standard "lost your password" link, or you send them a reset link yourself.

What matters is that customers hear it from you before they hit it. Send one short email on launch day: the store has moved, your orders and addresses are waiting, here is how to sign in. A customer who meets "wrong password" with no explanation assumes the account is gone, and a returning customer who gives up at sign-in is the most expensive loss in the whole project. If you run a customer club, subscriptions or business accounts with their own prices, treat the accounts as a workstream of their own and test them with real customers before the switch.

Payments and invoices in Israel

The payment provider is not migrated. It is connected again, and sometimes it is replaced. Your agreement is with the provider and the acquirer, not with the store platform, so in the best case you keep the same contract and only install the connection on the new platform. Start with one question to your provider, in writing: do you support the platform I am moving to, for new stores, today? Shopify Payments is not available in Israel, so a Shopify store here takes cards through a third-party provider, and Shopify charges its own transaction fee on those sales. On WooCommerce the provider connects through a plugin and there is no platform fee.

If your provider does not support the destination, you are choosing a new one, and that has its own clock: an application, an approval and a test period that do not depend on your developer. Open it in the first week, not the last. The payment gateway picker narrows the options, the Israeli payment gateways comparison has the published terms, and connecting payments to a website in Israel explains how the parts fit together.

Three things around payments get forgotten. Saved cards and recurring charges are tokens held by the provider, not by the store; whether subscriptions continue without customers entering a card again depends on the provider, so ask before you promise anything. Invoices and receipts are issued by your invoicing system or by the provider, and that connection is set up again and tested with a real document. And the old documents stay where they were issued: check with your accountant that you keep access to them after the old store closes.

URLs and the 301 map

The addresses change, and the redirect map is what protects your rankings. The two platforms do not share a URL structure. A Shopify product lives under /products/, a WooCommerce product by default under /product/, and its categories under /product-category/. WooCommerce lets you choose the product base under Settings > Permalinks; Shopify's prefixes are fixed. So even a product that keeps its exact name gets a new address, and every link Google, a customer or another site holds to the old one breaks unless you redirect it.

The map is a spreadsheet with two columns: every old address, and the one new address that replaces it. Build the old column from more than the product list: the sitemap, the pages Search Console shows with clicks, the pages other sites link to, and the landing pages of your ad campaigns. Google's guidance for a site move is specific. Use permanent server-side redirects such as 301 or 308. Do not send many old addresses to one unrelated page such as the home page, because that can be treated as a soft 404. Redirect straight to the final address and avoid chains. Keep the redirects for at least a year.

Each platform has its own mechanics. In Shopify you create redirects in the admin or import the whole map as a CSV file, and Shopify advises setting them up before you transfer the domain. A Shopify redirect works only from an address that no longer loads a page, and standard plans allow up to 100,000 of them. In WooCommerce, redirects are handled by a plugin, which is what WooCommerce's own migration guide recommends, or at the server. Either way, test the map before launch: run the full list of old addresses and confirm each one lands on the right page in a single step.

Expect movement even when everything is done right. Google says to expect a temporary fluctuation in ranking during a move, and that for a medium-sized site it can take a few weeks or more until the new addresses replace the old ones in results. Plan the move for a quiet season, not for the month before your biggest sale.

Order of work and the freeze window

The new store is built next to the old one, and the old one keeps selling until the switch. The risky part is the gap between the last export and the moment the domain points to the new store: an order placed in that gap exists only in the old store. The freeze window closes that gap. It has two parts. A content freeze, a few days long, during which nobody adds products or changes prices in the old store. And a short order freeze at the switch itself, at your quietest hour, with the old store closed to new orders until the final data has moved.

The order I work in:

• Inventory. List everything the store does today: apps or plugins, automations, emails, shipping rules, coupons, tracking codes, feeds to price-comparison sites. What is not on the list is what breaks.
• Payments and invoicing. Confirm the provider, open the account or the new connection, and start the approval. It is the longest wait in the project and it is not in your hands.
• Build. Set up the new store on a temporary address: design, shipping, taxes, emails and each integration from the inventory.
• Trial import. Import products, then customers, then orders. Compare the counts with the old store and open a sample of each by hand, including a product with variants and a customer with a long history.
• Redirect map. Build it, load it, and test it against the list of old addresses.
• Test orders. Place real orders with a real card through every payment and shipping option, then refund them. Check the invoice, the emails and the stock count.
• Switch. Freeze the old store, import what changed since the trial, point the domain, switch on the redirects and send the customer email.
• Afterwards. Keep the old store reachable, but not selling, until open orders are delivered, returns are closed and you have exported everything you may need later.

Launch-day checks

Launch day is a checklist, not a celebration. Each item below has cost a store real money at some point, and all of them can be checked in the first hour:

• A real order, with a real card, on the live domain, from a phone. Then the refund.
• The invoice or receipt for that order: issued, numbered correctly, sent to the customer.
• Order emails to the customer and to you, in the right language and from the right address.
• Twenty old addresses from the map, including your best-selling products and the pages with the most search clicks: each lands on its new page in one step.
• An existing customer signing in the new way and seeing their past orders.
• Stock: the quantities match the old store at the moment of the freeze.
• Shipping rates and VAT on a cart that looks like your typical order.
• Tracking: analytics and ad pixels record the test purchase, once.
• Search Console: the new sitemap is submitted. Over the following weeks, watch the indexing report and the search queries.

What drives the cost and the timeline

The catalog is rarely what makes a migration big. The work sits in everything the old store does that is not data. I do not publish prices; every migration gets a fixed quote after a short call, and the project scope estimator shows which kind of project yours is before we talk. How I work on each side is on the Shopify in Israel and WooCommerce development pages. What moves a quote and a schedule up or down:

• Custom behavior: every app, plugin or piece of custom code in the old store has to be replaced, rebuilt or deliberately dropped. Moving to Shopify, each one has to fit inside what Shopify allows.
• Integrations: CRM, ERP, invoicing, shipping companies, marketplaces. Each is a connection that is set up again and tested.
• Data quality: duplicate customers, products without an SKU and variants entered three different ways are cleaned before the import, not after.
• History: how many years of orders you need in the new store, and whether an archive export is enough for the rest.
• Accounts: a customer club, subscriptions or business customers with their own prices.
• Design: carrying the current look across, or using the move to redesign. They are two different projects.
• The size of the redirect map and the number of languages.
• Third parties: the payment provider's approval and the domain transfer run on their own schedule.