Row filter
The Advanced load filter in the Start run modal loads only the records that match conditions you choose, instead of every staged record. Pick a field, choose how to compare it, set a value, and only matching records are sent during the load phase.
It is built for testing a slice: load just the first few products that have bundles, confirm they land correctly, then run the rest.
Setting a filter
In the Start run modal, with Load in the phase set, expand Advanced load filter. For each resource in the run you can add one or more conditions:
- Field — pick from the fields available on that resource. The list comes from your already-transformed records, so run a transform first if it looks empty.
- Operator — choose how to compare, such as equals, contains, greater than, exists, or is any of. The choices adapt to the kind of field you picked.
- Value — type what to compare against (skipped for operators like exists that need no value).
With more than one condition you can require all of them or any of them to match. You can also set a Load limit to stop after a set number of matching records per resource.
The footer summary shows a row filter badge (and a load N/resource
badge for a limit) whenever one is in effect, so you can confirm at a
glance before clicking Start.
What the filter applies to
- Load only. The filter decides which already-transformed records get sent to your store. It does not change extract or transform.
- Per resource type. A filter or limit applies to each resource
separately. A load limit of
5on a run with products and customers loads up to 5 of each.
A filter or limit is for testing, not a full migration. A limit can leave out records that others depend on — for example a bundle whose component products fall outside the limit — so those may not load cleanly. Use it to sample, then run again without it to move everything.
Good to know
- While a row filter is set, Only dirty records is turned off so your filtered selection stays the same each time you re-run it.
- The fields list is empty until a transform has produced records for that resource. Run extract and transform first, then filter the load.
- Pair it with resource scope to focus on a single resource while you iterate, or with Dry run to preview the matching set without writing to Shopify.