Adobe Commerce & Magento

Magento, upgraded or moved, on purpose.

Adobe Commerce and Magento Open Source can run very complex stores. We help you decide whether to upgrade, rebuild the front end with Hyvä, or move platform, and then do it carefully.

  • 6–16 wksUpgrade to full rebuild.
  • HyväLighter, faster front end option.
  • Clear callUpgrade or move, with reasons.
What we build

What we do for Adobe Commerce and Magento

Seven jobs we take on most for Magento stores.

Upgrades

Older Magento 2 releases brought to the current 2.4.x line, extension by extension.

  • 2.4.4
  • Audit
  • 2.4.x
  • Live

Hyvä front ends

A lighter front end that cuts JavaScript and improves Core Web Vitals.

Extension clean-ups

Unused and overlapping extensions removed, the rest updated.

B2B features

Company accounts, shared catalogues and quotes set up and connected.

ERP and PIM wiring

Orders, stock, prices and product data synced with your systems.

Re-platform planning

A side-by-side comparison of upgrading against moving to another platform.

Security and care

Patches applied and tested, monitoring and backups in place.

Fit check

Should you stay on Magento?

Magento handles complexity few platforms can, but it has a running cost to match.

Good fit

Teams stay on Magento for

  • Complex business rulesDeep customisation of catalogue, pricing and checkout.
  • Many sites, one installMultiple websites, stores and views.
  • Advanced B2BRich B2B features in Adobe Commerce.
  • Full controlOpen source code and your own hosting with Open Source.
Known limits

When moving may be better

  • Running costHosting, patching and upgrades need steady investment.
  • Little customisation leftA simple store may run cheaper on SaaS.
  • Hard-to-find skillsExperienced Magento developers are scarcer.
  • Version driftFalling behind on releases makes every upgrade harder.
Editions explained

Open Source, Adobe Commerce or SaaS?

People say “Magento” for all of these, but they are run, licensed and upgraded differently. Knowing which one you have changes the advice.

Swipe sideways to compare every column.

Magento Open SourceFree, self-hostedAdobe Commerce (on cloud or on-premises)Licensed, still your codeAdobe Commerce as a Cloud ServiceAdobe’s newer SaaS option
What it isThe open-source core of Magento 2. You download it, host it and maintain it.Adobe’s licensed edition, with B2B features, staging and other extras, run on Adobe’s cloud infrastructure or your own servers.A SaaS version where Adobe runs and updates the core, and you extend it from outside rather than editing it.
UpgradesYour team applies each 2.4.x release and security patch through Composer, then tests.Still a code upgrade you plan, apply and test, even on Adobe’s cloud hosting.Handled by Adobe. Custom logic moves to apps and integrations instead of modules in the core.
Best forStores with real customisation and a developer or partner on hand.Complex B2B, many sites and teams who need the extra features.Teams starting fresh on Adobe who want fewer upgrade projects.
Strong when you value control and have someone to run it.Worth it when you use the licensed features.Moving here from an existing store is closer to a re-platform than an upgrade.
Connected

Magento, wired into the rest

Systems we most often connect to Adobe Commerce and Magento stores.

SAP Business OneerpNetSuiteerpDynamics 365 BCerpAcumaticaerpAkeneopimSalesforcecrmKlaviyoemailAlgoliasearchAvalarataxShipStationshipping
Delivery

A Magento upgrade, start to finish

  1. Week 0

    Audit call

    Version, extensions and pain points in 30 minutes.

    Gap list
  2. Weeks 1–2

    Code audit

    Every extension and custom module checked.

    Upgrade plan
  3. Weeks 3–8

    Upgrade

    Upgraded on staging, issues fixed, demoed weekly.

    Staging store
  4. Weeks 9–10

    Test

    Checkout, B2B, ERP and emails tested end to end.

    Test report
  5. Week 11+

    Release and care

    Released in a quiet window, then patches and support.

    Live store

Illustrative example

Worked example

A store two releases behind, with 60 extensions

A made-up but very typical case, not a client. A parts distributor runs Magento Open Source on an older 2.4 release, out of security support. It has 60 third-party extensions, 12 custom modules, a nightly CSV export to the ERP and a Luma-based theme scoring poorly on mobile. Here is the order we would work in.

  1. Weeks 1–2

    Audit and cut

    List every extension: used, unused, overlapping, abandoned. In cases like this a good share can usually go. Fewer extensions means a cheaper upgrade.

  2. Weeks 3–8

    Upgrade the core

    Move to a currently supported 2.4.x release with Composer, update or replace what’s left, and fix the custom modules against the new APIs.

  3. Weeks 7–10

    Replace the CSV

    Swap the nightly export for an API-based ERP sync with an error path, so stock updates every few minutes, not overnight.

  4. Weeks 10–16

    Then the front end

    Only now decide on Hyvä. Rebuilding the theme on a stable, upgraded core avoids doing the work twice.

The decision to stay or leave sits at step one. If the audit shows most customisation is no longer needed, we’ll compare this plan against a move to Shopify or BigCommerce before you spend anything on the upgrade.

Risks

Where Magento upgrades go wrong, and what we do about it

Risk

Running past end of support

Each 2.4.x release line has a published end-of-support date. After it, security patches stop, and payment providers may start asking questions.

How we handle it

We map your release against Adobe’s support dates in the audit, and plan the upgrade to land before the cut-off.

Risk

Extensions that never got updated

An abandoned extension can block an upgrade because it depends on a PHP version or library the new release drops.

How we handle it

We check every extension’s compatibility first, then update, replace or rewrite it as a small module of our own.

