Magento 1 support: patching, DevOps and a plan to move on
Magento 1 reached end of life in June 2020. We keep your store patched, hosted and monitored, and plan the move off it when you're ready. Certified developers, from $90/hr.
- Manual security patching
- Certified Adobe Commerce developers
- Dedicated DevOps team
Test drive our developers. 3 guaranteed hours of free Magento work.
Hand us a real task and our senior engineers do the first 3 hours on us. No obligation to hire us, just a straight look at how we work.
- Fix a bug
- Speed up a slow page
- Build a small feature
- Review your code
Not sure where you stand? Get a free audit.
We'll review your site's performance, code quality, UI/UX, and growth and optimization opportunities.
Magento 1 is end of life, and it can still be made safer
Adobe ended Magento 1 support in June 2020, and official security patches stopped with it. Plenty of stores still run on it for real reasons: budget, custom work, a busy season.
Patching by hand lowers the risk. It does not remove it. We tell you both halves.
- 1
Manual patches reduce risk, they don't end it
No vendor tests our fixes for you, and the platform around them keeps aging.
- 2
Hosts are moving on
Magento 1 needs PHP 7.2 or newer compatibility patches to run on a current server, and hosts keep dropping the older stack.
- 3
Extensions have been abandoned
Most Magento 1 extensions haven't been updated in years, so the fixes fall to you or to us.
- 4
Card payments raise the stakes
If you take payments, PCI compliance expects supported, patched software.
Support buys you time. The point of that time is a plan.
Support for a codebase Adobe no longer maintains
Security patches, applied manually
We apply security fixes by hand on a codebase Adobe no longer ships patches for, highest risk first.
DevOps and server changes
Our DevOps engineers keep your server changes ahead of what hosts are dropping, including the PHP compatibility patches Magento 1 needs.
Maintenance and monitoring
Proactive monitoring, so problems on an aging stack are caught before they become downtime.
Hosting and configuration
Hosting and server setup for Magento 1's older stack, kept running reliably instead of drifting further out of support.
Custom extensions
We audit, fix and build extensions against your actual store, since most off-the-shelf ones are no longer updated.
Bug fixes and small features
Ongoing development so the store keeps selling while you plan next steps.
Certified developers
Multiple Adobe Commerce certifications across backend, frontend and cloud.
Migrations
A scoped plan and full execution when you move to Magento 2, BigCommerce or Shopify.
Stabilize now, move on your own timeline
Assess
Store, extensions, hosting
Stabilize and patch
Priority fixes first
Harden and monitor
DevOps watching the stack
Support
Retainer, fixes, features
Move
To a supported platform
Many clients start on a support retainer and migrate once the plan and budget are right. You don't have to decide the last step to start on the first.
Three honest positions
Support is a bridge
It keeps a working store safe and selling. It is not a destination, and we won't pretend it is.
Patch what attackers reach first
We start with the exposures that matter most, then work down the list, instead of billing you for everything at once.
You set the timeline
We scope the migration and tell you what it involves. When to move is your call, made with real numbers.
Supporting B2B on Magento 1
Magento 1 predates Adobe's native B2B module, so B2B here usually runs on third-party extensions from that era. We support and extend what's there, without pretending it's Adobe Commerce B2B.
Existing B2B extension support
We maintain and extend the wholesale extensions your store already runs on.
Customer group pricing
Native customer groups and tier pricing, configured or fixed for how your accounts buy.
Quote and negotiated pricing workarounds
Practical quote workflows built inside the Magento 1 extension ecosystem.
A path to native B2B
Moving to Magento 2 or Adobe Commerce gets you native B2B instead of stacked extensions.
Backorders and pre-orders
Approved buyers can order out-of-stock items against a clear backorder date.
CSV and quick-order upload
Bulk add-to-cart from a CSV or SKU and quantity list.
EDI order channel
Large accounts order the way their own systems already work.
Grid ordering
Order multiple sizes, colors or variants in one grid on the product page.
Sales rep logic
Reps log in as a customer and place the order on their behalf.
A refreshed front end, without a forced re-platform
For stores staying on Magento 1 a while longer, a redesign can buy you a better converting store now while you plan the migration properly.
A redesign is cosmetic and UX focused. It does not fix the end of life problem. Security patching and migration are separate services, and we'll tell you plainly if a migration should come first.
What a redesign includes
- Updated .phtml templates and layout
- A full site audit before we touch a page
- A complete redirect map, SEO safe
- Navigation, product pages and checkout reworked for UX
- Performance budgets for Core Web Vitals
- Phased rollout if a full cutover is too risky
Choosing where to go next
We typically recommend Magento 2, BigCommerce or Shopify Plus. The right one depends on your catalog, your B2B and B2C mix and your budget. We'll be honest, even when the answer isn't Magento.
Magento 2 or Adobe Commerce
- Heavy customization
- Complex B2B rules and native B2B module
- Deep ERP and system integrations
BigCommerce
- More standard needs, less maintenance
- B2C and B2B Edition on one platform
- A fast storefront without running your own servers
Shopify or Shopify Plus
- Mostly standard commerce needs
- Wholesale through Shopify's native B2B on Plus
- Checkout Extensibility and Flow automation
Still running Magento 1?
Tell us what you run and we'll tell you how exposed it is and what to do first. Our free audit is a good place to start.
Talk to usFrequently asked questions
Is Magento 1 still safe to run?
Magento 1 hasn't received official security patches since June 2020. We apply fixes manually, which lowers the risk but doesn't remove it. We recommend running it only while you plan a move.
Can you patch vulnerabilities Adobe no longer fixes?
Yes. Applying security patches manually on unsupported Magento 1 codebases is one of our most requested engagements.
Do you only offer migration, or ongoing support too?
Both. Many clients start on a support retainer and migrate on their own timeline once the plan and budget are right.
Which platform should we migrate to?
It depends on your catalog, B2B and B2C mix and budget. We typically recommend Magento 2, BigCommerce or Shopify Plus, and we'll walk through the tradeoffs honestly.
Can you migrate our custom extensions and data?
Yes. Extension and data migration is a core part of our platform migration service, and our team has completed 40+ platform migrations with a 100% success rate.
Do you handle hosting and server management too?
Yes. Our DevOps engineers handle hosting, server changes and configuration. Magento 1 needs PHP 7.2 or newer compatibility patches to run on a current server, and we stay ahead of what hosts are dropping.
Are your developers certified?
Yes. Our developers hold multiple Adobe Commerce certifications. We are an independent agency, not an official Adobe partner.
How is Magento 1 support priced?
Hourly, from $90/hr. The rate depends on your plan and what your store needs. See our Pricing page for the monthly agreement, retainer and pay-as-you-go tiers.
What do we need to decide before a B2B launch?
Who qualifies for B2B pricing, who approves applicants, what approved accounts see and pay, order minimums, terms and tax exemption handling. If you are planning to move to Magento 2 anyway, we settle these before the move.
Do B2B buyers need special ordering features?
Often. Grid ordering, CSV and quick-order upload and sales rep login are common requests, and we can add them on top of your existing B2B extensions.
Does a redesign fix the end of life problem?
No. A redesign is cosmetic and UX focused. Security patching and an eventual migration are separate, related services.
Is it worth redesigning instead of migrating first?
Sometimes. A redesign can buy you a better converting store now while a migration is planned properly. It depends on your timeline and budget, and we'll walk through the tradeoff honestly.
Will a redesign hurt our SEO rankings?
Not if a complete redirect map from every existing URL to its new equivalent is built before launch.
Get a quote for Magento 1 Support
Ready to plan your project?
We'll follow up within one business day to talk through scope and next steps.
Start a ProjectRelated services
Magento 1 to Magento 2 Migration
Migrate your end-of-life Magento 1 store to Magento 2 / Adobe Commerce, and get back on a platform that still receives security patches.
Learn moreMagento 1 to Shopify Migration
Migrate your unsupported Magento 1 store to Shopify or Shopify Plus, fully managed, with no more security patching to worry about.
Learn moreMagento 1 to BigCommerce Migration
Migrate your unsupported Magento 1 store to BigCommerce, fully managed, without losing data or rankings.
Learn more