Target breakdowns migration

  • Release version: Yokohama
  • Updated January 30, 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 update describes the process and effects of running theMigrate BreakdownInterval To Checkinfrequencyscheduled job, which ServiceNow administrators use to migrate existing target-related data fields to a new structure. Specifically, values from theReview frequencyandBreakdown intervalfields are consolidated into theCheck-in frequencyfield on target records, and corresponding target breakdown records are created or updated accordingly.

    Show full answer Show less

    Migration Details and Behavior

    The migration job affects targets differently based on their original Breakdown interval and Review frequency settings:

    • When Breakdown interval is None: The Check-in frequency is set to the existing Review frequency value. For Review frequencies like Yearly, Quarterly, Monthly, Weekly, and Daily, target breakdowns are created accordingly. However, the Fortnightly option is retained in Check-in frequency but does not create breakdowns since it is no longer supported. If both Review frequency and Breakdown interval were None, no breakdowns are created.
    • When Breakdown interval is Quarterly or Yearly: Check-in frequency inherits the Review frequency. Target breakdowns are created based on this frequency. For example, targets with Yearly Breakdown interval will have quarterly breakdowns created, and their Target value distribution will be set to “Spread linearly across the time period (cumulative)”.

    Data Population in Target Breakdowns

    The migration job also populates key fields in the target breakdowns:

    • Actuals to date: Populated based on the current actual value of the target and its corresponding time period.
    • Planned target value and Actual: Each target breakdown gets these values calculated and set according to the overall target data and distribution logic.

    Practical Example Scenarios

    • A target with base value 0, target value 100, Review frequency Monthly, Breakdown interval None, and actual value 60 as of August 2024 will have 12 monthly breakdowns created after migration, with the August breakdown reflecting the actual value of 60.
    • A non-cumulative target with base 0, target 80, Review frequency Quarterly, Breakdown interval Yearly, and quarterly actuals of 10 each will have 8 quarterly breakdowns created post-migration. The target value distribution is set to linear cumulative, and actuals accumulate quarterly (e.g., 10, 20, 30,...).

    Key Outcomes for ServiceNow Customers

    • The migration job simplifies target frequency fields into a single Check-in frequency, improving clarity and consistency.
    • Target breakdowns are automatically created or adjusted to reflect historical and current target progress, enabling more accurate performance tracking.
    • Customers should review and adjust Check-in frequency values post-migration, especially if the Fortnightly option appears, to ensure breakdowns are created as needed.
    • The migration supports both cumulative and non-cumulative targets, standardizing breakdown creation and value distribution.

    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.