Skip to main content
With the full release of workspace-based collaboration, personal projects in Speckle are now in read-only mode. This guide helps you migrate your existing personal project data to a workspace to continue working collaboratively.

​
Why migrate?

✅ Legacy Personal projects are read-only - no new data can be sent to them.
✅ Workspace projects unlock editing, collaboration, and automation.
✅ Next-gen connectors require workspace-based projects.
✅ Migrating ensures you can continue using Speckle’s full capabilities with your existing data.

​
Migration steps

1

Review your personal projects

Go to Speckle and sign in. In the left sidebar, click My Projects and review the personal projects you want to migrate. It ma not eb everything, and this is a good time to decide which projects you want to keep working on in a workspace as it will affect the plan selection that suits your needs best.
2

Create a workspace

If you haven’t already created a workspace, in the top-right menu, click your profile and select Workspaces. Click Create Workspace and set up your workspace name, description, and invite team members.
3

Move projects into your workspace

From the workspace page.You can select Add Project to create a new project or move an existing one. You will be presented with a full list of all your personal projects.From the personal project page.For each project, click the Move button and you will be presented with a list of any workspaces you are the admin of.
4

Move your data

Moving your project models does not upgrade it from legacy to Next-Gen data structures. You will need to use the next-gen connector to send your data to your new workspace project.
5

Validate and start collaborating

Open your new project in the Speckle web interface to confirm all data transferred successfully. Invite collaborators as needed. Use next-gen connectors to keep your workspace project up to date.

​
Project migration questions

The Move button is disabled if you are not the project owner. Only the project owner can initiate the move to a workspace. If you need to migrate a personal project, contact the project owner to perform the migration.
If you have collaborators on a personal project, they will still have access to the project in read-only mode. However, they will not be able to send new data to the personal project. You can change their role to Editor in the migrated project. Depending on the workspace plan they will affect your billing.
If your workspace has reached its project limit or model limit, you can either: - Upgrade your workspace plan to increase the project limit. - Add the Unlimited Project and Models add-on to your workspace plan.
No. Personal projects remain in read-only mode for your reference and download.
Currently, no; personal projects and workspace projects use different permissions for collaborators. Migration is a manual process.
If you have many personal projects, consider prioritizing the most important ones for migration. You can also use the search functionality in the project page to quickly find and move specific projects. There is no bulk migration feature at this time, so each project must be moved individually.
Yes, you can still access your personal projects in read-only mode. They will remain available for reference and download, but you cannot send new data to them.
The main model was the default model in the v2 connectors. There is no longer an enforced convention for the main model.
The main model was the default model in the v2 connectors. There is no longer an enforced convention for the main model, but for backward compatibility it is a reserved model name.
⌘I