Resources

A resource is a category of data that moves as one unit. Graftport supports nine today:

Resource	Source examples	Notes
Product	catalog items + variants	Includes options, images, metafields. The richest mapping.
Customer	accounts, addresses	PII; opt-in.
Collection	manual + smart collections	Linked to products by handle.
Discount code	promo codes	Mapped to Shopify price rules + discount codes.
Gift card	issued gift card balances	Money; opt-in. Activated on Shopify side.
Order	historical orders + line items	Heaviest resource. PII + money; opt-in.
Blog	blog posts and articles	Content migration only — not theme.
Market	regional stores	Shopify Markets equivalents.
Redirect	URL redirects	Path-based, source `from` → destination `to`.

Enabling a resource

Resources are enabled per migration, not globally. Enabling does three things:

Adds the resource to the migration’s Resources list.
Pins a mapping — either the current default template version or a tenant-owned fork.
Tells future runs that this resource is part of the work to do.

Disabling later doesn’t delete the resource’s data — it just stops it being included in new runs. Re-enable to pick up where you left off.

Resource ordering at load time

When a load runs, Graftport pushes resources in a sensible default order: collections before products that reference them, customers before orders, and so on. You don’t pick the order — it’s enforced automatically.

If you start a run that only does extract or transform, the order doesn’t matter because nothing is written to Shopify.