Magento 1 and OpenMage
Magento 1 support for stores that are still selling
Your Magento 1 store still pays the bills, and years of custom features make moving a big decision. Fair enough. Magento 1 hit end of life in June 2020, but we keep stores on 1.9 and OpenMage patched, locked down and running. Where it fits we move you to OpenMage LTS, get you onto PHP 8 and put PCI controls in place. Meanwhile we plan the move to Magento 2 or Shopify on your timetable, so a hack doesn't force the decision for you. You get a risk review, a log of every hardening change and a migration plan with rough effort for each option.
- Working on Magento 1 since 2011
- OpenMage LTS upgrades and PHP 8 support
- PCI hardening for end-of-life stores
- A planned move to Magento 2 or Shopify
2011
When we started working on Magento 1
PHP 8
Supported through OpenMage
Your timing
You choose when to migrate
Merchants on Magento 1.9 or OpenMage with plenty of custom features
Stores whose acquirer or PCI scan keeps flagging the platform
Businesses planning a replatform who need the current store safe until then
Teams with nobody left who knows Magento 1
Adobe stopped patching Magento 1 in 2020. Attackers kept looking. Unpatched Magento 1 stores are a favourite for card skimming, and plenty still run PHP versions that haven't had a security fix in years. Meanwhile developers who know the platform properly are getting scarce. Sitting tight is risky, and so is rushing a rebuild. The sensible move is to make the current store as safe as possible and plan the migration properly.
signs-you-need-this.log
- ›Your store still runs Magento 1.9 or earlier
- ›The server is on PHP 5.6 or 7.x
- ›Your acquirer or PCI scan keeps flagging the platform
- ›The developers who knew the code have moved on
- ›Someone told you the only option is an immediate rebuild
We make the store as safe as an end-of-life platform can be, then move it when the timing suits the business.
- Step 01
Security and risk review
A malware sweep by content, plus patch level, admin and server access, checkout scripts, extensions and PHP version. You'll know exactly where the store stands.
- Step 02
Patch it, or move to OpenMage
Where it fits, we upgrade to OpenMage LTS, the community fork that still gets security fixes and runs on PHP 8. Where it doesn't, we apply community patches and backport fixes by hand.
- Step 03
Lock it down
Admin path and access limits, two-factor login, WAF rules, file integrity monitoring, checkout script controls, and server and PHP hardening.
- Step 04
Keep it running
Bug fixes, payment module updates, extension repairs and speed work, on a retainer or when you need it.
- Step 05
Plan the move
A written plan to Magento 2 or Shopify, covering how the data and SEO will move, so you migrate when you choose to.
We know Magento 1 properly
We've worked on it since 2011. The database, the layout system, the module structure and the quirks of 1.9 are home ground for us, so we're not reverse-engineering your store as we go.
We won't push you into a rebuild
We'll tell you plainly whether your Magento 1 store can keep trading safely and what it'll take. When to migrate is your call.
Security comes first here
An end-of-life platform needs more security attention, so our Magento 1 work always starts with a malware sweep and hardening. That's where the real risk is.
Either destination
We move Magento 1 stores to Magento 2 and to Shopify. Which one depends on your store, and we don't have a favourite.
Related services
Malware removal & security
Skimmers and backdoors removed, the way in found and closed, and a report your payment provider can use.
Emergency support
Store down, hacked or not taking orders? You get priority response and an experienced developer on it.
Magento 1 to 2 migration
Products, customers, orders and Google rankings moved from Magento 1 to Magento 2.4.9, with a practised launch.
Magento to Shopify migration
Products, customers, orders and every URL Google ranks, moved from Magento to Shopify or Shopify Plus.
Tell us what you're planning for the store.
You'll speak to one of the developers. We'll tell you which route we'd take, what usually goes wrong on projects like yours and where we'd start.
Happy to sign an NDA · Everything tested on staging first · The code is yours