Migrating from v2 Connectors to Next-Gen Connectors (v3)
Speckle’s new next-gen connectors (v3) offer faster performance, expanded features, and a unified data model. This guide helps you migrate your workflows from legacy v2 connectors to the next-gen environment.
Why upgrade?
✅ Next-gen connectors are faster and more reliable.
✅ Expanded property support and consistent schemas.
✅ Designed for workspace-based projects, enabling true collaboration.
v2 and v3 connectors cannot be used interchangeably.
Migration steps
Remove legacy v2 connectors
Uninstall the old Speckle plugin files from your authoring tool or remove them via your plugin manager.
Install next-gen (v3) connectors
Visit the next-gen connectors page for downloads and installation instructions.
Create workspace projects
Next-gen connectors require workspace-based projects.
- Go to your workspace in the Speckle web interface.
- Create a new project for each workflow you want to upgrade.
Re-send data using next-gen connectors
Since v2 and v3 connectors use different data models, data migration involves re-sending your models:
- Open your model in your authoring tool (e.g., Revit, Rhino, SketchUp).
- Use the next-gen connector to send your model to the newly created v3 project.
Validate and adjust workflows
- Open the new project in the Speckle web interface to confirm your data.
- Adjust any scripts or automation tools to use the new workspace project structure.
Connector migration questions
Do Next-Gen connectors and legacy connectors support the same tools?
Do Next-Gen connectors and legacy connectors support the same tools?
They match, but not completely.
Next-Gen connectors are available for: Revit, Rhino, Archicad, AutoCAD, Navisworks, SketchUp, Blender, Civil 3D, Grasshopper, ETABS, Tekla, and Power BI. These connectors are available in the legacy version as well, but we recommend you to use the Next-Gen version.
These connectors will be available only in the legacy version: Dynamo, Unity, Unreal, Excel, SAP2000, SAFE, CSiBridge, Bentley (MicroStation, OpenRoads, OpenRail, OpenBuilding), Advance Steel, TopSolid and QGIS.
Can I still use legacy connectors?
Can I still use legacy connectors?
If you need to use legacy connectors, they will still be available for download here.
How do I update the Next-gen connectors without Speckle Manager?
How do I update the Next-gen connectors without Speckle Manager?
If a new version of Next-Gen connectors is available, you’ll see a little Update button when you open it up in your host application. You can always go back to app.speckle.systems, to check for the latest version.
What's happening to Speckle Manager?
What's happening to Speckle Manager?
Speckle Manager is only used to install legacy connectors. If you must continue using legacy connectors, the Manager will be available here!
How do I uninstall the Next-Gen connectors?
How do I uninstall the Next-Gen connectors?
Just head to your computer’s standard programs/applications list and uninstall like any other app.
How do I remove an account or change the default one without Speckle Manager?
How do I remove an account or change the default one without Speckle Manager?
Accounts can be removed or changed even without Speckle Manager. Whichever account you had selected last time (across devices) is your default for the next session.
-
Click your profile picture at the top open up your account manager.
-
Click to Switch your active account. Your last used account will be the default account.
-
You can add a new account, or click on the Trash icon on any current account to remove it.
Do I have to upgrade immediately?
Do I have to upgrade immediately?
No, but v2 connectors are no longer supported or receiving updates. Switching to next-gen connectors ensures better performance and future-proofed workflows.
Will my old v2 data disappear?
Will my old v2 data disappear?
No. v2 streams remain in read-only mode in your personal area. You can still view or download them.
Can I roll back to v2?
Can I roll back to v2?
No; v2 and v3 connectors are built on different data models and cannot reliably be used interchangeably.