Migrating Knowledge data to Jira Confluence

When migrating knowledge data to Jira Confluence, you can migrate into Spaces, Pages and Comments.

It is recommended that the forms are mapped in the order of Space, Page and Comment as seen here:

If you are migrating from ServiceNow, you can build your migration project from the template provided (New > Project From Template > Service Now -> Jira > Knowledge).

You can optionally restrict the knowledge articles migrated to Confluence pages to only those for the spaces being migrated by using the Filter by Inclusion option of the Source Filtering for the Page mapping. 

Note that if you use this option to restrict the migration of pages to the migrated spaces, pages will only be migrated for any Spaces that are created in the migration, not for any that already existed.

To create the page in Confluence the Space Id field must be mapped. This can either be mapped using an Assignment mapping type to hard code it, a Value Mapping to map from a source field value to Space Id or if the Space Id in Confluence is not known, you can use a Lookup mapping to lookup the id based on the name.

Once the lookup is defined, you can specify the Lookup Query in the Lookup Mapping for the Space Id field.

If you are migrating from knowledge articles from Service Now to Confluence, it is recommended to use the JIRA_REPLACE_SNOW_IMG_TAG function to amend image links in the knowledge article body.

It is recommended that you do configure the Filter By Inclusion in the Source Filtering in the Comment mapping to only migrate comments for pages that are migrated.