Reduction in ServiceNow customization costs
Decrease in maintenance costs
Substantial savings for the company
INDUSTRY
Sports
Tools USED
Jira Service Management, Confluence
Service Provided
JSM and Confluence Migrations
Duration
2 months
SHARE THIS STORY
Problem Identification
Varsity's reliance on ServiceNow for incident and change management, as well as document storage, is proving increasingly costly. Expanding ServiceNow's service management capabilities (available on platforms like JSM and Confluence by default) without resorting to third-party plugins is also becoming financially unsustainable.
Solution Development
Solution Implementation Steps:
1. Initial Assessment: Thoroughly analyze the client servicenow platform to inform JSM and Confluence setup. Define necessary environment configurations, including the number of projects, spaces and permission structures, aligning these with client business needs.
2. Pilot Migration: Migrate a small subset of data to validate Confluence configuration. Internally review results to identify and resolve any potential problems.
3. User Acceptance Testing (UAT): Migrate approximately 50% of the ServiceNow data to Confluence. Facilitate client validation and feedback, using this input to refine the system and optimize its alignment with business requirements.
4. Production Deployment and Ongoing Support: Following successful UAT, complete the full data migration to the production environment. Provide post-migration support to address any issues and ensure seamless operation.
Implementation
The solution was successfully implemented through the following steps:
1. Discovery:
- An in-depth analysis of the servicenow platforms was conducted, and findings were presented to the client. This included details on how the data would be represented in the new system. Feedback and necessary adjustments were incorporated based on client input.
2. Pre-Migration Setup:
- The confluence environment was set up and configured in alignment with the proposals outlined in the discovery phase.
- Python scripts were developed to export and transform data from servicenow into formats acceptable by JSM and Confluence.
3. Migration
- The migration process was carried out in three stages:
- Pilot Test Migration: A small subset of data was migrated to validate the JSM configuration and ensure everything functioned as intended.
- UAT Migration: Approximately 50% of the data was migrated to enable the client to validate the system and provide feedback. This phase allowed for refinements to ensure the solution met the client’s business requirements.
- Production Migration: Following successful UAT, the full data migration was completed.
4. Post-Migration Support:
- After production migration, ongoing support was provided to address any issues, ensure system stability, and optimize performance.
Results and Impact
The elimination of high ServiceNow customization and maintenance costs resulted in substantial savings for the company.
