Skip to content

Published by

The LEADLION team

Published on

Featured image for Magento maintenance: what it means and how it is done
Magento 2

Magento maintenance: what it means and how it is done

Like a car, a Magento store needs regular servicing to stay fast, secure and functional. Magento maintenance means all the recurring work that keeps the platform in good shape: applying security patches, optimising performance, cleaning up the database, backups and controlled upgrades. Without it, the risks grow quickly: security breaches, a slower site, lost conversions and high costs to put things right later.

What Magento maintenance is and what it is not

Two terms are often confused:

  • Maintenance mode is a technical Magento feature that temporarily takes the site offline while an update or a reconfiguration runs.
  • General maintenance is the ongoing process of looking after the platform: security, performance, databases, upgrades.

Maintenance mode lasts minutes. Real maintenance is a planned, monthly activity.

Maintenance mode in Magento, in brief

When you enable maintenance mode, Magento creates the var/.maintenance.flag file and redirects visitors to a Service Temporarily Unavailable page. The basic commands:

php bin/magento maintenance:enable
php bin/magento maintenance:disable
php bin/magento maintenance:status
php bin/magento maintenance:allow-ips <ip>

You can add your own IP to the allowlist so you can test the site while it is offline for the public. Magento switches to maintenance mode automatically during upgrades and some backup operations. A common mistake: leaving the site in maintenance mode after a deployment.

Types of Magento maintenance

Serious maintenance covers four areas.

Security

Adobe publishes security patches at least once a year for each supported version (in 2026: on 10 March and 12 May; Adobe’s release schedule, checked in October 2026), separately from the major upgrades. Patches are applied with Composer, first on staging and only then on production. We recommend the Adobe Security Scan Tool (free) for known vulnerabilities, 2FA on the admin and CAPTCHA on the API endpoints.

Performance

Regular Core Web Vitals audits (LCP, CLS, INP), image optimisation (WebP, lazy loading, CDN) and correctly configured caching (Varnish plus Redis or Valkey). On the frontend, Hyva has become today’s standard for speed, with Lighthouse scores well above those of classic themes.

Databases and cron

Indexing set to Update by Schedule for large stores, plus regular clean-up of the log tables, cron_schedule, expired sessions and abandoned baskets. Cron jobs have to be monitored, because jobs that fail silently are a common cause of problems.

Upgrades and updates

Adobe has moved to one major version a year, plus security patches between versions. The key difference:

  • Minor upgrade (e.g. 2.4.7 to 2.4.7-p3): low risk, apply it quickly.
  • Major upgrade (e.g. 2.4.6 to 2.4.9): needs planning, testing on staging and a dedicated budget.

Magento versions and end of support (2026)

The current stable version is Magento 2.4.9, released on 12 May 2026. If you are on 2.4.6, standard support ended on 11 August 2026: on Magento Open Source you no longer get official security patches, while on Adobe Commerce extended support runs until 31 August 2027 (Adobe’s support policy, checked in October 2026).

VersionReleasedEnd of support
2.4.5Aug 2022Aug 2025 (EOL)
2.4.6Mar 202311 Aug 2026
2.4.7Apr 202431 May 2027
2.4.8Apr 202531 May 2028
2.4.9May 202631 May 2029

If your version is EOL or close to EOL, migration is no longer optional. See Magento 2 migration.

Magento maintenance checklist

Daily

  • Uptime monitoring and alerts
  • Check for errors in var/log/
  • Confirm that the automatic backup has run

Weekly

  • Clear the cache and expired sessions
  • Check cron_schedule for failed jobs
  • Manual reindex if needed

Monthly

  • Check for and apply new security patches
  • Performance audit (PageSpeed Insights, GTmetrix)
  • Clean up log tables and check extensions for updates
  • Partial restore test from a backup

Quarterly

  • Full security audit (Adobe Security Scan Tool)
  • Review installed extensions and remove the ones you do not need
  • Optimise MySQL tables and run a disaster recovery test
  • Rotate admin passwords and API keys

Yearly

  • Upgrade to the new major version
  • Hosting and infrastructure audit
  • Review the backup and storage strategy

What Magento maintenance costs

The cost depends on how complex the store is, the version (Open Source or Adobe Commerce), how often you deploy and your SLA requirements. As a rough international benchmark:

TypeIndicative monthly costWhat it includes
Basic retainer500-1500 EURSecurity patches, small bug fixes, basic support
Full retainer1500-5000+ EURFull patching, monitoring, multiple development hours included

These figures are international benchmarks, not a quote. For the real price for your store, ask for an assessment through our Magento maintenance service.

Common mistakes

  • Too many extensions from too many vendors: each one adds compatibility risk and overhead.
  • Backups without a restore test: you find out too late, exactly when you need them.
  • Upgrades that skip intermediate versions.
  • Maintenance mode left on after a deployment.
  • Badly configured cron jobs that fail silently.
  • Ignored logs, with errors piling up.

Frequently asked questions

How often should Magento maintenance be done?

At least once a month to check for security patches and clean up the database. Daily for monitoring and automatic backups.

Can I do the maintenance myself?

The basics (cache, backups), yes. Security patches and major upgrades require solid technical knowledge or a specialised team.

What happens if I skip maintenance?

A higher risk of a breach, degraded performance, incompatibility with newer PHP and MySQL versions, lower rankings and high repair costs.

Does Magento 2.4.6 still get updates?

Standard support ended on 11 August 2026. On Magento Open Source it no longer receives security patches; on Adobe Commerce, extended support runs until 31 August 2027 (Adobe’s support policy). Migrating to 2.4.8 or 2.4.9 becomes essential.

Conclusion

Maintenance is not a cost but an insurance policy for your speed, security and sales. LEADLION manages the whole cycle: patches, performance, databases and upgrades, with testing on two environments (production and pre-production). See our Magento maintenance service or contact us for an assessment.