PrestaShop was a serious choice for a shop. Over time, the modules made it complicated.
A module for payments, a module for shipping, a module for filters, and every version upgrade a small project of its own. I move products, customers, orders and Google rankings to a custom web shop with no modules clashing.
Where it starts to cost. Not on day one, but as the business grows.
- Modules
Every feature is a module you buy
Many of the useful modules are bought from the marketplace, and a new PrestaShop version often needs a new version of the module too. Over time the shop becomes a sum of other people's products.
- Conflicts
Modules that touch the same thing
Two modules that change the same page don't know about each other. The result is a checkout that suddenly stops working, and nobody knows why.
- Upgrades
A version upgrade that keeps being postponed
Going from 1.6 to 1.7 and on to 8 isn't a click, it's a migration of its own: themes and modules often don't make the jump. So the shop stays on the old version, and the old vulnerabilities stay with it.
What moves from the first product to the last order.
- Products
The catalogue with combinations
I take products, combinations (size, colour), features, categories, prices, stock and images through the PrestaShop webservice API or straight from the database. Combinations stay attached to their product.
- Customers and orders
Purchase history comes with you
Customers, addresses, customer groups and order history move to the new shop. If the protected password records can't be carried over, customers set a new password at first sign-in, with an email that explains why.
- URLs
Old links lead to the right product
Product and category URLs, with or without the ID in the address, get 301 redirects to the new ones, with meta titles and descriptions. Your Google rankings stay.
- Switchover
Orders don't stop for a day
I build the new shop alongside. Before the switch I run a final transfer of orders and stock, then change the DNS. You shut down the old shop once everything is checked.
Send me your website. You'll get advice and two time slots.
Enter your address and a few details. An email with advice for your platform and two open slots for a call arrives straight away, and I'll look at your site personally and get back to you.
- Advice for your platform you can act on right now, without me
- A personal look at your website and an idea for your business
- Two open slots for a 30-minute call, one click to book
Frequently asked questions
Module licences don't transfer, but the features do: they become part of the shop. At the end there are no modules to upgrade and no licences to renew.
No. The move goes straight from the database, so an upgrade that would be thrown away anyway isn't needed.
Yes. Your contracts with the bank, the card processor and the couriers stay as they are. The new shop connects to the same services directly through their APIs, with no module in between.
Not if the migration is done properly. Every old URL gets a 301 redirect, meta titles and descriptions move with it, and after the switch I watch Search Console until the index settles. A drop in traffic after a migration is a sign nobody did that work, not a consequence of the migration.
It depends on the scope and on whether a redesign comes with it. Roughly the same as a build: a website 3–6 weeks, a web shop 6–12 weeks. The exact timeline is in the proposal, before work starts.
No. You cancel the old platform only once the new site is live and we've checked that content, redirects and, for a shop, orders are all in place. Until then the old site runs as it always has.
Because migrating a five-page website and a shop with thousands of products are not the same job. After a call and a look at your site you get a fixed proposal, and that figure holds until the end of the project.
The site comes with maintenance: updates, security monitoring, daily backups and uptime monitoring. Alongside it comes SEO + AEO, so after the move the site doesn't stand still but gets found by search engines and AI models.