A cloud service can make shared work easier. However, the choice should also consider what happens when the company wants to change suppliers or discontinue the service. The ease of entry and the possibility of exit are different conditions.
I propose that we check how the data is exported, what formats are available and what is left out. An exported file can retain content but lose links, comments, or organization. It is necessary to understand whether another system will be able to use it to continue the work.
A hypothetical example is an archive of projects with many attachments. The exit may require you to retrieve documents and relationships between them, as well as a simple table. Limited testing allows for the necessary activities to be recognized before the change becomes urgent.
Access, assistance and contractual conditions also deserve specific verification. I propose linking this information to the overall cost of the service. The risk of dependence does not automatically make a choice wrong, but it must be known. Evaluating the output supports the continuity of the activity and allows you to compare offers through the conditions they will serve throughout the relationship, in addition to the initial presentation of the functions.