Jira Confluence to ServiceNow Migration

Precision Bridge supports the migration of Confluence Pages into a ServiceNow Knowledgebase. There is a template included specifically for this purpose that can be used to create a mapping project using:

File->New -> Project from Template -> Jira -ServiceNow -> Confluence Pages.

This project includes mappings for the two supported confluence tables Confluence Page and Confluence Comment.

Source Table Support

The following is supported for Jira Confluence as a migration source:

Confluence Page supports:

• Filtering on Space id, Article id, Title only is supported. If records need to be excluded from your migration using fields other than these, it is suggested you make use of the PERFORM_COND_ACTION Function to skip these records based on a comparison of the field with a value.
• Attachment Migration.
• Retrieval of the created by details and last updated details.
• Retrieval of the html body.
• Retrieval of the id/title of the most immediate parent and a list of all hierarchical parents.
• A 'From Previous Migration Set' inclusion filter. This allows the same set of migrated records to be updated in a subsequent mapping without redefining the filtering.
• Lookups are supported for Confluence Page and Confluence Space

Confluence Comment supports:

• Inclusion filtering, with the Confluence Page as the 'Parent'. This allows comments related to previously migrated pages to be extracted. Note that this inclusion filter is a mandatory requirement - Confluence Comments cannot be retrieved without reference to the parent pages.
• Retrieval of the created by details.
• Retrieval of the html body.

Limitations in Support

• No other confluence tables of fields are supported currently.
• Attachments are only supported for Pages.
• Retrieval of other content types (e.g. database/whiteboard) are not supported.
• Reference Mappings are not supported.

The Confluence to ServiceNow Migration Template

This template will migrate pages for a selected Confluence Space into a designated ServiceNow Knowledgebase. The source space and target Knowledgebase must be specified at runtime using the defined project variables.

Be sure you understand the points below and adjust the project to fit your requirements as needed:

• The template will only migrate content of type 'page'.
• Attachments related to the page will also be migrated.
• The Article Id field is set to the id of the confluence page to facilitate correlation between the source and target objects.
• The body of the article will be transformed to re-point embedded images to the ServiceNow attachments and to update inter-page links to re-point them to the ServiceNow pages, correlating using the Article Id.
• If links or attachments cannot be updated due to the item not being found on ServiceNow, warnings will be reported.
• Content comment will be added as feedback to the article.
• Parent/Child relationships between articles will be maintained if both parent and child pages are migrated.
• Article owners will be transformed to reference the same user in ServiceNow (correlating on the email address of the user)
• All pages/articles will be migrated as 'published'.