Choose Start a run → Update only the fields I pick → Metafields. Metafields is available for products, customers, collections, and orders. For products, this includes metafields on their previously migrated variants.

Choose what to update

By default, Metafields updates the metafields included in your mapping. To narrow the selection, enter comma-separated Metafield keys, such as custom.material, custom.care. Only matching mapped keys are updated. Metafields outside the mapping or key selection are preserved.

Save your mapping changes and include Transform to prepare the new values. Include Extract if you need fresh source data. Choose Load to send them to Shopify. You can use the usual resource selection, row filters, load limit, and dry run controls.

If you need to revisit records whose mapped values have not changed, turn off Skip records already loaded.

Preserve existing Shopify edits

Select only Metafields to leave the record’s other Shopify fields alone. This updates existing records only: records and variants without saved Shopify IDs are skipped. When updating the same store you read from, Graftport uses the Shopify IDs from that source, including on the first run. Records without a usable identity cannot be updated. Titles, handles, prices, inventory, images, publication status, and order contents are not sent or changed by this selection.

Missing or blank mapped values do not delete existing metafields. The migration’s identity metafields are protected. A different existing metafield type or an unresolved reference blocks the record. Concurrent edits during a write are rejected rather than overwritten.

You can also select Metafields alongside other fields. Those other selections use their usual update behavior; new records get their full mapped values.

Review results

Results appear in the normal run details and record errors. Dry runs do not write to Shopify or read live metafield values; they summarize the selected records. A live run can partially succeed, so review failed records before retrying. Successful metafield updates do not mark unrelated mapped fields as fully synchronized.