Risk

Indexers and cron out of step

Prices and stock look wrong on the storefront because indexers are stuck or cron stopped running after the move.

How we handle it

Indexers run on schedule, cron is monitored, and we alert if any index stays invalid for too long.

Risk

Search breaks after the upgrade

Newer 2.4 releases expect OpenSearch, and a mismatched search engine version takes catalogue search down.

How we handle it

We confirm the search engine version in the plan and test search, layered navigation and sorting on staging before release.

Pricing

Magento work and what it costs

Typical ranges. Your fixed quote follows the free audit, and nothing is billed before you agree it.

Audit

Upgrade or move audit

from $3,5002 weeks

  • Code and extension review
  • Upgrade versus re-platform costs
  • Written recommendation
Scope an audit
Most chosen

Version upgrade

from $15k6–14 weeks

  • Current 2.4.x release
  • Extensions updated or removed
  • Full regression test
Scope an upgrade
Rebuild

Hyvä front end

from $24k8–12 weeks

  • Hyvä theme build
  • Core Web Vitals budget
  • Checkout tested end to end
Scope Hyvä
Questions

About Adobe Commerce and Magento

Anything else, ask on the audit call.

Ask an engineer

Not answered here? Ask on the free 30-minute audit call. An engineer replies within one business day.

Quick facts

  • Based in Delhi, India Working across time zones, with written weekly updates.
  • Fixed quote first Nothing is billed before you agree it.
  • You own it The code, workflows and accounts are yours.
  • Stores and ERPs Shopify, BigCommerce, WooCommerce and Adobe Commerce, with NetSuite, SAP Business One, Odoo and Dynamics 365.
See all questions
What is the difference between Magento Open Source and Adobe Commerce?

Magento Open Source is the free, self-hosted edition. Adobe Commerce is Adobe’s licensed edition with additional features such as advanced B2B and cloud hosting options. Intelligize Digital works with both.

We are still on Magento 1. What now?

Magento 1 reached end of life in June 2020 and no longer receives security patches. Any move is effectively a rebuild, so Intelligize Digital compares Magento 2, Adobe Commerce and hosted platforms before you commit.

What is Hyvä?

Hyvä is an alternative front end for Magento 2 that replaces the default theme’s heavy JavaScript with a much lighter stack, which usually improves speed and makes theming simpler.

Should we upgrade or re-platform?

It depends on how much of your customisation you still need and what running Magento costs you each year. The audit puts both options side by side with costs and risks.

Can you integrate Magento with our ERP?

Yes. We sync orders, stock, prices and product data with SAP Business One, NetSuite, Business Central or Acumatica using a workflow engine, a custom integration or a proven connector.

How do we know if our Magento version is still supported?

Adobe publishes end-of-support dates for each 2.4.x release line. Intelligize Digital checks your exact version and patch level during the audit and tells you how long you have before security patches stop.

Is Intelligize Digital an Adobe partner?

No. Intelligize Digital is an independent agency and is not an Adobe Solution Partner. We upgrade, maintain and integrate Magento Open Source and Adobe Commerce stores, and work alongside your Adobe contacts where you have them.

Can we upgrade and move to Hyvä at the same time?

You can, but we usually upgrade the core first and rebuild the front end second, so each change is tested on its own. Doing both at once makes it harder to tell what broke when something does.

How do you connect Magento to an ERP?

Through the Magento REST API and webhooks or message queues on the store side, and the ERP’s own API on the other, with queueing, retries and a daily reconciliation. It replaces nightly CSV exports with near-real-time sync.

Glossary

Magento terms you’ll meet in an upgrade

Front endHyväTap for a short definition
HyväA lighter front-end theme for Magento 2 that replaces most of the default JavaScript stack, usually making pages much faster.
Front endLumaTap for a short definition
LumaMagento’s default demo theme. Many stores are still built on it, along with its heavy JavaScript.
ToolingComposerTap for a short definition
ComposerThe PHP dependency manager used to install Magento, its extensions and every upgrade.
Read the detail: Magento terms you’ll meet in an upgrade
DataIndexersTap for a short definition
IndexersBackground jobs that pre-calculate prices, stock and categories so the storefront can read them quickly.
InventoryMSITap for a short definition
MSIMulti-Source Inventory: stock held per source, such as warehouses or stores, and combined into stocks per website.
SpeedVarnishTap for a short definition
VarnishThe full-page cache that serves most storefront pages without running PHP at all.
SearchOpenSearchTap for a short definition
OpenSearchThe search engine Magento 2.4 uses for catalogue search and layered navigation.
StructureStore viewsTap for a short definition
Store viewsMagento’s website, store and store-view layers, used for brands, currencies and languages.
Keep reading

Related Magento reading

Upgrade, rebuild
or move?

Tell us your version, extensions and what hurts. An engineer replies within one business day with a first view.

We save what you type here so we can follow up if you get interrupted.
One file, up to 10 MB: PDF, Word, Excel, CSV, text, PNG or JPG.

An engineer replies within one business day.

What happens next

  1. An engineer replies Within one business day, by email.
  2. A free 30-minute audit On a call with an engineer.
  3. A fixed quote It follows the audit. Nothing is billed before you agree it.
All platforms

Get a quote. One form, one real reply.

Tell us what you are building or fixing. An engineer reads every request and replies within one business day, with a fixed scope, price and dates once we have talked.

Direct
[email protected]
Response time
Within one business day
Cost of asking
Nothing. The first 30-minute audit is free.

An engineer replies, not a form queue.