Your 5-Step Guide to Migrating from Cherwell to JSM in Under 6 Weeks

The End of Life (EOL) for Cherwell in 2026 is prompting IT teams to reevaluate their service management tools and make practical decisions about what comes next. If you're still running on Cherwell and considering a shift to Atlassian's Jira Service Management (JSM), the timeline might seem intimidating.

But here's the good news: with the right approach and the right partner, migrating from Cherwell to Jira Service Management can be completed in as little as six weeks without disrupting your daily operations.

This guide breaks down a realistic, step-by-step migration strategy that prioritizes efficiency, accuracy and business continuity.

Why Act Now?

Waiting until 2026 might appear convenient, but this delay can introduce avoidable risks: reduced vendor support, security vulnerabilities, lack of innovation, and limited access to skilled resources. Starting early gives you control over the timeline and the flexibility to adjust without urgency.

Whether you're looking to modernize your service desk, reduce long-term costs, or simply ensure business continuity, migrating from Cherwell to JSM can be completed in a structured and phased manner.

Here’s how to do it in five focused steps.

Step 1: Pre-Migration Assessment (Week 1)

The first step to any successful migration is understanding exactly what you're working with and where you're headed.

Key Activities:

• Inventory your current setup: Document all key elements in Cherwell, including ticket types, business rules, automations, workflows, dashboards, forms, and integrations.
• Identify business-critical components: Highlight which items must carry over to JSM and which can be retired or redesigned.
• Engage stakeholders: IT, HR, Finance and other service teams should be involved early to define success criteria and clarify usage requirements.
• Establish goals: Are you aiming to improve response time? Consolidate tools? Modernize the experience for end-users? Goals will shape your migration decisions.

Output: A migration blueprint that defines what needs to be moved, what can be improved, and who owns what.

Tip: A detailed assessment reduces the likelihood of surprises during the data and configuration migration stages.

Step 2: System Configuration & Design (Week 2)

Once you’ve mapped the existing environment, it’s time to design your future setup in Jira Service Management.

Key Activities:

• Set up JSM projects: Align request types, SLAs, queues, and user permissions based on your existing Cherwell workflows.
• Configure workflows: Use JSM’s visual editor to map out lifecycle steps for incidents, requests, changes and problems. Adapt existing Cherwell workflows where necessary.
• Recreate forms and request types: JSM allows for customized forms that match your service catalog needs.
• Establish automation rules: Use Atlassian’s no-code automation engine to replicate task assignments, escalations, and email notifications.

Output: A functional JSM environment that mirrors or improves upon your existing setup, ready for testing.

Tip: Focus on a minimal viable configuration first don’t try to migrate every feature or customization immediately. Build what’s essential, then optimize post-launch.

Step 3: Data Migration (Week 3–4)

This is where the actual transfer from Cherwell to Jira Service Management happens. Proper planning ensures your historical and active data comes over cleanly and remains usable.

Key Activities:

• Data export: Extract records from Cherwell including incidents, change records, service requests and user information. This can be done via SQL, API or export utilities.
• Data mapping: Define how fields from Cherwell map to fields in JSM. Some fields will align directly (e.g., priority, assignee), others may require reformatting or consolidation.
• Cleansing and validation: Remove obsolete or duplicate records. Ensure field consistency and format compliance.
• Data import into JSM: Use Atlassian’s import tools or third-party solutions to load clean datasets.
• Testing: Validate migrated data accuracy, relationships, attachments and permissions with sample records.

Output: Your data lives in JSM, accurately mapped and ready for use.

Tip: Not all data needs to move. Consider archiving older records that don’t require immediate access.

Step 4: User Testing & Training (Week 5)

Once your new environment is configured and populated, it’s time to get your users involved. Early engagement helps reduce resistance and builds confidence in the new system.

Key Activities:

• UAT (User Acceptance Testing): Select a group of real users—agents, approvers, and requesters—to run through common scenarios in JSM.
• Feedback loop: Capture issues, enhancement requests or confusion points and adjust configurations accordingly.
• Training sessions: Conduct focused training sessions using real workflows. Cover ticket management, request fulfillment, escalations and self-service features.
• Documentation: Provide quick reference guides and walkthrough videos for end-users and admins.

Output: An informed and confident team that knows how to use the new platform before go-live.

Tip: Train end users (requesters) as well—not just agents. Familiarity with the service portal is key to self-service success.

Step 5: Go-Live and Support (Week 6)

With testing complete and users trained, it’s time to launch Jira Service Management.

Key Activities:

• Go-live planning: Schedule your go-live for a time with minimal business disruption (weekends or low-volume days).
• Cutover process: Redirect service desk URLs, update internal documentation, notify teams, and deactivate Cherwell access where applicable.
• Hypercare support: For the first week post-launch, ensure your support team is available to answer questions, resolve access issues, and make quick adjustments.
• Performance monitoring: Review KPIs like ticket volume, resolution time, and portal usage to assess early adoption and address potential bottlenecks.

Output: Your Jira Service Management system is live and in active use, with real-time feedback and support in place.

Tip: Keep lines of communication open for feedback, but avoid making large post-launch changes without assessing long-term impact.

Key Success Factors

Completing a migration in six weeks is ambitious but entirely feasible if the following conditions are met:

• Clear scope definition: Know what’s critical to migrate and what can wait.
• Executive alignment: Leadership buy-in ensures resourcing, timing, and decision-making stay on track.
• Dedicated migration team: Assign a cross-functional team with clear roles—data, configuration, training, support.
• Agile execution: Work in sprints, and don’t wait until everything is perfect to move forward.
• Experienced partner support: Clovity’s team specializes in fast, low-risk Cherwell-to-JSM migrations with proven templates and tools.

What You Gain from Moving to JSM

Aside from moving off a legacy platform before EOL, here’s what organizations often find after migrating to Jira Service Management:

Final Thought

Migrating from Cherwell to Jira Service Management doesn’t have to be a massive, drawn-out project. With focused planning, realistic goals, and a strong execution strategy, it’s possible to complete the entire migration in under six weeks.

Doing so not only gets your organization ahead of Cherwell’s 2026 EOL, but also positions your ITSM practice for future growth—with a platform designed to keep up.

📧 Contact us at sales@clovity.com or visit 🌐 atlassian.clovity.com to get started today.