Configure Data Filter

Configure Data Filter

Data Filter controls which records of a selected entity remain in the migration. Each visual rule uses Field -> Operator -> Value, and multiple rules inside one Entity Filter can be combined with AND or OR.

Configure a filter

1. Expand Data Filter.
2. Select an entity and click Add Filter.
3. Select the data Field belonging to that entity.
4. Select the Operator that should evaluate the field.
5. Enter the comparison Value required by that operator.
6. Click Add Rule to add another condition to the same Entity Filter, then use AND or OR to define how the conditions relate.
7. Repeat for other entities when additional record-level scope is required.

Example: filter Manufacturers

To migrate only Manufacturers whose names start with US_, configure:

Setting	Value
Entity	Manufacturers
Field	Name
Operator	Starts with
Value	US_

The generated expression is:

(name starts_with "US_")

To narrow the same Entity Filter further, add another rule with AND:

Setting	Value
Field	Created Time
Operator	Is after
Value	09/11/2001

For 9 November 2001, the combined expression is:

(name starts_with "US_" AND created_at after "2001-11-09")

The filter keeps only Manufacturers whose names start with US_ and whose creation time is after the example date.

Direct expression editing

Expression is generated automatically from the visual rules. Direct editing is available when a supported condition is easier to express manually.

When direct editing begins, the visual rule controls are hidden and the editor shows:

The visual rules are hidden because this expression is being edited directly.

Validate manually edited expressions

Direct expressions can introduce syntax or logic errors. Use the visual rule builder unless the expression syntax and resulting record scope can be validated confidently.

Operator reference

Label is the customer-facing operator name displayed in the dropdown UI. Operator Identifier is the underlying syntax used when manually writing or editing expressions.

text

Label	Operator identifier
Equals	equals
Does not equal	not_equal
Starts with	starts_with
Does not start with	not_starts_with
Ends with	ends_with
Does not end with	not_ends_with
Contains	contains
Does not contain	not_contains
Is in	in
Is not in	not_in
Is empty	empty
Is not empty	not_empty

number

Label	Operator identifier
Equals	equals
Does not equal	not_equal
Is less than	less_than
Is greater than	greater_than
Is less than or equal to	less_than_or_equal
Is greater than or equal to	greater_than_or_equal
Is in	in
Is not in	not_in
Is empty	empty
Is not empty	not_empty
Is zero	zero
Is not zero	not_zero

date

Label	Operator identifier
Equals	equals
Does not equal	not_equal
Is between	between
Is not between	not_between
Is before	before
Is after	after
Is empty	empty
Is not empty	not_empty

datetime

Label	Operator identifier
Equals	equals
Does not equal	not_equal
Is between	between
Is not between	not_between
Is before	before
Is after	after
Is empty	empty
Is not empty	not_empty

boolean

Label	Operator identifier
Is true	is_true
Is false	is_false

Common record-scope questions

Start with the Field choices actually available for the selected entity in the active migration. A business requirement is suitable for Standard Data Filter only when those fields and the supported operators can express the requirement without changing its meaning.

Requirement	Standard Data Filter is suitable when	Do not approximate the requirement with
Only active Products	An available Product field represents the exact active or saleable state required by the project.	A different visibility, stock, or publication field whose meaning has not been confirmed as equivalent.
Only recent Orders	An available Order creation date/time field can be evaluated with Is after or Is between using the agreed boundary.	An update timestamp when the requirement is based on when the Order was created.
Products from selected Categories only	An available Product condition represents the required Product-to-Category membership.	Product name, SKU, Category selection, or another field that does not prove Category membership.
Customers who placed at least one Order	An available Customer condition represents the required Customer-to-Order relationship or the approved equivalent.	Customer creation time, status, or another unrelated Customer field.
Products that are in stock	The project defines what in stock means and the available Product fields can express that exact rule, such as the required stock state, quantity rule, or location-aware condition.	A generic status rule when stock depends on quantity, stock management, or location.
Valid or unused Coupons	The project defines valid and unused, and available Coupon fields can represent every required condition, such as status, effective dates, or usage boundaries.	A single status or date field unless it fully represents the approved business rule.
Blog Posts published after a date	An available Blog Post field represents the actual publication time required by the project.	Created Time or Updated Time when the requirement is specifically based on publication time.

Use Custom Service when the required condition is not representable

A similar-looking field is not evidence that the rule is supported. If the active Data Filter does not expose the field, relationship, or logic required to express the condition exactly, document the requirement for Custom Service rather than substituting a different condition.

Verify the filter

Before continuing, read the generated expression from left to right and confirm that the selected Field, Operator, Value, and AND / OR logic describe the intended record scope. After a Demo or Full Migration, validate representative records on both sides of the boundary: records that should migrate and records that should be excluded.

If the migrated scope is broader or narrower than intended, review the field type, operator, comparison value, and rule combination before running the filter again. For a directly edited expression, also check the operator identifiers and grouping syntax. Requirements that cannot be represented safely with the supported operators should be reviewed for Custom Service rather than approximated with a different condition.

Rule order and removal

Rules inside an Entity Filter are evaluated from top to bottom. AND / OR controls how the rules in that filter are combined.

• Click x to remove an individual rule.
• Use the remove control for the Entity Filter to delete the entire filter group.

Next Steps

If Data Transformation is included, configure it next. Otherwise continue to the next Add-on shown in Add-ons, preserving the required processing sequence.