---
title: "Migration Path - Glossary for Confluence"
canonical: "https://support.covectors.io/space/SAMM/540147713/Migration%20Path%20-%20Glossary%20for%20Confluence"
format: markdown
---
Below is a step-by-step guide to help you migrate your Glossary app data to Confluence Cloud.
## Before you start, please read carefully this checklist
- [ ] We recommend reading [this Atlassian article](https://confluence.atlassian.com/cloud/plan-your-cloud-migration-972349846.html) to plan your migration.
- [ ] We recommend reading carefully our major change to migration process [https://support.covectors.io/space/SAMM/661291017](https://support.covectors.io/space/SAMM/661291017) released on 1/2/2024
- [ ] Please check that you have Glossary for Confluence’s latest version for server/DC and the latest version of Glossary Cloud installed in both Confluence instances (having any previous versions to 5.1.0 in Serve/ DC won't trigger the Glossary migration; it will just migrate a Confluence space without glossary data).
- [ ] Make sure that Confluence users have valid email addresses that are the same as their cloud counterparts.
- [ ] Ideally, perform the migration with users that have admin site privileges on your Confluence Cloud site.
- [ ] Update the Confluence Cloud Migration Assistant to the latest version.
- [ ] Enable logging of [our migration module](https://support.covectors.io/space/SAMM/599785473/Steps+to+follow+before+migration) on your instance in order to debug any “possible” issue
> ℹ️ Detailed guide for migration assistant from Atlassian
> ℹ️
> ℹ️ [https://support.atlassian.com/migration/docs/use-the-confluence-cloud-migration-assistant-to-migrate/](https://support.atlassian.com/migration/docs/use-the-confluence-cloud-migration-assistant-to-migrate/)
## Running a migration of Glossary Data
### Step 1
Start by making sure that your Glossary App is tagged as **“Needed in Cloud”** in order to trigger the right event once a space is migrated via the Migration Assistant.
Navigate to Confluence Administration and choose Migration Assistant. Choose the Assess your apps option and select our Glossary app to be needed in Cloud.
:warning: Please note our Spectrum API bundle is not needed in Cloud.
### Step 2
Select your Cloud site where your data will be migrated.
To do so:
- Enter the site from which you want to migrate data and select the cloud site which data will be migrated to
- Select migration stage (Either Production or Staging)
- Check “Allow Atlassian” to access migrations data (if needed)
- Confirm
Now that your pre-configuration is done, you can proceed to creating a new migration plan.
### Step 3
Navigate to home page and **create a new migration**.
You will be redirect to the interface to confirm your cloud site selection and will be asked to choose what to migrate as following:
- Select Migrate spaces to choose after what spaces to migrate
- Select the users policy. Please note that you must sure that users that have created glossary content within your Confluence server are existing in your Confluence Cloud site. If not, the user who has created Glossary content in server and can’t be found during migration, he will be replaced by the user who is performing the migration in order to don’t break data or highlight feature.
Proceed to space select to migrate content from and migrate glossary data from as following:
After confirming the action, the migration assist will provide you with a list of checks and errors to fix before migration.
- **App Vendor Checks (NEW):**
The new release of the glossary app comes with **App vendor checks** designed to help you check for potential malfunctions that wouldn’t block the migration but rather result in some confusion when navigating your migrated glossaries.
There are 3 App vendor checks that appear within **the Pre-migration checks** interface:
All languages have saved page ID
This check appears if any given glossary language does not have a unique page ID that refers to it in space.
This error is extremely rare. However, if it does happen, then make sure to navigate to the [sanity check menu](https://support.covectors.io/space/CAD/540934145/Glossary+documentation+(Server%5CDC)#Sanity-check). Select “Glossary Page ID”. A list of affected pages will appear. Click “Clean”.
Each language has active letters
This check appears if the glossary you are willing to migrate does not have any active letters. This obviously does not block the migration, but it can lead to an empty glossary page within your cloud site. To fix this, we suggest you activate letters within the glossary language in question. If the glossary language is not part of your migration plan, then make sure to delete it.
Inadequate spaces configuration
This check appears if your space configuration is not up to date when it comes to the glossary highlights configuration. This might occur within spaces created when the app is disabled or not installed.
You will have a CSV file containing a list of all affected spaces. To fix this, navigate to the [sanity check menu](https://support.covectors.io/space/CAD/540934145/Glossary+documentation+(Server%5CDC)#Sanity-check). Select option “outdated configuration” and click “Start”. All affected pages will be listed. Click “Clean”.
You will get a recap of your migration before to run it: Details about your spaces, number of pages, what apps are impacted, etc.
You simply need to run the migration. You will be redirected to the home page where you can select the migration that you just launched to follow its state.
Please note that app migration progress will take time before displaying the feedback.
Two types of feedback are handled based on Atlassian API:
| **Migration App data state** | |
| --- | --- |
| COMPLETE | Your data are successfully migrated after space content and users migration. |
| INCOMPLETE | Something happened that may have broken the migration.
Some common cases for migration data errors:
- Non existing users in cloud
- Space data not found during migration due to latencies within cloud instance or internet
- Error in date to be migrated: glossary data containing special characters not handled in Cloud, null labels after data manipulation in Server, or server database, broken data. |