Migration to Resource Management

[Uncle Rob]

SCENARIO:  Moving from an old MS Project instance to ServiceNow.   Everything about Demand and Project is golden.  Resource management though....

I have my own opinions on this but I'm looking for a broader consensus.
What's the best strategy for migrating onto Resource Management when you did it in a prior system?

• Operational Plans only then only new demands/projects?
• Rebuilding all known resource plans from prior system into ServiceNow?
• Something in between?

[Namita Mishra]

Hi @Uncle Rob ,

My take is to migrate

1. Active demands & projects.

2. Selected closed demands / projects on which (in case) active demands / projects are dependent on

Now this approach raise questions where folks would also like to bring in closed demands / projects for last 2 -3 years (as per the audit policy).. This can be handled by using the previous application for audit demands / projects unless accessing previous instance / application is not a possibility.

3. Resources need to be in sync between two systems - obvious reasons

4. Regarding the resource plans, all active resource plans would be better to avoid duplicate manual effort in the new system.

5. You may also would like to see the attachments - may be linking to third party system so the attachments are accessible from new system. 

6. I am sure you might have taken care of areas like baselines, schedules and constraints as they are crucial.

Willing to see others suggestions. 

Thanks!

Namita Mishra

[Uncle Rob]

I'm aiming for a simpler model.  There is no dependency or audits in the picture and fail to see why closed demands/projects over the last 2-3 years even matter.
Why do the resource plans need to be in sync if the data is migrated to the new system?
I'm not sure what you mean by baselines and constraints.  Baselines are for the project and financials (customer is unwilling to use SPM financials) and constraints isn't a table I'm aware of.

Sorry, hope that doesn't sound too blunt.   Its just the way this whole thing is SUPPOSED to work still feels like a big black box.

[Mohd El Khatib]

Great question! Here’s how I would approach this:

1. Set Up Foundational Data – Ensure that key data elements like users, roles, skills, groups, and employee profiles are well-structured and up to date.
2. Establish Active Projects & Demands – Populate ServiceNow with current projects and demands, either through manual entry or by leveraging import sets for efficiency.
3. Create Resource Plans – Develop resource plans for ongoing projects and demands to get a clear view of resource allocation, availability, and capacity.

Would love to hear other insights—any recommendations or best practices?