Generating a comparison transaction

Starting in release 2026.10, the stale data warning has been replaced by four specific notifications: Error, Warning, and two Info levels, which provide more precise guidance on data changes detected since the last comparison. The previous message key DMW_COMPARE_STATUS_CHANGED_MESSAGE has been removed. If you customized this message text, you must re-apply your customizations to the new message keys.

A comparison step must be performed and validated before importing the contents of the Inbound Migration file.

  1. Select Maintenance > System Administration > Data Migration > Migration Import > Inbound Migration.
  2. Locate your imported migration in the list.
  3. Click the Compare button next to the migration to be compared.

    • If a comparison is already scheduled or in progress for this migration, this message is displayed:

      Comparison for migration {X} has been scheduled already.

    • If scheduling is successful, this message is displayed:

      Scheduling comparison for migration {X} was successful.

  4. To review the results after the comparison is completed, select Maintenance > System Administration > Data Migration > Migration Import > Migration Import Transactions.
  5. Find the transaction of type COMPARE for your migration.
    Status types displayed can include:
    • COMPARED: Comparison found differences
    • EMPTY COMPARISON: No differences found
    • COMPARISON FAILED: An error occurred
    • COMPARED WITH WARNINGS: Comparison completed but with warnings
    Note: Warnings indicate conditions that don't block the migration but may impact the outcome, such as potential overwrites or configuration mismatches. Warnings are displayed on the Migration Import screen, Migration Transactions page, and Workmail notifications.
  6. Ensure that the comparison transaction is valid, meaning:
    • There were no errors during the comparison.
    • The comparison is not empty, unless you expect no changes.
    • The comparison is not outdated. Check for warnings about the comparison being older than the configured validity period.
    • The Migration Compare task now applies intelligent comparison behavior when evaluating Job Scheduler tasks. For example, if a Job Scheduler task runs after the comparison is generated, system-managed runtime columns such as Last Run Time and Next Run Time are ignored because they do not indicate a configuration change. As a result, the comparison report focuses on relevant configuration differences and provides clearer messages for updated or newly inserted rows.
    This table shows the notifications that can appear when data changes are detected after a comparison is generated. Use the notification severity and effect on migration to determine whether you can proceed with migration or should generate a new comparison. The notifications reflect changes that are relevant to the migration and identify when review is required before you continue:
    Notification Severity Effect on migration
    Significant data changes found within compare scope Error Blocks migration. You must run a new comparison before proceeding.
    Existing data updated since last compare Warning Does not block migration. Review the comparison results and run a new comparison if needed.
    Rows outside compare scope updated Info Does not block migration. You can proceed or run a new comparison.
    New rows inserted since last compare Info Does not block migration. You can proceed or run a new comparison.
    Note: The banner displaying the latest comparison timestamp is permanently visible on the Inbound Migration screen and cannot be dismissed.