Projects and files

Last updated: 20 October 2026 17:44 BST

As part of the transition to the new 3D application, existing projects and files are copied into the new environment so they remain accessible. Existing permissions are preserved, allowing users to continue working with their projects and files without needing to start again.

Accessing migrated projects

Users continue to log in through the Hub. The new 3D application can be launched directly from the Hub using Quick Launch or by opening a project file from its location in the folder structure.

Organisation root folder

Project and file structure

Projects are now represented as folders. During migration, two folders are created within your organisation's root folder.

Migrated VU.CITY Projects contains one folder per each migrated project. Original project names are preserved.
Migrated Personal Drives contains one folder for each user’s personal drive. Personal drive content remains private to the relevant user and organisation admins.

Each project folder contains its associated models and files, including all of its .VU files.

A typical structure appears as:

Migrated Project folder diagram

What happens to .VU files?

The primary .VU file for each migrated project is pre-converted and ready to use in the new 3D application.

Within the migrated project folder, the legacy primary .VU file is represented by a separate folder. This folder contains the converted .VU file together with all assets associated with it.

Other .VU files are retained within the migrated project and can be accessed from the project folder.

What is preserved?

Migration preserves existing project content and access wherever possible. This includes:

associated models and files
project and file names
existing permissions
personal drive content and folder structure

Some content is represented differently in the new 3D application because the underlying project structure and workflows have changed. These differences are covered in the other migration guides.

What happens to the original project?

Migration creates a copy of the project content for use in the new 3D application. The original project remains available in Legacy and is not modified by the migration. Changes made to the migrated project in the new 3D application do not affect the original Legacy project. Likewise, changes made to the original project in the Legacy 3D application do not affect the migrated project in the new Hub/3D application.

Relevant articles