Skip to Content
Glossary

Glossary

TermMeaning
TenantThe org that owns a set of migrations, mapping forks, and credentials. Every user belongs to one tenant.
MigrationThe long-lived workspace representing one merchant’s move.
Source platformThe system the merchant is migrating away from (Magento, Shopify-as-source).
DestinationThe Shopify store the merchant is migrating into.
ResourceA category of data being moved (product, customer, order, …).
RunOne execution of one or more phases.
Run itemThe per-resource record inside a run; carries phase, result, counts, errors.
PhaseExtract, transform, or load — the three steps of a run.
ExtractPulling rows from the source platform into Graftport.
TransformRunning the JSONata mapping over the extracted data, producing Shopify-shaped records.
LoadPushing the staged records to Shopify.
Extracted dataThe faithful copy of source rows as the source returned them.
Staged recordA Shopify-shaped payload, ready to load.
PendingA staged record whose payload hasn’t yet landed on Shopify (or has changed since last load).
MappingThe link between a (migration, resource) pair and a specific mapping version.
Mapping templateA named recipe scoped to a source platform + resource type. Default templates are global; forks belong to your tenant.
Mapping versionAn immutable snapshot of the JSONata text.
JSONataThe JSON query and transformation language used for mappings. See jsonata.org .
Conflict strategyWhat load does when a record already exists on Shopify — overwrite or skip.
Only-dirtyRun-time toggle that limits load to records with pending changes.
Field filterRun-time filter that restricts which fields a load updates per resource.
Dry runA run mode that does the work but doesn’t write the result anywhere.
Resync locationsA button that re-pulls Shopify locations for the destination store, used before splitting inventory.
Last updated on