Win Health
Years of moving between eCommerce platforms ended here: one catalogue, one stock position, and an admin side built for the people in it every day.
Read the case study: Win Health →
Magento and Adobe Commerce
Catalogues, trade pricing and integrations that off-the-shelf carts can't carry. Magento Open Source and Adobe Commerce suit retailers with large catalogues, complex pricing, B2B accounts and serious ERP, stock and fulfilment integrations. We build on it, upgrade it, and move stores onto or off it when the numbers say so.
Where you're starting from
- Magento 1
- Magento 2
- Adobe Commerce
- Shopify
Where you go next is decided in the Blueprint. Sometimes the answer is to upgrade.
Which situation are you in?
Unsupported
Still on Magento 1
Magento 1 reached end of life in June 2020 and no longer receives security patches. Moving to Magento 2 is a rebuild rather than an upgrade: the theme, extensions and integrations all change.
We rebuild on Magento 2, or move you elsewhere.
Running hot
On Magento 2 or Adobe Commerce
Upgrades that keep slipping, extensions that conflict, and a store that slows down at peak. We audit the codebase and tell you whether an upgrade and clean-up will do, or whether it's time to rebuild.
We audit, then upgrade in place where we can.
Re-platforming
Moving off Magento
Sometimes the cost of running Magento outweighs what it gives you. We move stores to Shopify Plus when the evidence supports it, and say so when it doesn't.
Magento to Shopify Plus, with the data intact.
What usually goes wrong, and how we stop it
eCommerce migrations fail on the data and the joins: a price rule nobody documented, an order sync that drops a field, a category URL that took years to rank and disappears overnight.
1
Catalogue and data
Products, variants, customers and order history mapped and rehearsed with real data before cutover.
2
Pricing rules
Trade, tiered and customer-specific pricing documented and rebuilt, then tested against real orders.
3
URLs and SEO
Every product and category URL redirected, tested before launch and monitored afterwards.
4
ERP and stock
ERP, PIM, stock and fulfilment integrations inventoried and decided on: keep, rebuild or retire.
5
Checkout and payments
Checkout and payment providers tested end to end, with PCI DSS scope kept as small as possible.
6
Peak trading
Cutover timed away from your peak, with load testing before launch and a rollback plan.
How a Magento project runs
Typically six to nine months
- DiscoveryWorkshops, codebase and extension audit, integration inventory.
- ArchitectureCatalogue model, pricing rules, integrations, redirect plan.
- Build and migrateStaged releases and repeated test migrations of real data.
- CutoverTimed around trading, final migration, redirects, rollback plan.
- HandoverTraining, documentation, support through WebsiteSupport.io.
eCommerce projects we've delivered
CIA Alarms
Forty years of trade knowledge, very clear ideas about the CMS, and a catalogue that had to be right first time.
Read the case study: CIA Alarms →Questions
If yours isn't here, it's usually quicker to ask on the phone.
Magento Open Source or Adobe Commerce?
Open Source is free to license and suits most mid-sized stores. Adobe Commerce adds licensed features such as advanced B2B, staging and cloud hosting. We compare them against what you actually need before you commit to a licence.
Should we move from Magento to Shopify Plus?
Sometimes. It depends on your catalogue, pricing rules, integrations and how much customisation you need. Discovery compares running costs and trade-offs over several years, not only the build.
We're still on Magento 1. Where do we start?
With a migration plan. Magento 1 is out of support, so the priority is moving your data, URLs and integrations to a supported platform without disrupting trading.
Will we lose our search rankings?
Not if the redirects are planned. Every product and category URL is mapped during architecture, tested before cutover and monitored afterwards.
Can our ERP integration stay as it is?
Often it can. We inventory every connection during discovery and agree which to keep, rebuild or retire before build starts.
After launch
Magento support and maintenance →Already live? WebsiteSupport.io looks after it
Once a Magento site is live, our sister company WebsiteSupport.io keeps it patched, monitored, hosted and improving.
Start with a Blueprint!
Three weeks, from £5,500 + VAT. Credited against the build, and yours to take to any supplier.