Please refer to our main documentation for the Migration Assistant for general instructions on how to migrate bitvoodoo apps.
The following information is specific for the app "Viewtracker - Analytics for Confluence" by bitvoodoo.
If you migrate your Viewtracker data from Server/DC to your Atlassian Cloud instance, there are several points you should be aware of.
This document explains the differences and the steps you need to undertake to migrate data.
Some macros from the Server version are not compatible with Cloud.
To prevent you from getting the error "Unknown macro", we have marked the incompatible macros as "hidden" in our Cloud version. These macros don't have any output in Cloud.
|Not needed anymore because auto-tracking is enabled.|
|Viewtracker Report Macro||Not needed anymore. This is now done with the built-in Viewtracker Reports.|
|Space Analytics Macro||Not implemented yet, will be coming in a future release. Use the built-in Space Report instead.|
|Recently Viewed Macro||Retired in our Cloud version. We introduced the Popular Content Macro instead.|
|Page Analytics Macro||Not implemented yet, will be coming in a future release. Use the built-in Content Report instead.|
In the Cloud version, we removed the legacy Viewtracker Macro and implemented auto-tracking per default. So to start tracking views, you don't need to do anything.
Migrating the tracked data from Server to the Cloud requires several mappings. For example, the id of the page is different, and the key of the user differs. Viewtracker is using these two elements for tracking, so we need to change the Server data to Cloud data.
bitvoodoo implemented an automated migration path that is part of Atlassian's Migration Assistant. The process is explained in this document.
A maximum of 2 million Viewtracker views can be migrated in one go. If you have accumulated more than 2 million views, you need to split the migration into various batches.