---
title: "[Glossary][FAQ] Migration Server to Cloud major change"
canonical: "https://support.covectors.io/space/SAMM/661291017/%5BGlossary%5D%5BFAQ%5D%20Migration%20Server%20to%20Cloud%20major%20change"
format: markdown
---
## Problem

Several customers noticed issues during migration content from Server to Cloud where migration is stuck and can not move forward for unknown reasons. 

After investigation we found out that this can be related to issues executing REST API to store content related to Apps data (for Glossary and FAQ for Confluence)

Once App data are sent to Cloud, we are proceeding to storing those information within space properties. Action to store data is proceeded with user sent from cloud based on permissions (space manager, page owner etc.)

Still we noticed that if user is not yet enabled in Cloud (did not logged in Cloud to enable his account) the action is blocked due to lack of permission and security reasons which blocks migration process. 

## Changes made in App

We have made the change to be made by the ***APP USER.*** 

Having the right privileges (in both App: write and admin for space) App user is now able to run the REST APIs during the migration of APP data.  

## Impact

After data migration, App user will be displayed as the content creator: 

- Glossary: Term creator
- FAQ: Question creator

Creation date will be also set to the date when the user has made the migration and information has been stored in the space. 

#### Solution

We are storing the original information sent from Server in content property information and in next release it will displayed within a special tag (for Questions and terms) if user hover on it. 

## Known problems

We have noticed that migration can also behave in an expected way if launch for multiple spaces (generally more than  spaces) 

Created spaces are not listing APP User with the right permissions in the individual permissions. This has been reported for Atlassian and unfortunately workarounds do not apply in our case as space permissions for App are needed during the migration process and not after. 

[https://jira.atlassian.com/browse/MIG-905](https://jira.atlassian.com/browse/MIG-905)

As a workaround we advice strongly our users to run the migration with small bunch of spaces (Two spaces)