Upgrading a Confluence instance from 2.7.2: Issues with plugins and content.
Asked by Tihomir Nikolov _Nemetschek Bulgaria_:

Hi, all  

We are trying to upgrade a client's system from Very ancient version of Confluence ( 2.7.2 )  

On the system there are lots of plugins that had totally changed in the years.  

As far as the database is huge, the question is if there is an automated way for data migration, compatible with an actual plugin version. The key points are tables and calendars.  

Here is the list with the plugins:  

<br />

Adaptavist Advanced Search Plugin Version: 1.0.4  
Adaptavist Content Formatting Macros Plugin Version: 1.6.9  
Adaptavist Rate Macro Plugin Version: 2.0.2  
Advanced Macros Plugin Version: 1.3  
Attachment Extractors Plugin Version: 1.4  
Basic Macros Plugin Version: 1.3  
Booking Plugin Plugin Version: 1.4.0  
Cache Plugin Plugin Version: 3.2.1  
Calendar Plugin Plugin Version: 2.6.1  
Chart Plugin Plugin Version: 1.11  
Clickr Theme Plugin Version: 1.5  
Code Macro Plugin Version: 1.4  
Compatibility Macros Plugin Version: 1.3  
Confluence Atlassian Plugin Repository Plugin Version: 2.0.13  
Confluence Attachments Plugin Plugin Version: 2.10  
Confluence Blogging RPC Plugin Plugin Version: 1.2.4  
Confluence Classic Theme Plugin Version: 1.3  
Confluence Contributors Plugin Plugin Version: 1.1.3  
Confluence Remote API Plugin Version: 2.7.2  
Confluence Usage Stats Plugin Version: 0.8  
Create Page Macro Plugin Version: 1.2.1  
Custom Space User Management Plugin Plugin Version: 2.0.5  
CustomWare Composition Plugin Plugin Version: 2.3.5  
CustomWare Visibility Plugin Plugin Version: 1.8.0  
Dashboard Macros Plugin Version: 1.3  
Dynamic Table Macros Plugin Version: 1.2  
Dynamic Task List 2 Plugin Plugin Version: 2.2  
Dynamic Task List Macros Plugin Version: 1.8  
Excel Plugin Plugin Version: 3.6.0  
Form Mail NG Plugin Version: 1.2.2  
French language pack Plugin Version: 1.5  
German language pack Plugin Version: 1.1  
Google Calendar Plugin Plugin Version: 1.4  
HTML Macros Plugin Version: 1.3  
IM Presence NG Plugin Plugin Version: 2.3  
Information Macros Plugin Version: 1.0  
JIRA Macros Plugin Version: 2.4.1  
Layout Macros Plugin Version: 1.1  
Left Navigation Theme Plugin Version: 1.5.1  
Linking Plugin Plugin Version: 2.6.8  
Live Search Macros Plugin Version: 2.6  
Macro usage stats Plugin Version: 1.0.4  
Mail Page Plugin Plugin Version: 1.5  
Navigation Plugin Plugin Version: 1.11  
Office Connector plugin Plugin Version: 1.4.1  
Page Information Tools Plugin Version: 1.2.9  
Page Tree Plugin Version: 1.3  
Pagetree Search Plugin Version: 1.3.2  
RSVP Plugin Plugin Version: 1.6.3  
Redirection Plugin Plugin Version: 2.4.0  
SQL Plugin Plugin Version: 3.5.0  
Scaffolding Plugin Plugin Version: 2.7-dr9  
Social Bookmarking Plugin Plugin Version: 1.2.1  
Survey Macros Plugin Version: 1.1.8.6  
Table Plugin Plugin Version: 3.4.0  
Table of Contents Plugin Plugin Version: 2.4.11  
Tabular Metadata Plugin Version: 2.7  
Task List Macros Plugin Version: 3  
TinyMCE Editor Plugin Plugin Version: 2.11  
Tracking Plugin Plugin Version: 2.4.1  
User Listener Plugin Version: 2.3  
WebDAV Plugin Plugin Version: 1.2.3  
Word Plugin Plugin Version: 3.0.1  


Answers:
author: Deividi Luvison
body: Hi Tihomar,

Replying to your question:
> As far as the database is huge, the question is if there is an automated way for data migration, compatible with an actual plugin version. The key points are tables and calendars.

Sadly nope, the only thing you can do is to upgrade Confluence to it's bridge versions as per [this](https://confluence.atlassian.com/display/DOC/Upgrading+Confluence) page.

Another advice is to set up a [Confluence Test Instance](https://confluence.atlassian.com/display/DOC/Migrating+Confluence+Between+Servers#MigratingConfluenceBetweenServers-HowtoCreateaTestorDevelopmentSite) so you can avoid production downtimes during the process, since we are dealing with an ancient version there's no guarantee that everything will run smooth.

Regarding your plugins, my suggestions is that you also run the[Compatibility checker](https://confluence.atlassian.com/display/CONF43/Checking+Plugin+Compatibility+for+Confluence+Upgrades) prior each bridge version upgrade (I don't know for sure if that is available for version 2.7), since some plugins might be discontinued in Confluence latest versions, like calendars that turned into [Team calendars](https://www.atlassian.com/software/confluence/team-calendars) in latest version (your customer will need to pay a license to use it).

Hope it helps,  
Thanks and Regards,  
David\|Atlassian Support


author: Ryan Goodwin
body: Hi Tihomir,

When you upgrade to the each confluence version, you should also upgrade the addons and validate the related wiki content/data is upgraded and functioning. This way you can step through the versions and if necessary pinpoint the version where an issue occurs and remedy it before upgrading to the next version of Confluence and compatible plugins.

Likely, a lot of the addons are still available or the functionality has been wrapped into the core confluence product. As David mentioned, ensure you upgrade in a test environment first so you can evaluate the upgrade process and work out any kinks.

A quick glance through your plugin list only highlights 1 addon from my experience:

Calendar Plugin Plugin Version: 2.6.1

Calendars is not compatible with Confluence 3.5 or newer. You MUST export all calendars in Confluence 3.4.9 if you wish to use them in Confluence 4.x - they may work to some extent in 3.5 but this is not a compatible version with the addon. Confluence 4.x and newer require a paid addon for calendaring - Team Calendars. You can import the .ics calendar exports from 3.4.9 into Team Calendars, but there is no direct migration path. If you upgrade past Confluence 3.4.9 you may not be able to recover the calendars.

Hope this helps.


Tags: confluence-app

content

upgrade