Prepare
Create the new or temporary field structure without immediately removing the existing field.
SCHEMA MIGRATIONS
Your first schema decision shouldn't be your last.
Shopify intentionally locks some metaobject field properties after creation. That's safe for the platform. It's painful when your architecture evolves.
mozen provides a staged migration workflow for changes that would otherwise require manual reconstruction.
THE WORKFLOW
A migration, not a magic button.
mozen does not pretend schema changes are risk-free. It prepares the target structure, transforms existing values, checks dependencies, gives you a review step and verifies the result before cleaning up legacy fields.
Transform
Copy and translate existing entry values using an explicit transformation strategy.
Review
Inspect affected entries and scan the published Shopify theme for known references.
Cut over
Perform the destructive portion only after explicit confirmation.
Verify
Confirm migrated values before temporary or legacy data is removed.
EXAMPLES
Common dead ends, made navigable.
Single value → list
"Waterproof"becomes["Waterproof"]Field key rename
press_logobecomespublication_logoReference → list
One related product can evolve into several.
DEPENDENCY REVIEW
Theme-aware, not magically omniscient.
mozen can scan Shopify theme files for known references that may need to change. It cannot guarantee compatibility with headless storefronts, external applications or dynamic code it cannot statically understand.
That uncertainty should be visible before cutover.
3 references need review
- sections/press-grid.liquid High confidence
- snippets/card-press.liquid High confidence
- assets/press.js Review
CONSERVATIVE BY DESIGN
Stopping can be the correct result.
If mozen cannot establish a safe transformation path, the correct outcome is to stop and explain why.
Make schema changes less scary.
Move deliberately, understand dependencies, and verify what changed.