How do I import a tour from a JSON package?
Move an existing Mango360 tour between workspaces, restore a backup or start from a shared template with a JSON package.
A JSON package carries scenes, hotspots and settings between projects. Use it to copy a tour into another workspace, to restore a backup, or to start from a template that a colleague exported for you.
Export the package
- Open the project and choose Project → Export.
- Select the scenes you need, or export the whole project at once.
- Save the resulting .json file to your computer.
Exports are made from the project, so a package always describes the draft in its current state. Export a copy before a risky change and keep it with your backups: if a colleague deletes the wrong scenes, the package brings them back in a minute. The same file works as a starting point for a new workspace, which is how most agencies move a client from a test account to production. The package is the only portable part of a tour: panoramas and media stay where they are, so a tour that relies on external files has to be checked on the new machine as well. An import takes seconds and leaves the published versions untouched.
Import it
Open the destination project, choose Project → Import and drop the .json file into the dialog. Scenes are added to the current project; existing scenes are never overwritten, and imported hotspots keep their targets.
Check the result
- Imported scenes appear at the end of the scene list and keep the exported names.
- Media files are referenced, not copied — check that every link still points to a live file.
- Branding settings stay with the destination project and are not overwritten.
The file is plain JSON and contains no credentials. Still, keep it private if the tour shows unreleased property details, and remember that an import does not create a new published version.
Still need help?
Can't find what you're looking for? Our support team is here to help.