Seminar at SoftUni Creative
Last updated on
Have you ever asked your store platform for something quite specific and heard “that’s not supported”?
Prices for business customers. A link to your warehouse system. A calculator on the product page.
One “no” is an inconvenience. When they pile up, the store starts deciding how the business works, instead of the other way round.
Changing platforms is a serious decision. It touches products, customers, orders, integrations and your rankings in Google. Below is how to judge whether it is worth it, what carries over, and what to ask of whoever runs the migration, so you do not lose orders along the way.
The short version
- A move is worth it when the platform limits sales or day-to-day operations. If the only problem is how the store looks, a redesign does not need a migration.
- Hosted platforms such as Shopify take care of hosting and updates. In exchange, features and access to your data depend on the vendor.
- With WooCommerce, the code and the database are yours. So is the responsibility for maintenance and security.
- Products, categories, customers, orders and coupons usually carry over. Customer passwords often do not, and that is worth planning for.
- The most expensive mistake is migrating without a complete map of 301 redirects. Google recommends keeping them for at least a year.
- Temporary ranking swings are normal. For a medium-sized site, Google says it can take a few weeks or more before the new URLs replace the old ones.
When changing platforms is worth it
Most owners open the conversation with “the store looks dated”. That is rarely a good enough reason to migrate.
A migration is justified when the problem sits in the foundation of the store. In our experience, it is almost always one of the signals below.
| Signal | What you see in practice | Does a migration solve it? |
|---|---|---|
| Features the platform does not allow | Customer-specific prices, B2B ordering, calculators, unusual discounts | Yes, if the new platform supports them without workarounds |
| Missing integrations | Orders are retyped by hand into the ERP or warehouse system | Yes, if that system can exchange data |
| Fees that grow with revenue | A percentage of sales, a pricier plan for every new feature, paid apps | It depends. Compare the total cost over three years, not the monthly plan |
| Piled-up extensions | Every update breaks something and nobody knows what each module does | Yes, though sometimes a clean rebuild on the same platform is enough |
| End-of-life or hard upgrades | A major version upgrade that is almost a rebuild, fewer developers available | Often yes, if you are rebuilding anyway |
| Only the look | The store looks dated but works | No. That is a redesign |
If you only recognise yourself in the last row, you probably need a redesign, not a migration. If you are in the first rows, the platform conversation is worth having.
Hosted platform or a store you own
This is where many businesses go wrong: they compare the monthly fee and stop there.
The difference between a hosted platform and WooCommerce runs deeper. It is about ownership and responsibility.
| Criterion | Hosted platform (for example Shopify) | Self-hosted store (WooCommerce) |
|---|---|---|
| Hosting and updates | Handled by the vendor | Handled by you or your maintenance partner |
| Features | What the platform and its apps offer | Whatever can be developed |
| Data and code | With the vendor, available through export | On your server, fully yours |
| Costs | Monthly plan, sometimes a share of revenue, paid apps | Hosting, maintenance, development, paid extensions |
| Main risk | Dependence on the vendor’s decisions | Dependence on the quality of maintenance |
A hosted platform is a sensible choice for a store that fits its standard features. Hosting and updates are part of the price, and your team does not have to think about them.
WooCommerce wins when the store needs things that are not standard: its own pricing logic, integrations, a specific catalog structure.
According to W3Techs, as of November 2026 WooCommerce accounts for 47.3% of the e-commerce systems in its surveys. In practice, that means a wide choice of extensions and developers, and integrations for most payment providers and couriers.
If you are on Magento or OpenCart
Magento (Adobe Commerce) and OpenCart are self-hosted, like WooCommerce. So the question is not ownership but everything around the store.
The signals we see most often: extensions from different developers that are hard to update together, version upgrades that require new versions of every module, and the growing cost of developers who can work on the platform.
If none of that applies and the store sells, there is no need to rush.
Worth doing: Before you decide, ask your current platform for a full export of products, customers and orders. If the export is incomplete or difficult, it is better to find out now than halfway through the project.
What carries over and what does not
| Data | Does it carry over? | What to watch |
|---|---|---|
| Products, variants, categories | Yes | Attributes and variants are often structured differently and need cleaning up |
| Images | Yes | Keep file names and alt text where you can |
| Customer accounts | Yes | Passwords often cannot be migrated. Customers set a new one on first login |
| Order history | Yes | It matters for reports, repeat purchases and returns |
| Coupons and reviews | Usually | Check that reviews stay attached to the right products |
| Blog and pages | Yes | Internal links have to point to the new URLs |
| URLs | They change | Every old URL needs a 301 redirect |
| Integrations | No, they are rebuilt | Payments, couriers, ERP or warehouse, invoicing |
Integrations are the part most often underestimated in quotes. They are also where a migration done well shows.
The clearest example from our work is shop.bvl.bg, the official illycaffè store in Bulgaria. When it moved from Magento to WooCommerce in 2023, the ERP sync was part of the scope from day one, and the store kept running reliably after the switch.
SEO during a migration: where rankings get lost
A platform change almost always changes URLs. Categories get a new structure, product pages a new URL format.
To Google, that is a site move. In its documentation on site moves, Google says that for a medium-sized site it can take a few weeks or more before the search engine starts showing the new URLs instead of the old ones. Ranking swings during that time are normal.
The trouble starts when old URLs lead to a 404 error page. The history those pages built up is then lost.
For any migration, it is worth insisting on:
- A complete list of old URLs from the sitemap, Search Console and a crawl of the site, not only the products in the database.
- A 301 redirect for every URL to the closest new page, not a blanket redirect to the home page.
- Titles, meta descriptions and copy kept on the pages that bring traffic.
- A check in Search Console during the first weeks after launch.
- Redirects kept for at least a year, as Google recommends.
One change at a time, or everything at once?
Google recommends making changes one at a time: first the platform, then the design. That way, if rankings drop, you can see which change caused it.
With a platform change, that is rarely realistic. The old theme cannot be carried over, and rebuilding the same design on a new platform only to replace it a few months later usually means paying twice.
So when you migrate with a new design, reduce the other variables. Keep the domain, keep URLs where possible, and do not change the range or the prices at the same time.
Be careful: Do not plan the launch of the new store right before your busiest season. If Black Friday or Christmas brings a large share of your revenue, the new store should be live for at least a few weeks before that, so there is time for fixes.
How a migration runs
| Stage | What happens | What we need from you |
|---|---|---|
| Audit of the old store | Data, URLs, integrations, traffic by page | Access to the platform, Search Console and GA4 |
| Structure and design | Categories, key pages, the new path to checkout | Feedback within the agreed time |
| Development and integrations | Payments, couriers, ERP, automations | Contracts with payment and delivery providers, access to the ERP |
| Data migration | Test migration, checks, final migration | A check of a sample of products and orders |
| Testing | Test orders, payments, emails, redirects | Test orders from your side |
| Launch and monitoring | Switch-over, Search Console, fixes | Feedback from your team and customers |
The test migration is the step most often skipped. It surfaces data problems while there is still time to fix them: duplicate SKUs, variants without a price, images without a product.
The platform is not the goal in itself. Two years after its migration, the redesign of shop.bvl.bg on the same platform brought 52.8% more orders with almost the same traffic. The migration made that improvement possible without another move.
Questions to ask whoever runs the migration
- How will you build the list of old URLs, and will you show it to me before launch?
- Will there be a test migration, and who checks the result?
- What happens to customer accounts and passwords?
- How do we keep selling on the day of the switch?
- Who is responsible for the integrations after launch?
- What do we get at handover: access, code, documentation?
If the answer is something general like “we’ll take care of SEO”, ask for a specific example from a previous migration.
Frequently asked questions
Will we lose our Google rankings when we change platforms?
Temporary swings are normal. Google says that for a medium-sized site it can take a few weeks before the new URLs replace the old ones. Lasting losses usually come from missing redirects, deleted copy or a new structure without a plan.
Can we migrate customers and order history?
Usually yes. Accounts, addresses and order history carry over. Passwords depend on how the old platform stores them. Often customers set a new password on first login, so it is worth warning them by email.
How long does a migration take?
For a medium-sized store, roughly as long as building a new store, plus monitoring after launch. A large catalog, many integrations or messy data make it longer.
Can the store keep selling during the migration?
Yes. The new store is built in parallel on a test address. The old one sells until the day of the switch, and orders from the last days are carried over in the final migration.
When is it better to stay on Shopify or another hosted platform?
When the standard features cover your sales, you do not need complex integrations, and you prefer the vendor to handle hosting and updates. A move makes sense when the platform starts limiting the business.
Do we have to change the design as part of the migration?
Almost always, because the old platform’s theme cannot be carried over. It is worth limiting other changes during the same period: the domain, the range and the prices.
Key takeaways
- Change platforms because of limits on sales or operations, not because of how the store looks.
- Compare ownership and total cost over several years, not only the monthly fee.
- Ask for a full data export before you decide.
- The redirect map is the most important document in the project.
- A test migration saves surprises on launch day.
Thinking about changing platforms?
In one call we can look at the platform your store runs on, what is holding you back, and whether a migration is the right move. Sometimes the answer is that it is not.
Contact us with your store’s address. See how we handle WordPress and WooCommerce migrations and WooCommerce development.
