Migration of resource plans, operational resource plans, and cost plans
Summarize
Summary of Migration of resource plans, operational resource plans, and cost plans
This guide explains how ServiceNow customers can migrate resource plans, operational resource plans, and associated cost plans from traditional formats to attribute-based resource assignments and cost plans. This migration facilitates managing resource allocations and project financials more effectively using the Project Workspace and Capacity Planning tools in the Next Experience.
Show less
Migration of Resource Plans to Resource Assignments
- Resource plans from projects or demands are converted into attribute-based resource assignments based on primary planning attributes: Group, Skill, and Role.
- Only resource plans in Planning, Requested, Confirmed, Allocated, Rejected, and Completed states are migrated; plans in Canceled or In-progress states are excluded.
- Status mapping ensures continuity, e.g., Planned/Requested become Unassigned assignments, Allocated/Confirmed/Completed become Approved, and Rejected become Unapproved in resource assignments.
- Each unique combination of Group, Skill, and Role creates a single resource assignment; for plans with selected member preferences, one assignment per user is created.
- Resource assignments do not support custom allocation types or spreads; allocation spread defaults to Even, and allocation type is set to planned duration.
- Existing resource allocations are deleted and recreated during migration to align with the new assignments.
Migration of Operational Resource Plans
- Operational resource plans in Allocated and Completed states are migrated to operational resource assignments.
- Post-migration, the Request type of operational plans changes to Hours.
- Parent-child relationships between operational plans and assignments are preserved, with some assignments possibly appearing without an assigned resource.
Migration of Cost Plans to Attribute-Based Cost Plans
- Cost plans associated with resource plans (typically Labor capex cost type) are migrated to attribute-based labor cost plans aligned with the planning attributes Employee Type, Expense Type, and Role.
- The migration consolidates costs if Employee Type or Role is missing, resulting in a single cost plan.
- Planned costs are transferred to new attribute-based cost plans; actual costs remain on the original cost plan records.
- Rate models for the project or demand are used to generate attribute-based labor costs.
- After migration, direct one-to-one links between resource assignments and cost plans no longer exist due to attribute consolidation.
Practical Steps for Customers
- Enable attribute-based resource assignments to manage effort requests for planning items.
- Create resource assignments to allocate team or individual capacity for projects or demands.
- Migrate operational resource plans to operational resource assignments to allocate capacity for operational tasks like meetings or training.
- Activate the "Migrate Resource Plans" scheduled job to automate migration of resource plans, operational resource plans, and cost plans to their attribute-based counterparts.
Why This Matters
The migration enables ServiceNow customers to leverage the Project Workspace and Capacity Planning applications more effectively by standardizing resource planning and financial tracking using attribute-based models. This modernization improves resource allocation accuracy, enhances visibility into project costs, and aligns with the Next Experience platform capabilities.
Effortlessly 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.
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.
| Resource plan status | Resource assignments status |
|---|---|
| Planned or Requested | Unassigned |
| Allocated | Approved |
| Confirmed | Approved |
| Completed | Approved |
| Cancelled or In-progress | Resource plan is not migrated |
| Rejected | Unapproved |
When a resource plan is migrated, a corresponding resource assignment is created based on the primary attributes from the resource plan. Resource assignments do not support custom selection of allocation type and allocation spread.
- 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 plans in Confirmed and Allocated states are retained with the resource plans.
Migration of Resource plans to Resource assignments
Resource plans in different states.
Operational resource plans to 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.
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.
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 to a resource plan.
Attribute-based cost plan Resource_Internal_Capex is created after migration.