About DQ job export
The DQ job export feature lets you migrate data quality jobs from Data Quality & Observability (self-hosted) to a Data Quality & Observability (cloud) environment. You select one or more jobs in Data Quality & Observability (self-hosted) and export them as a migration bundle. The bundle is then imported into Data Quality & Observability (cloud), where you map connections, resolve conflicts, and review the configuration before importing.
The migration moves job and dataset configuration only. It does not migrate historical job run data, results, execution logs, or connection credentials.
Who can export
Export requires the ROLE_ADMIN role. If dataset security is activated in Data Quality & Observability (self-hosted), you can only export datasets you have access to.
What is migrated
The following configuration entities are exported from Data Quality & Observability (self-hosted):
| Entity | Supported? |
|---|---|
| Job and dataset definition | Y |
| Connection mapping metadata | Y |
| Schema and table configuration | Y |
| Job options | Partially (see the log report for more information) |
| Adaptive monitors | Y |
| Advanced monitors | N |
| Custom rules | Partially (SQLf rules only) |
| Rule dimensions | Y (only when a matching Data Quality & Observability (cloud) dimension exists) |
| Schedules | Partially (see the log report for more information) |
| Notifications and alerts | Partially (email only) |
| Notification recipients | Y (only when the recipient email matches a Collibra Platform user) |
What is not migrated
If a feature is not supported in Data Quality & Observability (cloud), then it can't be migrated.
| Entity | Notes |
|---|---|
| Job run history | Previous Data Quality & Observability (self-hosted) job runs are not migrated |
| Job run results | Historical results, scores, and findings are not migrated |
| Execution logs | Past job logs are not migrated |
| Connection credentials | Passwords, usernames, and other sensitive values are not included in the bundle |
| License keys | Not included in the migration bundle |
| Unsupported monitor, rule, and notification types | Skipped with warnings; the rest of the job is still exported |
| Rule templates | Rule templates are not migrated |
Adaptive monitors
All supported Data Quality & Observability (self-hosted) adaptive monitor types are migrated:
-
Row count
-
Time check
-
Minimum value
-
Maximum value
-
Null check
-
Empty check
-
Unique check
-
Mean value
-
Shift check
Note Adaptive monitor breach alerts are not migrated.
Advanced monitors
Advanced monitors are not supported in 2026.06. The following types are skipped with warnings:
-
Shape detection
-
Outlier and record detection
-
Pattern detection
-
Duplicate detection
-
Validate source for reconciliation
If a job contains advanced monitors, the job can still be exported and imported. Unsupported monitors are skipped and reported as warnings in the import report.
Custom rules
Only SQLf custom rules are migrated. All other rule types, including simple rules, native rules, and simple checks (EMPTY, NULL, DATE, INT, DOUBLE, STRING, DATATYPE, CUSTOM), are skipped with warnings. The rest of the job is still migrated.
Rule dimensions
Rule dimensions are migrated when a matching Data Quality & Observability (cloud)dimension exists. Matching is case-insensitive. If no matching dimension exists in Data Quality & Observability (cloud), the rule is imported without a dimension assignment and a warning is reported.
Schedules
Unsupported schedules are skipped with warnings. The job is still exported, but without the unsupported schedule.
| Schedule frequency | Supported? |
|---|---|
| Hourly | Y |
| Daily | Y |
| Monthly | Partially (Data Quality & Observability (cloud) equivalent only) |
| Quarterly | N |
Notifications
Only email notifications are migrated. Slack and webhook notifications are skipped with warnings. If a recipient email matches an existing Collibra Platform user, the recipient is migrated automatically. Unresolved recipients are skipped with warnings and can be added manually in Data Quality & Observability (cloud) after import.
| Alert type | Supported? |
|---|---|
| Job failure | Y |
| Job complete | Y |
| Condition-based alerts | Y (only when compatible with Data Quality & Observability (cloud)) |
| Rule-status alerts | Y |
| Schema-change alerts | Y (only when the schema-change-monitor feature flag is activated in Data Quality & Observability (cloud)) |
| Adaptive monitor alerts | N |
File size
A Data Quality & Observability (cloud) admin can configure the maximum upload size for migration bundles using the maxmigrationfilesize admin config in Data Quality & Observability (cloud). The default is 15 MB. If the bundle exceeds the configured limit, the upload is rejected when importing into Data Quality & Observability (cloud). Set maxmigrationfilesize to "0" for no limit.