migration from Jira / Confluence to ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi All -
we are planning to do the migration from JIRA and Confluence to ServiceNow, i would like to know if anyone has completed it in past and any suggestions, lesson learned, how to start and where to start planning it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @Learner-in-Prog,
Hi there,
Planning early makes a big difference with this kind of move. I’d start by looking at:
- Defining exactly what data needs to migrate (incidents, knowledge, attachments).
- Mapping workflows between Jira and ServiceNow carefully.
- Preserving historical comments and relationships.
- Planning a phased vs. big-bang migration approach.
In your case, you may want to explore OpsHub Migration Manager (OMM), a ServiceNow Partner. It supports phased or full migrations, preserves comments, attachments, and field mappings, and ensures no downtime or data loss.
Hope it helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi, @Learner-in-Prog,
If you’re moving from Confluence to ServiceNow, the standard KB can be limiting for preserving structure and collaborative content.
We just published Documate on the ServiceNow Store to solve this.
It is a direct alternative to Confluence operating natively within the platform.
- It can import spaces directly from Confluence while maintaining the original formatting and hierarchy.
- It eliminates the manual work of forcing complex, collaborative documents into the static KB model.
Here is a short video showing how the Confluence import to Documate works: https://youtu.be/mAoa3eYVsbE
