General App Documentation

Cloud Migration Hub: Viewtracker - Analytics for Confluence

Cloud Migration – Viewtracker - Analytics for Confluence

Atlassian is ending support for Confluence Data Center by March 2029.
This page explains how Viewtracker - Analytics for Confluence will be migrated from Confluence Data Center to Confluence Cloud, what you need to prepare, and what you can expect.

Viewtracker changed its migration path

Viewtracker Data Center 8.5.0, 10.4.0, and 11.2.0, in combination with the Viewtracker Cloud 9.0.0 version, migrate your data with Atlassian Forge. If you're currently preparing a migration, check which case applies before you update:

  • If you still have time for testing migrations: Update the app on Data Center and Cloud to the above-mentioned versions and test the migration again.

  • Production migration already tested and imminent: Keep your current versions. Update Viewtracker Cloud only after the successful migration.


🔎 Quick overview

Question

Answer for Viewtracker - Analytics for Confluence

Migration effort and automation level

Low – Typically, only one migration run is required. Certain settings must be configured manually in the cloud, including data privacy and access permissions.

Fully automated – CCMA migrates view and viewer data automatically.

Main risks/limitations

  • Viewtracker Cloud 9.0.0 and later only accept migrations from Viewtracker Data Center 8.5.0, 10.4.0, or 11.2.0 and later.

  • Outdated macros are hidden.

  • Tracked Confluence searches and custom URL Reports are not migrated.

  • Some features or metrics may not be available in the Cloud.

Migrate Viewtracker - Analytics for Confluence to Cloud | Communardo App Documentation

Differences between Viewtracker Data Center and Cloud versions

Key prerequisites

  • Viewtracker Data Center 8.5.0, 10.4.0, or 11.2.0 (or a later version of the same major version) and Viewtracker Cloud 9.0.0 or later. If you already tested your migration with an older Data Center version, read the notice "Viewtracker changed its migration path" at the top of this page first.

  • IP allowlist: If enabled in Cloud, Viewtracker backend IPs must be whitelisted.

  • Full backup of the Confluence instance.

  • Test/staging environment recommended for trial migration.

  • Inform users about possible read-only mode or short downtime.

Best practice

  • User impact during migration: Read-only recommended for affected spaces.

  • Typical duration: From a few minutes up to several hours, depending on data size.

  • Best practice: Perform migration outside business hours or in a test/staging environment first.

Available Cloud types

Viewtracker - Analytics for Confluence is available on Commercial Cloud.
Contact us about a potential migration to the Government Cloud.


info What Viewtracker - Analytics for Confluence does

Viewtracker delivers in-depth Confluence analytics, offering insights into page, space, and user activity. Track engagement, monitor trends, and gain visibility into dashboards, calendars, and third-party apps
This section explains how your Viewtracker - Analytics for Confluence data and configuration move from Data Center to Cloud.


🔄 How to migrate

Please unfold the sections below to view the complete, detailed instructions for the upcoming migration.

By expanding these folders, you will access all the steps and guidelines needed for a smooth, successful migration.

Before you start

Use this checklist before planning the migration.

Supported versions

  • Minimum Viewtracker - Analytics for Confluence version on Data Center: 8.5.0, 10.4.0, or 11.2.0

  • Minimum Viewtracker - Analytics for Confluence version on Cloud: 9.0.0

  • Minimum supported Confluence Data Center version: 7.5.0

  • Viewtracker - Analytics for Confluence on Cloud: Link to Marketplace

Viewtracker Data Center 8.4.0 and later versions before 8.5.0 use the previous Connect-based migration. This combination only works with Viewtracker Cloud versions before 9.0.0. Use it only to complete a production migration you already tested with these versions.

Preparation

  • Create a full backup of your Confluence instance

  • Update Viewtracker - Analytics for Confluence on Data Center to version 8.5.0, 10.4.0, or 11.2.0 or later (latest recommended)

  • Configure IP allowlist: If your Atlassian Cloud instance uses an IP allowlist, you must add Viewtracker's backend IPs to ensure the migration can communicate with the Atlassian API:

    • EU: 18.153.151.42, 52.28.186.134

    • US: 34.206.215.200, 3.81.253.191

  • Install Viewtracker - Analytics for Confluence Cloud 9.0.0 or later

    • to configure data privacy settings, access permissions, and other tracking settings

    • to review the migrated data

  • (Recommended) Use a test/staging environment for a trial migration

  • Inform users about possible read‑only or short downtime

  • Review known Cloud limitations/differences

How the migration works

📖 Migration approach

Recommended: Using Atlassian migration tools via Confluence Cloud Migration Assistant (CCMA)

  • Use the Confluence Cloud Migration Assistant (CCMA)

  • Include Viewtracker - Analytics for Confluence data in the migration wizard

  • App‑specific export/import: Not needed, migration is automated

Recommendation for most customers:

  • We recommend using CCMA with Viewtracker included in the migration run. This ensures automatic migration of all view and viewer data.

  • After a successful migration, we recommend performing this Content Synchronization.

🔢 Step‑by‑step

Step 1 – Prepare on Data Center

  • Check versions (Confluence ≥ supported version, Viewtracker Data Center ≥ 8.5.0, 10.4.0, or 11.2.0, Viewtracker Cloud ≥ 9.0.0)

  • Create and verify a backup

  • (Optional) Run a test migration in a staging environment

  • Communicate migration timing and impact to users

Step 2 – Run the migration

  1. Start the Confluence Cloud Migration Assistant

  2. Select the spaces/projects and mark Viewtracker as “Needed in Cloud”

  3. Confirm app data policy for Viewtracker

  4. Start the migration and monitor progress

Step 3 – After the migration in Cloud

  • Verify that the view and viewer data are present

  • Use the Cloud Content Synchronization feature to restore “Edits” and “Creations” metrics

  • Make sure to adjust the Cloud settings if this has not already been completed before the migration.

  • Inform users that Viewtracker in the Cloud is ready to use

After Migration

🎉 Congratulations: You have successfully migrated Viewtracker - Analytics for Confluence from Data Center to Cloud.

Reference / Blog:


🤝 Support & resources

❓ FAQ for Viewtracker - Analytics for Confluence migration

  • Can users continue working while the migration runs?
    We recommend read‑only mode for the affected spaces during the migration to avoid inconsistencies in view tracking. Users can still browse content, but edits may not be captured in the migrated analytics.

  • What is not migrated?

  • What are the biggest changes compared to Data Center?
    All important differences are documented here. This list is continuously updated.

  • Why is my Viewtracker migration stuck in "In Progress"?
    If the migration hangs while other tasks are finished, it is likely blocked by an IP allowlist. Solution: Ensure that Viewtracker's backend IPs (listed in the Preparation section) are whitelisted in your Atlassian Cloud site settings. Once whitelisted, the app can successfully send progress updates to Atlassian and complete the task.

  • I already tested my migration with an older Viewtracker version. Do I need to update? It depends on how much time you have before your production migration. If you can run another test migration, update both apps (Data Center to 8.5.0, 10.4.0, or 11.2.0, Cloud to 9.0.0) and test again. If your production migration is imminent, don't update either app. Complete the production migration on the tested versions, then update Viewtracker Cloud to the latest version.

  • Are you a solution partner and have questions about licensing during migration?
    Contact us via Partner Fast Lane