Importing Personal Projects Into A Workspace
Importing lets you copy personal projects into a Business workspace without touching the original personal copy. It is the cleanest way to turn private work into shared team work.
Find the import entry point
In the workspaces area, Business workspaces that allow editing show an Import Personal Projects action. The same import route is also available from the workspace projects area when your role allows it.
In the live app, owners, admins, and members can use the import flow when the workspace is active and not blocked by a seat-limit problem.
Understand what the import does
The import flow copies personal projects into the selected Business workspace. Your original personal projects remain private and unchanged.
The copied projects become organisation-owned workspace projects. They are now part of the shared workspace context rather than the personal one.
Select the projects to copy
The import page shows your available personal projects and lets you select one or more of them. The page also shows how many versions each project has, which helps you judge how much history you are bringing across.
Choose the projects the team genuinely needs. If a personal project is still only a private experiment, it may be better left in the personal workspace until it is ready for shared use.
Know what gets copied and what does not
The import brings across the project structure, versions, scenarios, appliances, and input data so the workspace can continue from the same general setup.
It does not copy stored calculation results or warnings. That part is deliberate. The workspace copy should generate its own saved results in the shared context rather than relying on old personal result storage.
If the workspace already has a project with the same name, GridGap resolves the imported copy to a unique workspace name instead of overwriting an existing project.
Run the import and review the outcome
After you click Import Selected Projects, the app confirms the import and gives a recalculation notice. It also offers a shortcut to View Workspace Projects so you can move straight into the shared copy.
The import page is careful about expectations. It tells you up front that copied projects need fresh calculation inside the workspace.
Recalculate inside the workspace
This is the most important step after import. Open the copied workspace project, review the versions you want to keep using, and run Calculate again so the workspace copy has its own stored results and warnings.
Until you do that, the imported project structure is present, but the workspace does not yet have a fresh saved result set for those versions.