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 feature enables administrators to migrate existing target breakdown data to a new structure by running theMigrate BreakdownInterval To Checkinfrequencyscheduled job. The migration updates key fields such asCheck-in frequency,Actual to date, and breakdown-specific planned and actual values based on the current state of targets and their breakdowns.

    Show full answer Show less

    Migration Behavior for Different Breakdown Intervals

    The migration process varies depending on the original Breakdown interval and Review frequency settings:

    • Breakdown interval set to None:
      • The Check-in frequency is populated from the existing Review frequency.
      • Target breakdowns are created for targets with a review frequency other than None, even if the breakdown interval was None.
      • The Fortnightly review frequency is retained in check-in frequency, but no breakdowns are created since it is no longer supported; breakdowns will be created only after manual update.
      • If both review frequency and breakdown interval were None, no breakdowns are created.
    • Breakdown interval set to Quarterly or Yearly:
      • The Check-in frequency is set based on the existing review frequency.
      • Breakdowns are created based on the review frequency.
      • For targets with a yearly breakdown interval, quarterly breakdowns are created regardless of cumulative or non-cumulative type, and the target's value distribution is set to "Spread linearly across the time period (cumulative)".

    Key Outcomes

    • After running the migration job, target records have an updated Check-in frequency reflecting their prior review frequency.
    • Target breakdowns are created or updated accordingly to align with the new check-in frequency structure.
    • The Actual to date for targets and the Planned target value and Actual fields for breakdowns are populated based on the current actual values and historic data.
    • The migration preserves existing data integrity while transitioning targets to a new breakdown model, ensuring continuity in monitoring and reporting.

    Practical Example Scenarios

    • Monthly review frequency with breakdown interval None: Migration creates 12 monthly breakdowns with the current actual value populated in the relevant month and planned values distributed accordingly.
    • Quarterly review frequency with yearly breakdown interval: Migration creates quarterly breakdowns spanning the target duration, sets value distribution to cumulative linear spread, and populates actual values per quarter.

    This migration helps ServiceNow customers maintain accurate, actionable target tracking after upgrading, by automatically aligning old breakdown configurations to the new check-in frequency model and ensuring historical and current data are correctly represented.

    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 Actual 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.