Target breakdowns migration

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Target breakdowns migration

    This migration process is designed for ServiceNow administrators to transition existing target data when upgrading to the Zurich release. Specifically, it involves running theMigrate BreakdownInterval To Checkinfrequencyscheduled job, which consolidates values from theReview frequencyandBreakdown intervalfields into the newCheck-in frequencyfield on target records. Additionally, it populates theActuals to date,Planned target value, andActualfields on the target breakdown records based on current and historical target data.

    Show full answer Show less

    Key Features

    • Migration of frequency fields: Values from existing Review frequency and Breakdown interval fields are merged into Check-in frequency for targets.
    • Creation of target breakdowns: Depending on prior settings, target breakdown records are generated to reflect proper intervals (e.g., monthly, quarterly).
    • Handling targets with Breakdown interval set to None: Check-in frequency is populated from Review frequency. Target breakdowns are created if the Review frequency is anything other than None. Fortnightly frequencies are retained but do not create breakdowns as they are no longer supported.
    • Handling targets with Breakdown interval set to Quarterly or Yearly: Check-in frequency is set from Review frequency. Quarterly breakdowns are created even for Yearly breakdown intervals, and target value distribution is set to “Spread linearly across the time period (cumulative).”
    • Population of actual and planned values: The migration populates current actual values and planned target values on each breakdown, reflecting progress to date.

    Practical Implications

    After running the migration job, ServiceNow customers can expect:

    • Accurate and consolidated check-in frequencies on targets.
    • Automatically created target breakdown records aligned with existing frequencies, ensuring continuity of reporting and tracking.
    • Proper distribution of target values, even converting yearly intervals into quarterly breakdowns with cumulative spread when needed.
    • Up-to-date actuals and planned values populated on breakdowns, enabling precise performance monitoring.
    • Support for previously configured frequencies, with exceptions such as Fortnightly breakdowns which require manual update to create breakdowns.

    Example Scenarios

    • Monthly breakdown example: A target with Monthly review frequency and no breakdown interval will have 12 monthly breakdowns created with current actual values assigned accurately to the relevant month.
    • Quarterly breakdown with Yearly interval: A target with Quarterly review frequency and Yearly breakdown interval will have quarterly breakdowns created with cumulative target value spread linearly over the period.

    This migration ensures that after upgrading to Zurich, target tracking remains consistent and accurate without manual data re-entry.

    As an administrator, when you run the Migrate BreakdownInterval To Checkinfrequency scheduled job, the existing values in the Review frequency and Breakdown interval fields are migrated to the Check-in frequency field in the target records.

    The value in the Actuals to date field for the target and values in the Planned target value and Actual fields for the target breakdowns are populated based on the current actual value of the target and values in the existing target breakdowns.

    Target breakdowns migration for targets with breakdown interval set to None

    After running the job, the value in the Check-in frequency field for a target is populated based on the existing value in the Review frequency field of the target. If the existing value in the Review frequency field was set to any option other than None, then target breakdowns will be created for such targets based on the existing review frequency of the target. Even though Breakdown interval was set to None for a target, target breakdowns will be created for the target based on the existing review frequency of the target.

    The following table describes how the check-in frequency value is populated for targets with different values in the Review frequency and Breakdown interval fields.
    Table 1. Target breakdowns migration with breakdown interval set to None
    Review frequency (Before upgrade) Breakdown interval (Before upgrade) Check-in frequency (After upgrading and running the job)
    Yearly None Yearly
    Quarterly None Quarterly
    Monthly None Monthly
    Fortnightly None Fortnightly

    The Fortnightly option is retained and no target breakdowns will be created because the Fortnightly option is no longer supported.

    After the owner or a contributor of the target updates the check-in frequency for the target, the target breakdowns will be created accordingly.
    Weekly None Weekly
    Daily None Daily
    None None None

    In this case, no target breakdowns will be created.
    For example, consider a scenario where details of a target are as follows before upgrade:
    • The base value and target value of the target is 0 and 100, respectively
    • The review frequency is set to Monthly and Breakdown interval was set to None
    • The start date and end date of the target are 2024-01-01 and 2024-12-31, respectively
    • The current actual value of the target is 60 and the current month is August
    In this case, after running the scheduled job 12 monthly target breakdowns are created for the target and the current actual value as 60 is populated in the August monthly breakdown. Also, the planned target value is populated for each breakdown.

    Target breakdowns migration for targets with breakdown interval set to Quarterly or Yearly

    After running the job, the value in the Check-in frequency field for a target is populated based on the existing value in the Review frequency field of the target. Then, target breakdowns are created for the targets based on the existing review frequency of the target.

    The following table describes how the check-in frequency value is populated for targets with different values in the Review frequency and Breakdown interval fields.
    Table 2. Target breakdowns migration with breakdown interval set to Quarterly or Yearly
    Review frequency (Before upgrade) Breakdown interval (Before upgrade) Check-in frequency (After upgrading and running the job)
    Quarterly Quarterly Quarterly
    Quarterly Yearly Quarterly
    Note:
    For targets with breakdowns interval set to Yearly, irrespective of the target is of type cumulative or non-cumulative, after running the scheduled job quarterly target breakdowns will be created and the Target value distribution is set to Spread linearly across the time period (cumulative) for the target.
    For example, consider a scenario where details of a target are as follows before upgrade:
    • The base value and target value of the target is 0 and 80, respectively
    • The review frequency is set to Quarterly and Breakdown interval was set to Yearly
    • The start date and end date of the target are 2023-01-01 and 2024-12-31, respectively
    • The target is of type non-cumulative
    • The actual value achieved in each quarter is 10 starting from Q1-2023 till Q2-2024
    • The current total actual value of the target is 60 and the current quarter is Q2-2024
    In this case, after running the scheduled job 8 quarterly breakdowns are created and the Target value distribution is set to Spread linearly across the time period (cumulative) for the target. The current actual value for Q1-2023, Q2-2023, Q3-2023, Q4-2023, Q1-2024, and Q2-2024 quarterly target breakdowns are populated as 10, 20, 30, 40, 50, and 60, respectively. Also, the planned target value is populated for each breakdown.