Magento 2 EAV cleanup: remove orphaned attributes, options and values safely
SKU: EAVCLEANER1
- Dry run first: a report on orphaned data without deleting anything
- Protection list for system attributes, which are never offered
- Backup file of the affected rows before every deletion
- Admin and CLI, with a log of every run
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 EAV cleanup: remove orphaned attributes, options and values safely
Anyone planning a Magento 2 EAV cleanup needs one thing above all: safety. This module finds orphaned attributes, unused options and values without a related entity and shows them to you first in a report only. Deletion happens only after a backup file and explicit confirmation.
After years of imports, module changes and range rebuilds, leftovers pile up in the catalog data model. They clutter the admin form, bloat tables and slow down imports and reindexing. The module works with dry run, a protection list for system attributes, batches and a log, in the admin and via CLI. We set it up in your shop.
Features for a Magento 2 EAV cleanup: the overview
Six building blocks that make tidying up controllable: look first, then back up, then confirm.
Scan and report
Lists orphaned attributes, unused options and unassigned values, with counts and examples.
Dry run
The default mode changes nothing, it just produces the report.
Protection list
System attributes and any attributes you protect are never offered for deletion.
Backup file
Before any deletion the affected rows are written to a file.
Confirmation and batches
Deletion only after explicit confirmation, in small batches.
Log
Every run traceable with time, admin user, scope and result.
Magento 2 EAV cleanup: what the scan finds
The scan looks for attributes that no longer belong to any attribute set, attribute options no product uses, values in the catalog tables whose product or attribute no longer exists, and values for store views that are gone. Every finding appears in the report with a count and examples so you can judge whether it is really superfluous.
- Attributes without an attribute set assignment
- Unused options of select attributes
- Values without a valid entity, attribute or store view
Safety mechanisms: several locks before a Magento 2 EAV cleanup deletes anything
System attributes sit on the protection list and are never offered; you can protect your own attributes as well. Before deleting, the module writes all affected rows to a backup file. Deletion happens only after you explicitly confirm, in batches your database can handle. Restoring from the backup file is possible via CLI.
- Protection list for system and custom attributes
- Backup file before every delete run
- Restore from the backup file via CLI
Admin and CLI: tidying in daily use and in the maintenance window
In the admin you see the report and start clean-up runs. For large data sets or maintenance windows there is a CLI command with the same checks. The log records who cleaned what and when. Important: test on a copy of your shop first. The module does not replace a database backup.
- Report and start in the admin
- CLI command for maintenance windows
- Log with admin user and time
When you should run a Magento 2 EAV cleanup
Three situations in which a Magento 2 EAV cleanup measurably calms your catalog.
After a platform move
After a migration from Magento 1 or a shop relaunch, old attributes and options remain that mean nothing in the new shop. The scan shows you what is left over.
After removing modules
When a module is removed, its attributes often stay in the database. The report reveals these remains and lets you remove them selectively, as far as they are no longer needed.
Before imports and upgrades
A tidy catalog makes imports faster and errors easier to find. Before an upgrade, less legacy data reduces the number of possible surprises.
Magento 2 EAV cleanup: manual SQL or with the module
The comparison shows why a Magento 2 EAV cleanup with a tool is safer than with self-written SQL.
| Aspect | Manual SQL | With the module |
|---|---|---|
| Overview | Write and verify your own queries | Ready report with counts and examples |
| Pre-check | Usually none | Dry run as the default mode |
| System attributes | Accidental deletion possible | Protection list, never offered |
| Backup | Has to be thought of separately | Backup file before every deletion |
| Load on the database | Large DELETEs at once | Batches of adjustable size |
| Traceability | None | Log with admin user and time |
How we set up the module for a Magento 2 EAV cleanup in your shop
Setup is done personally by Mironsoft. In a Magento 2 EAV cleanup care and safety come before speed.
1. Provide a copy
We start with a copy of your shop so that the first run has no consequences.
2. Installation
The module is set up, backup directory and batch size are defined.
3. Dry run and protection list
We go through the report together and enter attributes worth protecting.
4. Cleanup
Only then do we tidy the live shop, ideally in a maintenance window via CLI.
Magento 2 EAV cleanup compared with image cleanup and backups
The Mironsoft module Image Clean tidies up media files, specifically duplicate images on the file system. This module, in contrast, cleans entries in the catalog data model of the database. They complement each other without overlapping.
An honest classification matters to us: the module does not replace a full database backup. Create a backup before every deletion and test on a copy. The module's backup file covers only the deleted rows. No customer data is evaluated, only structural catalog data.
No download — personal setup instead
The module for a Magento 2 EAV cleanup is not listed here as a ready-made download file for self-installation. The purchase is a service commission: we get in touch after the purchase, set the module up, run a first dry run with you, and define the protection list before anything is deleted.
Frequently asked questions about a Magento 2 EAV cleanup
Everything important about safety, procedure, and how the purchase of the extension works.
Can the module delete important data by accident?
What counts as orphaned?
Could attributes used by other modules be deleted?
Does it work with very large catalogs?
Can I undo a deletion?
How can I find orphaned attributes in Magento 2?
How can I delete unused attribute options in Magento 2?
Is the module only meant for Hyvä shops?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 EAV cleanup – Mironsoft EAV Cleaner