Switching from old Change Management product to ServiceNow

[kelliclarke0226]

Soon we will launch Change Management in ServiceNow, moving from a homegrown application we've used for more than a decade. I've been thinking about HOW to make the switch from folks entering changes in the old system to the new, when changes have to be entered so many days in advance to not be Emergency for example.

We already have a few changes entered into our current system that are not slated to begin until a week or more that we should be "live" in ServiceNow.

My plan was that as we get close to the "go-live" date, any changes that I see entered into our old system, I could impersonate them in ServiceNow and go ahead and enter the change as they did in the old system. I could make sure that any reviews/approvals that happen in current system, are also completed in SN, so that when we actually go-live, the changes should be in the same place they were in old system, and they pick up exactly where they left off basically. New changes get created in new system, the only things not migrating are changes that should be  implemented prior to go-live, will need to be completed in the old system.

Does that make sense? Am I forgetting or overlooking something?  This is our very first instance of ServiceNow. Thank you in advance. 

[PratikshaKate]

Hi @kelliclarke0226 

Switching from a legacy change management system to ServiceNow Change Management involves migrating data, configuring workflows, and potentially customizing the platform to align with specific organizational needs. The process can be streamlined by leveraging ServiceNow's out-of-the-box features and adopting best practices for migration.
Here's a more detailed breakdown:
1. Assessment and Planning:
Evaluate Existing Processes:
Thoroughly analyze the current change management processes, workflows, and customizations in the old system.
Define Requirements:
Determine the specific requirements for ServiceNow Change Management, including desired workflows, approval processes, risk assessments, and reporting needs.
Identify Data to Migrate:
Determine which data from the old system needs to be migrated to ServiceNow, such as change requests, configuration items, and user information.
Plan the Migration:
Develop a detailed migration plan, including timelines, resource allocation, and testing procedures.
2. Configuration and Customization:
Utilize Out-of-the-Box Features:
Leverage ServiceNow's out-of-the-box functionalities for change management, including change models, workflows, and risk assessments.
Configure Workflows:
Configure workflows to match the defined change management processes, potentially using the Flow Designer for more complex automation.
Customize if Necessary:
Customize the platform to accommodate specific organizational requirements, such as unique change types or approval processes.
Integrate with Other Systems:
Integrate ServiceNow Change Management with other relevant systems, such as incident management, problem management, and configuration management.
3. Data Migration:
Clean and Prepare Data:
Clean and prepare the data from the old system before migrating it to ServiceNow.
Utilize Data Migration Tools:
Utilize ServiceNow's data migration tools or third-party solutions to efficiently migrate the data.
Validate Data:
Thoroughly validate the migrated data in ServiceNow to ensure accuracy and completeness.
4. Testing and Training:
Test Thoroughly:
Conduct thorough testing of the configured workflows, customizations, and data migration to ensure the system functions as expected.
Provide Training:
Provide comprehensive training to users on how to utilize ServiceNow Change Management, including the new workflows and processes.
5. Go-Live and Support:
Plan Go-Live:
Develop a go-live plan to transition from the old system to ServiceNow Change Management.
Provide Ongoing Support:
Offer ongoing support to users to address any issues and ensure a smooth transition.
Key Considerations:
Change Models:
ServiceNow Change Management utilizes change models to define different change types and their associated workflows.
Risk Assessment:
ServiceNow provides robust risk assessment capabilities to evaluate the potential impact of changes.
CAB Workbench:
ServiceNow offers a CAB workbench to facilitate efficient and effective Change Advisory Board meetings.
Automated Workflows:
Automated workflows streamline the change process, ensuring consistency and efficiency.
Integration Capabilities:
ServiceNow integrates seamlessly with other IT and business systems, enabling a holistic approach to change management.

Happy to help if you need any help into this.

Thank You 🙂

[Simon Hendery]

Hi @PratikshaKate 

Please don't copy and paste answers from ChatGPT. It adds no value to the Community. 

[kelliclarke0226]

This was not helpful or answering my actual question.

[Tosin D]

Hi @kelliclarke0226, I think you have a pretty solid plan. Do remember that training is also important for your users to understand how it will work in the new system.