Migration of resource plans, operational resource plans, and cost plans

  • Release version: Australia
  • Updated March 12, 2026
  • 4 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 Migration of Resource Plans, Operational Resource Plans, and Cost Plans

    This document outlines the process for migrating resource plans, operational resource plans, and cost plans to enhance project management in ServiceNow's Project Workspace. It emphasizes transitioning to attribute-based resource assignments, which facilitate better resource allocation and cost management for projects and demands.

    Show full answer Show less

    Key Features

    • Migrate Resource Plans: Resource plans are converted to resource assignments based on planning attributes such as Group, Skill, and Role. Only resource plans in certain states (Planned, Requested, Confirmed, Allocated, Rejected, Completed) are eligible for migration.
    • Mapping Status: Resource plan statuses are mapped to corresponding resource assignment statuses to maintain clarity during migration.
    • Operational Resource Plans: Similar migration logic applies for operational resource plans, transforming them into operational resource assignments, with only Allocated and Completed states eligible for migration.
    • Cost Plans Migration: Financial cost plans based on resource plans are migrated to attribute-based labor costs, considering Employee Type, Expense Type, and Role.
    • Maintain Allocation Contour: Existing allocation contours are preserved during migration to ensure uninterrupted project management and accurate resource capacity insights.

    Key Outcomes

    • Improved management of resource allocations and project financials through the use of Project Workspace.
    • Seamless transition to attribute-based resource assignments without the need for replanning or manual adjustments.
    • Enhanced clarity and consolidation of cost plans, resulting in better financial tracking and reporting.
    • Activation of scheduled jobs for efficient migration execution, ensuring all relevant resource and cost plans are processed.

    Migrate resource plans to resource assignments and the associated cost plans to attribute-based labor costs of your projects or demands and easily work on resource allocations using Project Workspace.

    Tip:
    Resource Managers are encouraged to view the Resource Management Workspace boot camp to learn about Resource Management Migration to the Next Experience.

    Resource plans to resource assignments

    Migrate all the resource plans of a project or demand to attribute-based resource assignments depending on the planning attributes to easily manage your projects on Next Experience using Project Workspace and Capacity Planning.

    Group, Skill, and Role are the primary attributes enabled for Resource Management depending on which the resource plans are migrated to resource assignments.
    Important:
    Resource plans in Planning, Requested, Confirmed, Allocated, Rejected, and Completed states are only migrated to Resource assignments. Resource plans in Canceled and In-progress states aren’t migrated.
    Let us see how the status of the resource plans is mapped to the status of resource assignments.
    Table 1. Status mapping between resource plans and resource assignments
    Resource plan status Resource assignments status
    Planned or Requested Unassigned
    Allocated Approved
    Confirmed Approved
    Completed Approved
    Canceled or In-progress Resource plan isn’t migrated
    Rejected Unapproved
    Migrating requested efforts of resource plans

    When a resource plan is migrated, a corresponding resource assignment is created based on the primary attributes from the resource plan. Resource assignments don’t support custom selection of allocation type and allocation spread.

    Resource assignments only support an even spread of resource allocations by default.

    The efforts of the resource plan in requested state are also migrated to resource assignments. For example, if a resource plan is in Requested state with 20 additional hours requested, but not yet approved, the new migration flow accounts for these requested 20 hours and the total efforts are reflected in the migrated resource plan. See the following screenshots for more details.

    Figure 1. Existing resource plan in requested state
    Classic ServiceNow view of a resource plan in Requested state.
    Figure 2. Monthly aggregates of migrated resource plan with requested allocations
    Monthly allocations view of resource assignment with requested efforts.
    With the migration of resource plans:
    • Resource plans in Planning or Requested states, resource assignments are created based on the planned dates and planned duration with their default state as Unassigned.
    • Allocation type is set to planned duration.
    • Allocation spread is always Even.
    • Existing resource allocations are deleted and created again to accommodate resource allocations with the resource name and planned duration.
    • The allocated costs and allocated hours are copied to planned costs and planned hours.
    • Actual hours for the resource plan in Confirmed and Allocated states are retained with the resource plans.
    Note:
    Only one resource assignment is created for every unique combination of primary attributes, Group, Skill, and Role, and one for every user if the resource plans are created with selected member preferences. After migration, if you create resource assignments with any of the existing combinations, the available resource assignments are updated with the new requests.
    Allocation contour while migrating to resource assignments
    The existing contour of allocations in resource plans is maintained while migrating to resource assignments.
    Maintaining the existing contour ensures that the planned effort, timing, and effort distribution remain consistent before and after migration. By carrying forward the same allocation contours, you can continue managing ongoing work without disruption, maintaining accurate capacity and utilization insights, and trust that financial and resource plans reflect your original intent. This seamless transition helps you adopt the workspace experience confidently, without the need to replan or manually adjust allocations.

    Migration of Resource plans to Resource assignments

    Resource plans in different states.

    Resource plans list.

    Resource plans migrated as resource assignments.

    Resource assignments list.

    Operational resource plans to operational resource assignments

    Operational resource plans also follow the same logic to migrate operational resource plans to operational resource assignments.
    Important:
    Operational resource plans in Allocated and Completed states are only migrated as Operational resource assignments.

    After migration, the Request type of operational resource plans is changed to Hours.

    Migration of Operational resource plans to Operational resource assignments

    Operational resource plan in Allocated state created for Demo GroupA.

    Operational resource plans form.

    After migration, you'll have the following Operational resource assignments for every member of the group.
    Note:
    The parent-child mapping is retained and you may see an additional resource assignment with an empty resource.

    Operational resource assignments view after migration from Operational resource plans.

    Migration of cost plans to attribute-based cost plans

    When resource plans of a project or demand are migrated to resource assignments, the corresponding financial cost plans based on the resource plans will be migrated to new attribute-based labor costs. Migrate resource plans related link trigger migrates the cost plans along with resource plans migration.

    Every resource plan has an associated a cost plan with Labor capex as the cost type. While migrating, the planning attributes of the resource plans are analyzed to create attribute-based cost plans for the unique combination of the three planning attributes enabled for financials (Employee type, Expense Type, and Role). After migration, there will be no one-to-one association between resource assignments and attribute-based cost plans.

    Note:
    If a resource plan isn’t associated with either Employee Type or Role, the migrated cost plans costs are consolidated into a single cost plan.

    The planned costs are moved to the new attribute-based cost plans while the actual costs remain on the existing cost plan records. The rate model values associated with project or a demand are considered to generate attribute-based labor costs.

    Migration of cost plans to attribute-based cost plans

    Cost plans associated with a resource plan.

    List of cost plans with accounted planned and actual expenses.

    Attribute-based cost plan Resource_Internal_Capex is created after migration.

    List of attribute-based labor costs capturing the aggregate planned costs.