How can I achieve the migration from the Legacy SharePoint Connector to the current Connector?

Background

Communardo provides 2 apps for embedding SharePoint contents into Confluence and vice versa:

• Legacy SharePoint Connector for Confluence

• SharePoint Connector for Confluence

The Legacy SharePoint Connector for Confluence is feature-complete and will not be developed further. Therefore we recommend using the SharePoint Connector for Confluence if you are working with a compatible SharePoint version. It can not only be used with SharePoint Online, but also SharePoint Server 2016 and 2019.

You may also refer to our official communication about the end of life of the SharePoint Connector for Confluence: https://www.communardo.com/sharepoint-connector-for-confluence-end-of-life/

Questions ans Answers

Q: Is there an automated migration path available?

A: No, there is no automated migration path available. You have to do it manually. Please refer to the instructions below.

Q: Is a migration always necessary?

A: No, it is not always really necessary. Increasingly, we find that companies are moving from older Server SharePoint instances to SharePoint Online. That process often does not include a migration, and the “old” SharePoint is used for existing projects while new data is created and stored in SharePoint Online. This leads to a scenario where both systems are used in parallel, requiring two different connector apps.

Instructions

To migrate the content, we recommend the following procedure:

1. Install the new SharePoint Connector app and apply a valid license.

2. Find out on which pages the macros of the Legacy SharePoint Connector app are used. There are different appoaches to achieve this, for example

   1. using the Macro usage app

   2. using the Confluence search with a keyword query with the keyword “macroName”

      1. for example “macroName:sp-link“

         Open

         

      2. the relevant macro names for migration are

         1. sp-link (SharePoint Document Link macro)

         2. sp-list (SharePoint List macro)

      3. with “macroName:sp-*“ you’ll get all Legacy SharePoint Connector app macro instances

3. Decide which pages are relevant for migration.

   1. If the amount of pages is too big to cover immediately (or at all), we recommend using the date of the last page update to determine relevant pages. You might decide that only macros on pages that were updated within the last x months will be migrated. You don’t have to be concerned about data loss, as the files will be available in your SharePoint, even if you decide against migrating any particular macro in Confluence.

4. For every relevant page

   1. For every Legacy macro instance place an instance of the according new SharePoint Connector macro.

   2. Configure it the same way as the old one.

      1. For the SharePoint Document macro you probably want to use the new “Preview” display option rather than the “Link” option.

   3. Check the result.

   4. Delete the old macro instance.

Related articles