Magento 1 Support, Migration & Upgrade
make it safe first. Then decide where the store goes.
For businesses whose online store still runs on Magento 1. We reduce the risk while it keeps trading, keep it on maintained code where that is the right call, and move the catalogue, customers and orders to Magento 2, Adobe Commerce or a simpler platform when it is time.
More about this service
We are an Australian team working remotely with businesses in the United States, the United Kingdom, New Zealand and Australia. Every engagement starts with a scoped technical assessment, so the estimate that follows is based on your code and your data.
- Assessment A scoped technical review before any estimate
- 18+ yrs Building business software
- Independent No licence commission, no reseller agenda
- US UK NZ AU Australian team, working remotely
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
The store still takes orders. Adobe stopped patching it in 2020
Magento 1 ran a very large number of online stores, and many were heavily customised: a bought theme, dozens of extensions, and code written for one business. That investment is why stores stayed on it after Adobe ended support on 30 June 2020. Adobe told merchants that from that date they carry more of the responsibility for security and for card compliance.
Read more
The difficulty is that Magento 2 is a different system, not a new version. Data can be moved. Themes, extensions and custom code cannot simply be carried over, so a move is a migration and a partial rebuild. That makes it worth asking what the store really needs, and whether Magento is still the right size of platform for it.
Our Magento developer service is for businesses in Perth, Melbourne, Sydney and Brisbane. It covers three kinds of work: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
Three ways forward for a Magento 1 store
The first is only safe on maintained code.
-
Keep it and make it safe
The store stays on Magento 1 code, moved to OpenMage, the community project that maintains it, and to a current version of PHP, the language Magento is written in. Admin access is locked down, faults are fixed and changes are made. This suits a store that works and cannot justify a rebuild yet.
-
Move to Magento 2 or Adobe Commerce
Products, customers, orders and settings are migrated. The theme is rebuilt, each extension is replaced by its Magento 2 version or an alternative, and custom code is written again. Right for a store that uses what Magento is good at: large catalogues, several storefronts, complex pricing.
-
Replace it with a simpler platform
Where the store is mostly a catalogue, a cart and a checkout, it moves to Shopify or WooCommerce in stages: catalogue first, then customers and order history, then the connections to accounts and shipping.
What we do with Magento 1 stores
Six kinds of work. Most engagements are three or four of them.
-
Store audit
Version, patches applied, extensions, theme, custom code and changes made to core files listed, with what is used and what is not.
-
Security hardening
The admin address and logins locked down, unused extensions removed, the server tightened, and the checkout checked for scripts that should not be there.
-
Move to OpenMage
The store moved onto the maintained community code and a current PHP, with every extension tested on a copy first.
-
Magento 1 maintenance
Faults fixed and changes made in the existing theme and extensions while the store keeps trading.
-
Data migration
Products, categories, customers, orders and content moved to the new platform, with counts and totals reconciled.
-
Addresses and redirects
Every product and category address kept or redirected, so links, bookmarks and search ranking survive the move.
Holding, moving to Magento 2 and leaving Magento are different projects
The right one depends on how much of Magento the store really uses.
-
Stay on Magento 1 code
Lowest cost. Reasonable on OpenMage and a current PHP, with somebody responsible for updates. On the original Adobe code it is a short holding position: a public checkout without security fixes is exposed.
-
Magento 2 or Adobe Commerce
Keeps the catalogue structure, storefronts and pricing rules that larger stores depend on, on software Adobe supports. The theme, extensions and custom code are rebuilt, and it carries the running cost of a large system.
-
Shopify or WooCommerce
Less to run and less to secure. Right when the store is mostly products, a cart and a checkout. Anything that leaned on Magento features or custom code has to be reconsidered, and a hosted platform such as Shopify sets its own limits on what can be changed.
What a Magento 1 assessment looks at
The dates and version facts are from Adobe, the PHP project and the OpenMage project. The rest is about what your store is made of.
-
Version and patches
Magento Open Source 1, once Community Edition, or Magento Commerce 1, once Enterprise Edition, the exact version, and which patches were applied. Adobe issued its final patches in June 2020, for Open Source 1.9.4.5 and Commerce 1.14.4.5 and earlier.
-
Changes to core files
Whether anybody edited Magento's own code instead of adding to it. Edited core files are why patches fail to apply, and why a move to OpenMage is checked file by file.
-
Extensions
Each add-on in use, who made it, and whether a version exists for OpenMage, for Magento 2 or for the platform you might move to. Adobe took Magento 1 extensions off its Marketplace after the end of life.
-
The theme
A Magento 1 theme cannot be installed on Magento 2 or on another platform. The design is rebuilt, which is also the chance to fix a checkout that never worked well on phones.
-
PHP and the server
Magento 1 gained support for PHP 7.2 in version 1.9.4.0, and PHP 7.2 reached end of life on 30 November 2020. OpenMage needs PHP 8.1 or newer. We check what the server runs, including the database, and who applies updates to it.
-
Payments and card data
How cards are taken: on a page hosted by the payment provider, or on a form inside the store. This decides how much of the card industry security standard, known as PCI DSS, applies to you, and how urgent the work is.
-
Integrations
Connections to accounting, stock, shipping, marketplaces and email, and whether each is an extension, a scheduled file or custom code. Each one has to work on whatever the store runs on next.
-
Addresses and traffic
Which product, category and content pages people and search engines use. Every address is kept or redirected.
Still on Magento 1, with no security patches from Adobe since June 2020?
What the assessment needs from you
A fixed-scope piece of work with a written result: the options, the risks of each, and a staged estimate. No production data is sent by email. We agree a secure way to share it first.
-
The store
Its address, what it sells, and roughly how many orders it takes in a month.
-
Version
The Magento edition and version shown at the foot of the admin screens, and any patches you know of.
-
Access
An administrator login and access to the code and the server, or to somebody who has them.
-
Size
Roughly how many products, customers and past orders.
-
Extensions and custom work
The extensions you know of, who built the theme, and any custom features.
-
Hosting
Where it is hosted, who manages the server, and the PHP version if you know it.
-
Payments and integrations
How you take payment, and what the store connects to: accounts, stock, shipping, email.
-
What is hurting
The two or three problems that started the conversation.
-
The way back
How long you could trade on the old store if a cutover had to be reversed.
From assessment to a store that is supported
Done remotely, with meeting times agreed to suit your time zone.
-
Audit and assessment
We list what the store is made of and what is used, and put OpenMage, Magento 2 and a simpler platform side by side. You get written options with the risks of each and a staged estimate.
-
Reduce the risk
The live store is tightened first: admin access, unused extensions, the server and the checkout. This happens whichever option you choose.
-
Trial migration
The catalogue, customers and orders are moved into a test store early, so problems with the data show up before the build is finished.
-
Build
The theme, the extensions and the custom functions are rebuilt or replaced, in stages agreed from the assessment, each with its own scope and estimate.
-
Checks and redirects
Product counts, prices, stock and order history are reconciled, test orders are placed, and every old address is made to resolve.
-
Cutover and support
The switch is planned for a quiet trading time, with a way back. We watch the first days of live orders, then maintain the store for as long as it stays in service.
What people ask us about Magento 1
Is Magento 1 still supported?
Not by Adobe. Support for Magento Open Source 1 and Magento Commerce 1 ended on 30 June 2020, and the last security patches were issued that month. A community project, OpenMage, still maintains the Magento 1 code, and is one way to stay on it with security fixes.
Can we upgrade Magento 1 to Magento 2 directly?
Not as an upgrade. Magento 2 is a different system. Adobe describes the move as four parts: data, extensions and custom code, themes, and customisations. Adobe provides a tool that moves the data. The other three are rebuilt or replaced.
Is it safe to keep trading on Magento 1?
On the original code, with no fixes since 2020, not for long. An unpatched public checkout is what card-skimming scripts look for. On OpenMage with a current PHP, card payment on a page hosted by the payment provider and somebody watching it, the risk is much lower.
What is OpenMage, and is it a real option?
It is an unofficial, community-run continuation of the Magento 1 code. It still publishes security fixes and needs PHP 8.1 or newer. For a store that works and has compatible extensions it can be the right answer. The project says its 20 series may not be fully compatible with older code, so every extension is tested.
Should we stay on Magento at all?
It is worth asking. If the store is a catalogue, a cart and a checkout, Shopify or WooCommerce will usually cost less to run and to keep secure. If you rely on several storefronts, complex pricing or heavy custom work, Magento 2 or Adobe Commerce earns its place.
Will we lose our search ranking or our order history?
Not if both are part of the project from the start. Every old address needs to resolve, and customers and past orders are migrated and reconciled. On some platforms customers are asked to set a new password, because stored passwords do not always carry across.
Do you provide Magento developers in Perth, Sydney, Melbourne and Brisbane?
Yes. We are an Australian team and we take on Magento work for businesses in Perth, Sydney, Melbourne and Brisbane, and elsewhere in Australia. Most of the work is done remotely, by video call and screen share, with secure access to a copy of your system. The service is the same in every city: code fixes and updates, migration to a modern technology stack, and ongoing maintenance and support.
How does this work from the United States, the United Kingdom or New Zealand?
Remotely. We are based in Australia and do not have offices elsewhere. Discovery is done by video call and screen share, with meeting times agreed to suit your time zone. Confidentiality, who can reach your systems and where your data is held are agreed in writing before work starts.
What does it cost?
The assessment is a fixed-scope piece of work with an agreed fee. The estimate for anything after it comes from what the assessment finds, in stages, so you are not asked to commit to a whole project on a guess.
Sending your details…
You can stay on this page while we send it.
Tell us about your Magento 1 store
The store address, the Magento version if you know it, who looks after it, how you take payment, and what is forcing the question. Include your country so we can suggest meeting times. Please do not send production data.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.
Kasun Wijayamanna, founderYou deal with Kasun from scope to delivery. No account managers and no offshore handoff.