Understand the scope when starting from a file.
The existing file route works through vector PDF. Pages are analysed and recognisable text, shapes, sticky notes and lines are converted into Xohre objects. Information absent from the exported file is not guessed and presented as fact.
Not every visual element is expected to arrive as an exact editable equivalent. The import report explains approximate mappings and content retained only in the original image. The PDF itself and the editable result are different representations.
Import into the library, then place it in the work.
Review imported pages in the team library with their previews and reports. Place suitable content on a Wall in a Room, then check the imported objects and relationships.
Team-library access depends on Xohre membership. A person’s name visible in the source tool does not grant verified membership or permissions to that person in Xohre.
Consider session information separately in enterprise migration.
Bulk packages may include board files and comments, participants, votes or activity information explicitly provided by the source. Source-space mapping to teams and personal-data options are handled within the approved scope.
No new history is invented when session information is not supplied by the source. Official API access is a separate development route from file import and remains conditional on a legal opinion.
