This is one of the harder questions in e-commerce: an existing store is not working as it should. It is slow, hard to manage, does not integrate well with systems. Is it better to rewrite from scratch or refactor? Both options have their advocates and both can be the right answer – depending on context.
When rewriting makes sense
The platform has reached End of Life (Magento 1, older PrestaShop versions) and cannot be updated without rewriting. The architecture is so outdated that every change is risky and costly. The store requires features that the current platform structurally cannot support. The code is in such poor condition (no documentation, no tests, many unidentified authors) that debugging and developing it costs more than a new implementation.
When a refactor is enough
The platform is current and supported. The main problems are third-party modules, integrations or configuration – not the system core. Data and business processes work well, only the interface is outdated. Budget and time do not allow a full rewrite without risk of business disruption.
The “we’ll do it better from scratch” trap
Rewriting from scratch is tempting because it seems like this time everything will be done right. In practice a new project inherits the same business requirements as the old one – and often the same compromises. Rewriting typically takes 2-3x longer than estimated. During that time the old store is generating revenue – the new one is not yet. This is a financial risk worth calculating.
Hybrid approach
Often the best way out is an iterative migration: the new platform is launched in parallel with the old one, gradually taking over traffic. This allows testing the new solution on real users before the old store is shut down. It requires more effort but minimises risk.
If any of the signals described sound familiar, it is worth analysing before the problem grows. I offer a free initial consultation – write to biuro@tews.pl or visit tews.pl.
