Version upgrades
Core, PHP and every module moved together, with custom code patched and kept.
Technical improvements
Magento upgrades,
done in days
Ari runs version upgrades, security patches, extension fixes and integrations on a copy of your store, then hands you one pull request.
What an upgrade takes
Time
40 hourswith Ari and a developer250 hoursin a typical agency quoteTested
Every pageon a preview store, before anything goes liveSpot checkson staging, if the quote includes itCustom code
Keptpatched for the new version, with its testsRewrittenor dropped, in many quotesEvery kind of technical work
Apply the September patchnorthfield-store.com
Security patches
Applied and checked on a copy of your store, then sent for review.
Extension conflicts
Modules that break each other after an update, found and fixed one at a time.
Bugs
Reproduced on a copy of your store, traced to the cause and fixed.
Performance
Images resized, scripts deferred and the cache warmed, measured before and after.
Send new orders to the ERP and bring back stock and trackingnorthfield-store.com
ERP, PIM and carriers
The connector upgraded or fixed, with its field mapping tested both ways.
How a Magento upgrade runs
You ask for the upgrade in the chat
One sentence, in your own words. Ari says what it found and what it will do, and you can ask for the technical outline before anything starts.
How a change is made →Every module you run is read first
Versions, the compatibility code a previous vendor left behind, and which modules have a release for the target version. Nothing is touched yet. The audit is the first thing you get, and you can stop there.
The dependency tree is resolved
The target version, PHP, and every module and its requirements, resolved together. Where a compatible release exists, it is used. Where none exists, the module goes on the patch list.
Modules with no new version are patched
Custom modules and abandoned extensions are patched to the new APIs and kept, with their tests. Your customizations survive the upgrade.
The upgrade runs on a copy of your store
Composer, setup:upgrade, compilation, static content, reindex and the test suites, on the copy of your store. The live store and its database stay exactly as they are.
Security and access →The storefront and the admin are checked
Every page type on every store view, the checkout with a test order, the emails, and the admin screens your team uses, with screenshots. Anything that breaks is in the report before you see it.
You get one pull request
The full diff, a module report, the screenshots, and the checks already green. Your developer reviews and merges it like any other branch, and it goes through your own staging and release.
Contact sales →K
You
Upgrade us from 2.4.6 to 2.4.9 and tell me what breaks.
Ari
You run 142 modules on PHP 8.1. I will read them first, then resolve, patch and run the upgrade on the copy of your store. The first read takes about 20 minutes. Do you want the technical outline before I start?
K
You
Yes, send the outline first.
Reply to Ari
ModuleInstalledStatus
amasty/shopby2.16.4conflicts with 2.4.9klarna/m2-payments8.1.0no 2.4.9 release yetacme/module-legacy-import1.4.2custom, unmaintainedmageplaza/smtp4.1.0outdatedmirasvit/module-seo2.9.1outdated58 other modulescompatible
142 modules read, in about 20 minutesNothing touched yet
> composer why-not magento/product-community-edition 2.4.9amasty/shopby 2.16.4 requires magento/module-catalog ~104.0 2.4.9 ships 105.1klarna/m2-payments 8.1.0 requires php ~8.1 2.4.9 needs 8.3> resolving 142 packages against 2.4.9 and PHP 8.3amasty/shopby 2.18.0 released, compatibleklarna/m2-payments 10.1.0 released, compatibleacme/module-legacy-import no newer version, needs a patch✓ 141 resolved 1 to patch
141 resolved, 1 left to patchPHP 8.3
Plugin/ProductImport.php · uses a class removed in 2.4.9- use Magento\\Framework\\App\\ObjectManager;- $this->helper = ObjectManager::getInstance()->get(ImportHelper::class);+ public function __construct(ImportHelper $helper) { $this->helper = $helper; }etc/di.xml · the CSV reader is replaced- <preference for="Magento\\ImportExport\\Model\\Import\\Source\\Csv" .../>+ <type name="Magento\\ImportExport\\Model\\Import\\Source\\Csv"><plugin .../></type>✓ 3 files patched the import still runs, 12 fixtures pass
Custom code carried across with its 12 fixtures3 files
> composer require magento/product-community-edition 2.4.9 --with-all-dependencies 6m 12s> bin/magento setup:upgrade 41s 38 schema changes, 12 data patches> bin/magento setup:di:compile 3m 12s> bin/magento setup:static-content:deploy en_US de_CH fr_FR 6m 40s> bin/magento indexer:reindex 1m 08s 4,108 products, 3 store views> vendor/bin/phpunit 1,204 passed · integration 318 passed✓ 2.4.9 up on the preview store your live store untouched
Run on a copy of your storeLive store untouched
ScreenCheckedResult
Home, category, product, searchon 3 store viewsrenders
Cart and checkouta test order placedrenders
Customer accountlogin, addresses, reorderrenders
Admin: orders, products, promotions24 screensrenders
Admin: legacy importa CSV of 200 rowsimports
Emails: order, shipment, invoicesent to a test inboxrenders
58 pages and 24 admin screens, with screenshots0 errors
Upgrade to Magento 2.4.9Open
ari/upgrade-2.4.9 into mainComposer install and setup:upgrade41 sUnit tests1,204 passedIntegration tests318 passedStatic analysis, PHPStan level 6cleanStorefront walk58 pagesAdmin walk24 screens
61 files, a module report and 82 screenshotsReview requested
PayPal
Adyen
Klarna
Stripe
DHL
UPS
FedEx
SAP
Salesforce
HubSpot
Mailchimp
AlgoliaThe systems Ari connects to
Ari connects to payment, shipping, ERP, PIM, search and marketing platforms through their Magento modules and APIs. Ari reads the module and its documentation first, and tests the connection on a copy of your store.
Questions
Which versions can Ari upgrade?
Any store on 2.3 or 2.4, on Magento Open Source or Adobe Commerce, up to 2.4.9.
Is the upgrade run on our live store?
No. The upgrade runs on a copy of your store, and a person merges and releases it.
What if an extension has no compatible release?
Ari patches it for the new version and keeps its tests. Custom modules are patched the same way.
How long does an upgrade take?
A typical upgrade takes about 40 hours with Ari and a developer. An agency usually needs around 250 hours for the same job.
How many credits does an upgrade use?
An upgrade uses a few hundred task credits, out of the 2,000 a month in the $99 plan.
Pricing
A month of Ari for less than 2 developer hours
$99from, per month
Enterprise plans carry custom volumes and terms. Contact sales, or read what it costs and how it works.