Skip to main content

Magento & Adobe Commerce Maintenance

Magento rewards careful upkeep and punishes neglect

Magento 2 is powerful and complex: Composer dependencies, indexers, cron, search, caching and third-party extensions all have to work together. We keep that stack patched, consistent and documented.

Checkout testedStore healthy

Business impact

Why Magento stores need specialist maintenance

Magento is often chosen for large catalogues, complex pricing and B2B requirements. That flexibility comes with more moving parts than most e-commerce platforms, and more ways for them to fall out of step.

Security patches cannot wait

Magento has a history of serious vulnerabilities that attackers target to skim card details at checkout. Applying Adobe's security patches promptly is one of the most important protections a store has.

Upgrades get harder with time

Each skipped release widens the gap in PHP, OpenSearch, Composer and extension compatibility. Stores that fall well behind face a project rather than an update.

Background processes drive the storefront

Prices, stock, search results and catalogue changes depend on cron and indexers. When they stall, customers see wrong prices or missing products long before anyone reads a log.

Common issues

Problems we regularly solve

Stalled cron and invalid indexers

Cron jobs that stop running or overlap, leaving indexers marked invalid and product, price and stock changes stuck without reaching the storefront.

Search service problems

Elasticsearch or OpenSearch clusters running out of memory or disk, or version mismatches after an upgrade, breaking catalogue search and category pages.

Extension conflicts and rewrites

Third-party modules overriding the same classes through preferences and plugins, causing errors after upgrades or subtle checkout and pricing bugs.

Card-skimming injections

Malicious JavaScript inserted into the database, CMS blocks or design configuration to capture payment details, often going unnoticed for weeks.

Cache and full-page cache misses

Varnish or Redis misconfiguration, or blocks that are not cacheable, resulting in slow pages under load and high server usage.

Uncontrolled deployment practice

Changes made directly on production, missing static content deployment steps or the store left in developer mode, causing outages and slow pages.

What's covered

What's included in Magento maintenance

Magento maintenance covers the application and the services it depends on. For Magento 1 stores, which reached end of life in June 2020, we focus on risk reduction and planning a move to a supported platform.

Security patching

Monitoring Adobe security bulletins and applying security patches and patch releases through Composer, tested on staging before production deployment.

Version upgrades

Planning and executing upgrades within Magento 2.4.x, including PHP, OpenSearch, MySQL or MariaDB, Redis and Composer requirements, plus extension compatibility.

Cron, indexer and queue health

Monitoring cron schedules, indexer status and message queue consumers, and resolving backlogs that stop catalogue and order changes flowing through.

Search and caching stack

Keeping Elasticsearch or OpenSearch, Varnish and Redis correctly sized, configured and compatible with your Magento version.

Extension management

Reviewing third-party modules for support status, known vulnerabilities and conflicts, and updating or replacing them as part of upgrade planning.

Integrity and malware checks

Scanning files and database content for injected scripts, reviewing admin users and enforcing two-factor authentication. See malware detection and removal.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

Continuous

  • Uptime, checkout and search availability monitoring
  • Cron and indexer status monitoring
  • OpenSearch or Elasticsearch cluster health checks

Daily

  • Database and media backups
  • Exception and system log review for new errors
  • Message queue consumer checks

Monthly

  • Security patch review and staging deployment
  • Malware and injected-script scan
  • Admin user and integration token review
  • Maintenance report

Quarterly

  • Upgrade path and PHP compatibility review
  • Extension compatibility and support status audit
  • Test restore and performance baseline review

Our methodology

How we work

  1. 1

    Audit code and infrastructure

    We review the Magento version, Composer dependencies, custom and third-party modules, core modifications, server stack and deployment process.

  2. 2

    Establish a deployment pipeline

    Changes move through version control and a staging environment, with a repeatable sequence of composer install, setup:upgrade, di:compile and static content deployment.

  3. 3

    Patch and test on staging

    Patches and upgrades are tested against catalogue, search, cart, checkout, payment and admin workflows before production.

  4. 4

    Deploy with minimal downtime

    Production deployments use maintenance mode for as short a window as possible, scheduled for low-traffic periods, with backups and a rollback route ready.

  5. 5

    Monitor and plan ahead

    Post-deployment checks, ongoing background process monitoring and a forward plan for the next upgrade keep the store from falling behind again.

Business benefits

What you gain

Patched promptly

Security patches are tracked and scheduled as soon as they are released, reducing the window in which your store is exposed.

Accurate storefront data

Healthy cron and indexers mean price, stock and catalogue changes reach customers when they should.

Upgrades as routine, not projects

Keeping close to current releases helps keep each upgrade smaller and more predictable.

Repeatable deployments

A documented deployment process reduces downtime and the risk of human error during releases.

Better performance under load

Correctly configured Varnish, Redis and search services help the store stay responsive during campaigns.

Technologies supported

  • Magento Open Source
  • Adobe Commerce
  • Composer
  • OpenSearch
  • Elasticsearch
  • Varnish
  • Redis
  • RabbitMQ
  • PHP-FPM
  • MySQL / MariaDB
  • Nginx
  • Magento CLI
  • Git

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs Magento maintenance?

Mid-market and enterprise retailers

Stores with large catalogues, multiple store views or complex pricing that need specialist Magento knowledge.

B2B merchants

Businesses using company accounts, quotes, shared catalogues and ERP integrations on Adobe Commerce.

Stores inherited from another agency

Retailers who have lost their original developer and need someone to take ownership of an unfamiliar codebase.

Magento 1 stores

Businesses still on an end-of-life Magento 1 installation who need to reduce risk while planning a replacement platform.

Industry guidance: E-commerce

FAQs

Magento Maintenance: common questions

Do you support both Magento Open Source and Adobe Commerce?
Yes. We maintain Magento 2 Open Source and Adobe Commerce installations on your own hosting or cloud infrastructure. For Adobe Commerce Cloud, we work within Adobe's deployment tooling and support arrangements.
How quickly are Magento security patches applied?
We review Adobe security bulletins when they are published and schedule patches according to their severity and your plan's response targets. Every patch is tested on staging before production unless an emergency requires a different approach, which we agree with you first.
What access do you need?
SSH access to staging and production, Git repository access, a named Magento admin account and access to hosting or cloud consoles where relevant. Credentials are stored in a vault and access is reviewed regularly.
We are on Magento 1. Can you still help?
Yes. Magento 1 no longer receives official security patches, so we focus on reducing risk through hardening, monitoring and malware scanning while helping you plan a migration to a supported platform.
Are version upgrades included in maintenance?
Security patches and minor patch releases are part of routine maintenance. Larger version upgrades that require significant extension or custom code work are planned and quoted as separate projects so the scope is clear.
Do you need to put the store into maintenance mode?
Many deployments need a short maintenance mode window for database schema updates. We schedule these for low-traffic times, keep them as short as possible and tell you in advance.
Where can I read more about common Magento issues?
Our guide to common Magento maintenance problems explains the issues we see most often and how they are typically resolved.

Know exactly how far behind your Magento store is

Request a technical audit covering your Magento version, outstanding patches, extensions, cron and indexers, search and caching configuration.