Refer to the table below to determine your Magic Collaboration Studio upgrade path.

Magic Collaboration Studio Software Upgrade Path

19.0


Database Migration 19.0







19.0 SP3


Database Migration 2021x







2021x


Cassandra Upgrade




2021x Refresh2 HF5


Cassandra Upgrade




 

2026x




19.0 SP119.0 SP4

2021x Refresh12022x

2026x HF1









19.0 SP2

2021x Refresh22022x Refresh1
2021x Refresh2 HF5

2022x Refresh2

2024x

2024x Refresh1

2024x Refresh2

2024x Refresh3

Cassandra 3

Cassandra 4

Cassandra 5

How to use the table:

  • Find the product version you are currently using.
  • Find the target version you would like to upgrade to.
  • If you are upgrading from left to right, you need to migrate the database and/or upgrade Cassandra as well as the Magic Collaboration Studio software.
  • You cannot skip database migration and upgrade steps when upgrading from left to right.
  • You can upgrade directly between non-consecutive versions (for example, from 2021x to 2024x), but you may need to upgrade Cassandra.
  • If you upgrade vertically down a single column, you only need to upgrade the Magic Collaboration Studio software. Intermediate versions can be skipped as well.

  • The procedures of data migration for versions 19.0 & 2021x are completely different. See the following pages on migrating data and upgrading the product for the relevant target version:
  • Magic Collaboration Studio 2021x Refresh 2 HF5 supports both Cassandra 3 and 4.

Upgrade guides

  1. Back up your current data before any upgrade! Once you upgrade Magic Collaboration Studio , you cannot downgrade it. Major database changes occur with each product upgrade, and data cannot be reverted.
  2. Upgrade Apache Cassandra (if needed).
  3. Upgrade the product.
  4. Migrate server projects.

When migrating from a server version earlier than 2022x Refresh1, you must delete duplicate external LDAP users with usernames in different cases (e.g., JOHN and john) if such usernames exist. Leave just one user. Otherwise, authentication of these duplicate user entries might fail in 2022x Refresh1 or newer versions.