How to migrate Viewtracker data from Server / Data Center to Cloud?
Please refer to our main documentation for the Migration Assistant for general instructions on how to migrate bitvoodoo apps.
The following information is specific to the app "Viewtracker - Analytics for Confluence" by bitvoodoo.
Viewtracker on-premise version 8.0.0 and above can migrate all existing views to Cloud. We highly recommend upgrading to the latest version.
If you migrate your Viewtracker data from Server/DC to your Atlassian Cloud instance, please note:
The tracked Viewtracker data (views and viewers of pages, blog posts and attachments) can be migrated automatically using Atlassian's Migration Assistant.
An administrator can carry out a content synchronization on Viewtracker Cloud to also display edits and creations accumulated in Server/DC.
Some Server/DC macros are not available on Cloud.
This document explains the Viewtracker data migration details and the differences in the deployments.
Viewtracker Data Migration
bitvoodoo implemented an automated migration path that is part of Atlassian's Migration Assistant. It is therefore not necessary to manually export and import the data.
The automated process for all bitvoodoo apps is explained in the general migration documentation.
Selecting the Viewtracker app
Viewtracker comes bundled with multiple plugins:
System App: Administration UI
System App: Analytics Core
System App: Attachment Tracking
System App: Search Analytics
To migrate all data, you have to mark “Viewtracker” and “System App: Attachment Tracking” as “Needed in Cloud”
In a later step, you will need to confirm the app data policy of Viewtracker other selected apps:
What is done during migration
The view data accumulated in Viewtracker and Attachment Tracking will be present once you migrate to Viewtracker Cloud.
The automated app migration path carries out the following steps:
Export the existing views and viewer data from Server/DC
Import the views and viewer data into the Cloud instance
Mappings of page IDs and user keys. The page IDs and user keys need to be changed from Server/DC data to Cloud data.
The Viewtracker metrics “Edits” and “Creations” are not part of the automated cloud migration. An administrator can use the Content Synchronization on Viewtracker Cloud to return this data in reports.
Data accumulated in the Search Report and URL Reports can not be carried over to Viewtracker Cloud. We suggest creating a CSV export of these reports for reference.
Macros
Some macros from the Server/Data Center version are incompatible 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.
Viewtracker Macro | Current state |
|---|---|
Not needed anymore because auto-tracking is enabled. | |
Not needed anymore. This is now done with the built-in Viewtracker Reports. | |
Will not be built on Cloud. Use the built-in Space Report instead. | |
Recently viewed pages are displayed in the tab “Recent” in the Confluence Cloud header, so this macro is not necessary anymore. | |
Will not be built on Cloud. Use the built-in Content Report instead. |
We introduced the Popular Content Macro on Viewtracker Cloud.
Auto-Tracking
We removed the legacy Viewtracker Macro in the Cloud version and implemented auto-tracking per default. To start tracking views, you don't need to do anything. Tracking can be restricted at any time; see "Manage Tracking".