Upgrade-Strategy: Washington-to-Xanadu

Upgrade-Strategy: Washington-to-Xanadu offers a roadmap to optimize your ServiceNow upgrade process. Immediate value or automatically installed may be prioritized for use sooner. If there are plugins, that are in the present release that comes in the late year (November), evaluate if it makes sense to install now or wait to train and test in Xanadu.

Transitioning from Washington Standard to Pro unlocks powerful new features, while the subsequent upgrade to Xanadu Pro brings game-changing enhancements. Did you know that 68% of IT leaders report faster issue resolution with predictive analytics, while 74% find proactive vulnerability management critical for operational security?

Your phased upgrade strategy—starting with a fast move of all production functionality from Washington to Xanadu—is both practical and efficient. To determine whether second-half-year plugins should be upgraded before moving to Xanadu or deferred, consider these guiding principles:

---

Guiding Questions for Washington Current Release Plugin Prioritization

Learn, Prepare, and Upgrade Tips

1. Critical Dependencies:
   • Does the plugin directly support core processes or critical functionality (e.g., ITSM, ITOM, or workflows)?
   • Is it a dependency for other features that you plan to implement in Xanadu?
2. Upgrade Complexity:
   • Does the plugin require significant customization or rework in the current environment?
   • Will configuring the plugin in Washington Pro cause redundant effort or conflict with Xanadu’s capabilities?
3. Value Timeline:
   • Will upgrading the plugin in Washington Pro deliver tangible value (e.g., improved performance or functionality) during the interim period?
   • Or would that value only be realized fully in Xanadu?
4. Plugin Stability:
   • Is the plugin known for stability and easy compatibility across versions, or does it have a history of requiring significant updates with major platform upgrades?
5. Training and Adoption:
   • Can teams fully adopt and use the plugin effectively in the short interim period before Xanadu?
   • Would introducing the plugin now create confusion or training overhead for users?

---

Decision Matrix for Washington Current Release Plugin

Category	Upgrade in Washington Pro	Wait for Xanadu Pro
Core Functionality	Upgrade if it enhances core ITSM/ITOM processes immediately.	Wait if the plugin has Xanadu-native improvements.
AI-Driven Features	Upgrade if Predictive Intelligence or Virtual Agent is a priority now.	Wait if AI functionality is limited in Washington Pro and better in Xanadu.
Automation Tools	Upgrade only if modular and extensible to minimize rework.	Wait if significant enhancements are coming in Xanadu.
Advanced Plugins (e.g., ITBM)	Upgrade if the plugin aligns with current project needs.	Wait if Xanadu offers a better integrated or enhanced version.
New Features (Experience)	Wait if not immediately needed, as implementation may differ in Xanadu.	Use Xanadu to maximize native experience-building capabilities.

---

Steps to Decide Washington Current Release Plugin Timing

1. Inventory and Assess Plugins
   • Create a list of active and inactive plugins in Washington.
   • Categorize each plugin by its purpose (e.g., ITSM, ITOM, ITBM, etc.).
   • Document dependencies, configurations, and usage.
2. Align with Business Priorities
   • Identify plugins critical for day-to-day operations (must upgrade in Washington Pro).
   • Highlight plugins with secondary or optional value (wait for Xanadu).
3. Review Plugin Release Notes
   • Check release notes for both Washington Pro and Xanadu for key differences.
   • Identify plugins with significant enhancements in Xanadu.
4. Test and Validate
   • Use functional testing in AutomatePro or ServiceNow to simulate plugin performance and compatibility in Washington Pro.
   • Validate whether upgrading now creates stable functionality.

---

Fast Phased Approach for Plugins

1. Phase 1: Immediate Upgrade (Washington → Pro)
   • Upgrade core plugins necessary for operational continuity.
   • Limit upgrades to plugins critical for reducing user or IT effort during the transition.
   • Conduct functional testing to validate plugin configurations.
2. Phase 2: Interim Optimization (3-4 Months in Pro)
   • Monitor and assess plugin performance.
   • Deploy additional configurations if needed to stabilize workflows.
3. Phase 3: Complete Upgrade (Xanadu Pro)
   • Reassess plugins delayed from Washington Pro.
   • Enable advanced or enhanced features as per business priorities.
   • Validate through end-to-end testing using tools like AutomatePro.

---

Key Takeaways Washington Current Release Plugin

• Upgrade plugins in Washington Pro if they deliver immediate, high-impact value or support critical dependencies.
• Defer plugins that are:
  • Non-critical for daily operations.
  • Likely to require reconfiguration in Xanadu.
  • Significantly enhanced in Xanadu.
• Use the interim period in Pro to stabilize workflows and plan for more advanced features in Xanadu.

This guide breaks down what’s automatically updated, what to deploy now, and which features are worth waiting for in Xanadu.

Other Upgrade-Strategy: Washington-to-Xanadu Resources

• AI experience Now Assist for Strategic Portfolio Management (SPM)
• CMDB Plan and Xanadu
• CMDB Collaborative Articles – LinkedIn
• CMDB Powered Digital Transformation – Dawn Christine Simmons
• CSDM and the CMDB Data Foundations Dashboards
• Discovery
• Exploring Now Assist for IT Operations Management (ITOM)
• How do AI agents enhance customer service management?
• ITOM Health
• ITOM Visibility
• New Features and changes by product in Xanadu
• Predictive Intelligence for Enterprise Architecture (formerly Application Portfolio Management )
• Release Notes Washington DC
• Release Notes Washington Available patches and hotfixes
• Release notes– Xanadu
• Release notes for upgrading from Washington DC to Xanadu
• Service Mapping
• ServiceNow Xanadu release
• SPM Xanadu release