> For the complete documentation index, see [llms.txt](https://docs.valtimo.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valtimo.nl/configuration-guides/cases/migration/conditions.md).

# Conditions

Conditions on the **General** tab of a migration plan decide which cases the plan migrates. A case is migrated only when all conditions hold. Cases that do not match are left to other plans.

Leave the conditions empty to apply the plan to every case on the source version.

***

## Configuring a condition

{% stepper %}
{% step %}
Open the plan editor and go to the **General** tab
{% endstep %}

{% step %}
Under **Conditions**, add a condition and fill in its field, operator, and value

<figure><img src="https://3330064618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq5dx9HWFJGshztp4binE%2Fuploads%2Fgit-blob-d2a8daa674218fc4e9334caddc21a847cf7984fd%2F04-conditions.png?alt=media" alt=""><figcaption><p>Conditions and operators</p></figcaption></figure>
{% endstep %}
{% endstepper %}

A condition consists of a **Field** (a value on the case, such as its status or a field in its data), an **Operator**, and a **Value**. A case whose value cannot be read does not match.

The Field column has a **Dropdown** / **Manual** toggle. Leave it on **Dropdown** to pick a field from the case's data model, or switch to **Manual** to type a path the dropdown does not offer, such as `case:sequence`.

| Operator             | Matches when                                                                                                                  |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| `==`, `!=`           | The field is (not) equal to the value                                                                                         |
| `>`, `>=`, `<`, `<=` | The field is greater or smaller than the value. Numbers are compared as numbers, anything else alphabetically                 |
| `in`                 | The field equals one of several values. Enter the values separated by commas, for example `in-behandeling,wacht-op-klant`     |
| `contains`           | The field contains the value: one of the entries when the field holds a list, part of the text when it holds a single value   |
| `exists`             | The field has a value at all. Leave the value empty, or enter `false` to match only cases where the field is empty or missing |

***

## Combining conditions with groups

Conditions listed one after another must all hold. To express an either/or, add a **group**. Each group has a **The group holds when** selector, set to either **Any of these hold** (OR) or **All of these hold** (AND). A group can contain other groups, so conditions can be combined to any shape.

{% stepper %}
{% step %}
Under **Conditions**, click **Add group**
{% endstep %}

{% step %}
Set **The group holds when** to **Any of these hold** or **All of these hold**
{% endstep %}

{% step %}
Add conditions, or further groups, inside it

<figure><img src="https://3330064618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq5dx9HWFJGshztp4binE%2Fuploads%2Fgit-blob-aeaa96a69cf0491ce6c09cc8969d9d0d1b67a25c%2F05-condition-group.png?alt=media" alt=""><figcaption><p>Nested condition groups</p></figcaption></figure>
{% endstep %}
{% endstepper %}

A group must contain at least one condition, and groups may be nested up to ten levels deep.

<details>

<summary>Example: a nested combination in the plan JSON</summary>

The combination "status is `in-behandeling`, and either the case is marked urgent or (the amount is at least 1000 and a file number is present)" reads as follows in the **JSON editor** tab:

```json
"conditions": [
{"path": "case:internalStatus", "operator": "==", "value": "in-behandeling"},
{
"anyOf": [
{"path": "doc:/spoed", "operator": "==", "value": true},
{
"allOf": [
{"path": "doc:/bedrag", "operator": ">=", "value": 1000},
{"path": "doc:/dossier", "operator": "exists"}
]
}
]
}
]
```

</details>

{% hint style="info" %}
Building block migration plans have no conditions. They apply to every building block instance the case migration brings onto the plan's version. See [Building blocks](/configuration-guides/cases/migration/building-blocks.md).
{% endhint %}