Matrixify can import and export metaobject entries — the actual data records — but it does not support metaobject definitions. This distinction matters: definitions are the structural templates that describe what fields a metaobject has, what types those fields accept, and what capabilities are enabled. Without the definition, you can’t create entries.
Altera supports full import and export of metaobject definitions.
What Are Metaobject Definitions?#
Metaobject definitions are custom data structures you create in Shopify under Settings → Custom Data. They work like database table schemas — each definition specifies:
- Name — the type name (e.g., “Authors,” “Size Charts,” “FAQs,” “Ingredients”)
- Fields — each with a name, key, data type (text, rich text, image, product reference, etc.), and optional validations
- Capabilities — whether entries can be published/drafted, accessed via the Storefront API, or rendered as web pages with URL handles
- Access controls — who can read or write entries of this type
Metaobject definitions are not the same as metaobject entries. A definition is the blueprint — it says “an Author has a Name (text), Bio (rich text), and Photo (image).” An entry is an actual author like “Jane Smith” with her specific bio and photo.
What Matrixify Does (and Doesn’t Do)#
Matrixify can:
- Export metaobject entries to Excel/CSV
- Import new entries, update existing entries, or delete entries in bulk
- Filter exports by definition name, display name, or update date
Matrixify cannot:
- Export metaobject definitions (the structure/schema)
- Import or create metaobject definitions
- Migrate metaobject definitions between stores
- Manage definition capabilities, field configurations, or access controls
Matrixify’s documentation states explicitly: “Each Metaobject entry is linked to a specific Metaobject definition. So those definitions do need to exist in the store before importing entries.”
Why This Matters#
When migrating a Shopify store, metaobject definitions must exist in the target store before you can import any entries. If your store uses metaobjects for content types like authors, FAQs, size charts, ingredients, or custom sections, you need to recreate every definition manually — including all field names, types, validations, and capability settings.
For stores with complex content models using many metaobject types, each with multiple fields and cross-references, this manual recreation is time-consuming and easy to get wrong. A missing field or wrong type will cause entry imports to fail.
How Altera Handles Metaobject Definitions#
Altera treats metaobject definitions as a first-class data type. You can:
- Export all definitions with their complete field configurations, validations, and capabilities
- Import definitions using MERGE, NEW, DELETE, or REPLACE commands
- Transfer definitions between stores — field references to other metaobject types export as portable type handles instead of store-specific IDs
- Handle self-references and cross-references — definitions that reference themselves (e.g., a Category with a “Parent Category” field) or other definitions in the same file import reliably in a single pass
- Manage URL handle capabilities — control whether a metaobject type generates web pages with the “Capability: Online Store URL Handle” column
This means you can export your entire content model from one store, import it into another, and then import your metaobject entries — all using spreadsheets, no manual setup required.
Frequently Asked Questions#
Does Matrixify support metaobject definitions? No. Matrixify supports metaobject entries only — the data records. It cannot import, export, or manage metaobject definitions — the structural templates that define each metaobject type’s fields, types, validations, and capabilities.
Can I use Matrixify to migrate metaobject definitions between stores? No. You would need to manually recreate each metaobject definition in the target store before importing entries with Matrixify, or use a tool like Altera that supports definitions as a data type.
What happens if I try to import metaobject entries without definitions? The import will fail. Shopify requires a matching metaobject definition to exist before entries can be created. Matrixify will return errors for any entries whose definitions are missing.
See our full Altera vs. Matrixify comparison for a breakdown of all the differences between the two tools, or check the FAQ for more common questions.
