The opportunity
A product metafield can point to a metaobject that references other metaobjects, product variants, files, images, videos, and market-specific values. Copying only the root value creates broken or cross-store references.
BizSidekick traverses the complete graph, maps stable product identifiers, creates a target-safe plan in dependency order, and requires approval before a migration with read-back verification.
How it works
- Confirm source, target, and root field — Verify stores, resource type, namespace, key, locale and market scope, and the required target behavior.
- Traverse nested dependencies — Read metafield definitions and values, metaobject definitions and entries, nested references, files, media, products, and variants.
- Map stable commerce references — Match products and variants by approved SKU, handle, or external identifier rules and leave ambiguous records unresolved.
- Prepare target definitions and files — Compare existing schemas, upload missing media, generate target-safe handles, and preserve alt text and content type.
- Preview ordered writes — Show definitions, files, entries, metafields, reference rewrites, conflicts, skips, and rollback identifiers.
- Confirm, apply, and verify — Require approval, create in dependency order, update the root target reference last, read back every record, and validate storefront rendering.
Safety boundary
The source remains read-only. Existing target definitions, entries, files, and product data are not overwritten without an approved conflict decision, and ambiguous SKU or variant mappings remain unresolved.
Expected outcome
A dependency graph, target mapping, approved migration preview, mock execution, and verified references
Try this prompt
Paste it into Claude to start this use case.
@BizSidekick Migrate this Shopify product metafield and its nested metaobject and media dependencies into the target store. Map products by stable identifiers, preview every definition, entry, file, and reference, and wait for confirmation.
