EAV Data Model

EAV stands for Entity-Attribute-Value. It models an entity, its attributes and their values separately, allowing different entities to have different attribute sets. Magento and Adobe Commerce use EAV for parts of their data model; not every field is stored in the same way.

In Magento, attribute metadata describes each field and its storage type. Values can be stored in type-specific backend tables, while static attributes use the entity table. The number of attributes is not the number of separate tables a product needs.

EAV gives you flexibility. Adding a new attribute doesn't require a schema change. You can have wildly different attribute sets for different product types without sparse tables. That's why Magento adopted it.

The trade-off is additional modelling and query complexity, which caching and indexing also affect. EAV does not mean every migration needs a custom export script: Adobe Commerce supports CSV product exports, including attribute and configurable-product data. Assess the exported relationships and target requirements before choosing tools.

When migrating Magento to Shopify Plus, map size and colour to suitable options, title and vendor to standard fields, and other attributes to appropriate tags, metafields or reusable metaobjects. The mapping decision should support the actual merchandising, filtering and integration requirements.

Work from the supported source export or API, then validate the target records. Do not infer Shopify’s internal database design from the fields exposed to merchants.

Frequently asked questions

What does EAV stand for?

Entity-Attribute-Value. It separates entities, attribute definitions and values so different entities can have different attributes. Magento uses type-specific storage for many attributes alongside static fields; it is not one separate table for every product attribute.

Why does Magento use EAV?

It lets merchants add attributes without schema changes and support very different attribute sets per product type.

How does EAV data map to Shopify?

Map attributes according to their purpose: standard fields, variant options, tags, metafields or metaobjects. Preserve identifiers and relationships and test the resulting filters and merchandising. A supported CSV export or API may provide the source data; custom scripting depends on the mapping requirements.

Related terms: Catalog Mapping, Metafields, Re-platforming. For hands-on help, see how Flux runs Shopify Plus migrations.

Shopify Plus development and AI search

We build Shopify Plus stores that customers and AI shopping agents can find, compare and buy from. 210+ stores since 2012.

Chosen by Shopify Plus brands worldwide.