How do you know it is time to switch webshop platforms?
Not at the first outage, but when the same problem returns a second time in the same month, or when nobody still knows which plugin does what. What tips the balance is usually a sum of things: time, knowledge sitting with one person, and integrations that keep getting more tangled.
- Plugin chaos is the clearest signal on WooCommerce and Shopify.
- On Lightspeed and CCV Shop, shop-floor stock and online stock drift apart more often.
- One crash rarely decides it. It is a sum of things.
I get the same question more and more often: how do you know it is time to switch? Usually it is not one thing. It is a sum of things.
The moment the plugin list becomes the problem
On a WooCommerce shop I moved over last year, I counted thirty-six active plugins. Not because the owner wanted that. Each plugin solved one problem: a payment method, a shipping rule, an SEO check, a pop-up. On its own, every plugin worked fine. Together they threw up an update conflict every few weeks.
That is the pattern I see most often on WooCommerce and Shopify: the core works, but everything around it grows like loose sand. At some point the upkeep costs more time than setting up the platform ever did.
Where it really tips over
Not at the first outage. Almost every shop owner I speak to has had a plugin update break something at some point. You survive that.
It tips over when it happens a second time in the same month. Or when you notice you no longer know which of your forty plugins delivers which piece of functionality, so you no longer dare to update for fear something falls over. From that moment on you are not managing your webshop any more. You are managing your fear of your own stack.
Lightspeed and CCV Shop: a different problem, the same outcome
On Lightspeed and CCV Shop I see less plugin chaos, but a different pattern instead: the shop floor and the webshop do not talk to each other properly. Stock in the shop and stock online are two separate records that you have to keep aligned by hand, or through an integration that stalls now and then. That works until it does not: a product sold in the shop that can still be ordered online.
What actually tips the balance in practice
Looking back at the migrations I have run myself, it was almost never one big crash that made the decision. It was three things adding up.
First, the time the upkeep costs grows faster than turnover does. You spend more hours keeping the stack running than you spend selling.
Second, nobody on the team knows exactly how it all hangs together any more. One person is the only one who dares to update, and that person is on holiday at the wrong moment.
Third, every new feature you want to add starts with working out which of the existing plugins it is going to clash with.
What I would check before you start
Before you consider a platform, I would start with a simple inventory: which plugins or apps are active, what does each one do, and which of them are really standard functionality that your platform just does not ship with. On most shops I go through, at least half the active plugins turn out to solve something an integrated platform already does.
That is no reason to switch blindly. It is a reason to take the question seriously before the next plugin update answers it for you. Want to know what that migration actually looks like in practice? I wrote up the playbook from three of my own migrations.