Migrating from Shoper - one of the biggest hosted e-commerce platforms in Poland - to WooCommerce is a subject that usually comes back at one particular moment: the store has grown, sales are rising, and the SaaS bill is rising with them. At the start, the subscription plus the transaction fees looked like a reasonable price for convenience - someone else runs the server, keeps it updated, nothing needs configuring. But at higher turnover that same model starts working against you: the more you sell, the more you pay the platform for the right to sell at all.
The biggest worry about a migration like this is usually not the money but the fear of losing what you have worked on for years: your Google rankings, order history, customer accounts. And rightly so - a badly executed migration can blow all of that up. Done well, it touches nothing that works and only changes the foundation the store stands on.
Below I split it into two parts: what the migration process looks like step by step, and how to work out whether moving to your own store is worth it at all.
What does the migration process from Shoper to WooCommerce look like?
A migration is not a five-minute “export-import” - it is an ordered process where every step protects what you already have. In practice it breaks into several stages:
1. Exporting data from the Shoper store. Products (names, descriptions, images, prices, variants, stock levels), customers (accounts, order history) and the orders themselves. Some of it Shoper lets you export directly, some has to be pulled via the API or filled in by hand - it depends how unusually the store is configured.
2. Mapping categories and attributes. A Shoper category structure rarely transfers one to one to WooCommerce - it has to be remapped so that a customer arriving from an old link lands in the same place, just on the new platform. The same goes for product attributes (size, colour, variant) - they have to keep their logic so filters and variants work exactly as before.
3. Import into WooCommerce and store configuration. Products, customers and orders go into the new structure, and alongside that I configure what was “built in” on Shoper: payments, shipping, taxes, transactional email templates.
4. 301 redirects from the old URLs. This is the step that most often decides whether the migration keeps your Google traffic or loses it. Every old product, category and page address has to redirect to its new counterpart - without it, Google and customers land on nothing (a 404 error) and the search position you built starts falling apart.
5. Testing on a staging environment. The entire buying process - add to cart, payment, confirmation email - gets tested before the new store replaces the old one, not on live customer traffic.
6. Keeping the SEO. Beyond the 301 redirects there is the meta data to watch, the sitemap, and submitting the changes in Google Search Console so the search engine notices the new setup as fast as possible without treating it as a completely different site.
What helps: before the migration, make yourself a full list of the current store’s URLs (products, categories, pages) - that is the basis for the 301 redirect map. The more accurate the list at the start, the smaller the risk that something gets lost along the way.
I run this whole process on a staging environment in parallel with the live Shoper store - customers keep buying without interruption, and the switch to the new setup only happens once everything has been checked and works.
SaaS fees and subscriptions versus the cost of your own store
This is the heart of the “is it even worth it” question. Shoper’s model - like most store SaaS platforms - rests on two recurring bills: a monthly subscription for using the platform and, on many plans and with some payment methods, a fee calculated on the value of your sales. It is a convenient model at the start, because the cost grows slowly along with a small store. The problem shows up when the store stops being small - a transaction fee grows in proportion to turnover, so the better the store does, the more someone else earns from it.
WooCommerce works on a completely different principle. The plugin itself is free, and the costs that remain are:
- Hosting - a fixed monthly cost, independent of how much you sold.
- Any paid plugins - one-off or on an annual licence, not a percentage of turnover.
- No commission on sales - what you sell stays with you in full (leaving aside the payment gateway’s own fee, which is identical whatever the platform).
| Shoper (SaaS) | WooCommerce (your own store) | |
|---|---|---|
| Cost model | monthly subscription + transaction fees | hosting + any paid plugins, no commission on sales |
| Dependence on turnover | the bill grows with sales | the bill is fixed, independent of turnover |
| Who manages the server | the platform provider | you (or your technical support) |
| Flexibility | within the platform’s features | full - you have access to all the code |
| Maintenance | included in the subscription | requires hosting and technical support |
To be fair: WooCommerce is not “free” in the sense of zero cost - you pay for hosting and for someone (you or a contractor) keeping updates and security under control. But as turnover grows, that fixed cost very quickly comes out cheaper than a percentage handed over on every transaction. Where those two cost curves cross is different for every store - it depends on turnover, margin and how many transactions go through payment methods that carry a fee.
I go wider into the differences between the platforms (not only Shoper, but Shopify too) in the piece on WooCommerce, Shopify or Shoper - which one to pick - it also covers who SaaS still makes sense for and when your own store starts to win.
What helps: before you decide on a migration, work out your actual cost on Shoper for the last 12 months - subscription plus all fees - and set it against the estimated cost of hosting and maintaining WooCommerce. That single number usually settles the discussion faster than any argument about “control” or “flexibility”.
How long does such a migration take and when is a good moment?
The timeline depends above all on the number of products and how unusually the current Shoper store is configured - the more variants, attributes and integrations, the longer the mapping and testing take. That is why I do not give a fixed deadline without looking inside a specific store - the same as with price, I would rather say honestly “this is how long it will take” after seeing the scope than throw out a number from thin air.
A good moment for a migration is usually outside the sales peak - not the week before Black Friday or in the middle of the Christmas season. Not because a migration is risky in itself (I run the whole process on staging, so the old store works without interruption right up to the switch), but because every change deserves a calm period of observation afterwards - checking that orders come in properly, that transactional emails look right, that Google Search Console is not reporting indexing errors.
What happens to customer accounts and order history?
This question comes back almost every time, and rightly so - customers who created an account in your store should not feel any difference after the migration. In practice that means:
- Customer accounts move across with their basic data (email, address, invoicing details), though passwords usually have to be set again for security reasons - that is standard when changing platform, not a migration fault.
- Order history is carried over, so a customer logging in after the migration still sees what they bought from you and when.
- Loyalty programmes or standing discounts need checking separately - if you used mechanisms like that on Shoper, they have to be recreated in WooCommerce (there are dedicated plugins for this), because they do not transfer automatically with the rest of the data.
The more precisely you describe at the start which extra mechanisms your Shoper store used, the smaller the risk that something gets missed in the quote and only surfaces mid-project.
Will the migration hurt my Google rankings?
Short answer: no, if it is done properly. The SEO risk in a migration does not come from changing platform but from neglect in the process - missing 301 redirects, URLs changed for no reason, lost meta descriptions and titles, or content that ranked well simply disappearing. All of those can be addressed if they are planned from the start rather than bolted on afterwards.
That is why staging tests and a complete redirect map are not a formality - they are exactly the part of the process that decides whether search traffic stays where it was after the migration, or has to be rebuilt from zero over the following months.
Let us check together whether a migration pays off for you
If you are thinking about moving from Shoper to WooCommerce, you do not have to guess whether it is worth it. Send me the address of your current store, tell me roughly how many products you have and what your turnover is - I will send back a written quote within 24 hours: exactly what the migration covers in your case, what it costs and how long the switch realistically takes with no break in sales.
The full scope of this service - including the guarantee on keeping your Google rankings - is described on the WooCommerce migration page.
Frequently asked questions
How long does a Shoper to WooCommerce migration take? It depends above all on the number of products, variants and integrations - a catalogue of a hundred simple products is a different job from several thousand SKUs with filters and a connected warehouse. I do not throw out a deadline: I give it together with the written quote, after looking inside the specific store.
Will customers have to create their accounts again? No, accounts move across along with their data and order history. Passwords usually have to be set again, because they are stored encrypted and do not transfer between platforms - that is standard when changing engine, and the customer simply gets a link to set a new password.
What about product reviews from the old store? Reviews can be moved, but that is a separate step - they do not come across automatically with the product export. Tell me at the start that you have them and where they are collected (Shoper’s built-in mechanism or an external service), and I will include it in the scope. External review systems are usually just reconnected to WooCommerce and stay where they are.
Do I have to change domain when moving to WooCommerce? No, the domain stays yours - the only thing that changes is which server it points to. That is in fact the more convenient option for SEO, because Google sees the same store address, and the change in page structure is handled by the 301 redirects.
On Shopify, PrestaShop or a local SaaS and thinking about moving? I run migrations to WooCommerce without losing search positions and without pausing sales. Describe the store and you will get a quote with a date.