---
title: "[Glossary] Migration DC to Cloud best pratices"
canonical: "https://support.covectors.io/space/SAMM/1418919952/%5BGlossary%5D%20Migration%20DC%20to%20Cloud%20best%20pratices"
format: markdown
---
Glossary Cloud relies on both Glossary page information (macros and page labels) and database information related to Glossary App. 

Some checks can be done before Cloud Migration to ensure data full migration and avoid errors. 

## Frequent problems that may block migration

|  |  |  |
| --- | --- | --- |
| Glossary related to App Labels and page architecture | Glossaries |<br>Glossary FR  |<br>Letter FR<br>Letter FR<br>Glossary EN  |<br>Letter EN<br>![image-20250701-085919.png](media://82e11cf6-cb0d-4429-af53-a0558ec02115)<br>***Labels in pages:***<br>Glossaries: [glossary-blueprint]<br>Glossary page: [glossary-hoME] [LANG-glossary-blueprint]<br>Letter page: [glossary-letter] | - Ideally those labels must exist in pages.
- Page titles (glossary page name can be changed if needed)
- Glossaries page is not mandatory for migration but its existance facilitates the migration |
| App User not listed in Global permissions | This is an Atlassian related problem that sometimes can happen | Uninstall App and reinstall the app the provoke app creation and addition<br>To check if user exists:<br>```
CLOUD_URL/wiki/admin/permissions/global?tab=apps 
```<br>![image-20250701-090447.png](media://71b76ead-03d9-447e-a4f8-ef05a5d7ac63) |
| Incoherence in database | For some cases it may exist that database contains corrupted data (null page references) which may block the migration<br>Indicator for this case are:<br>- The non existance of export button in Glossary pages
- The existance of NULL references in PAGE ID columns in related Glossary tables | Please contact us if you want to make sure that the database tables are clean and without errors.<br>We can assist you in doing the right queries and fixing the problem. |

## Metrics to ensure data has been fully migrated from DC/Server to Cloud

The best metric to monitor is the **total number of terms** either per space or for Confluence instance. 

In DC a global interface listing all glossaries can be accessed as following where you can see count of terms per glossary:

![Untitled-20250701-113536.png](media://fa3e0353-a55b-449f-abcf-0e78bd354439)

Same can be verified in Cloud:

![Untitled-20250701-113741.png](media://24e63bb6-e01e-44c1-9806-9edababf4230)


## Migration workaround 

Use export - Import features between Server/DC to Cloud

Export is available via JSON (to keep terms definition formatting) or CSV.

## Enable logging before migration

Enabling the logs on DC provide us with details about the state of the migration and if there are any problem from the above list. 

To enable the logs please follow this guide: 

> Macro (include)