Import & export metafields with CSV

When CSV is the right tool

Use CSV when you need to create or update many metafields at once, migrate from another system, or apply Health scan results with an import-ready file.

Live edit in Admin is better for a handful of values. CSV is better when the work is repetitive or catalog-wide.

• Bulk create or update metafields on products, variants, and other supported resources
• Export a structured snapshot for backup, audit, or offline review
• Pair with Product Data Health downloads when you are closing coverage gaps

How import and export work in the app

From Bulk Import/Export in the app, start an import or export job, choose the resource type, and provide a CSV (or download one). Jobs run in the background so large catalogs do not block Admin.

You get status, logs, and—when rows fail—files that help you fix and retry. On higher plans, unlimited bulk and backups make large runs safer to reverse.

Practical tips

Start with a small export of one resource type so you can see the column layout before a full import.

Keep namespace and key consistent with your metafield definitions. Wrong keys create new fields instead of updating existing ones.

After a Health scan, use the generated CSV where available, then import only the rows you intend to change.