When a new version of Vectorworks is released, we are often asked "When should we introduce this new version of Vectorworks to our practice and workflows?" With that in mind we wanted to share guidance about moving from previous version to a newly released one.
Transitioning your Vectorworks software from an older version to a new version is something that should be approached with a care and caution. New releases of software are, by their very nature, going to be somewhat different from older versions. Typically ther are new features introduced and other existing features are enhanced.
One consequence of these changes is that you may find your familiar workflows, tools, and techniques have been redesigned, moved, renamed or function a bit differently. Files that are transitioned from an older version to the new version may exhibit unexpected behaviour. Tools might be re-configured and designed to be used in a manner that is unfamiliar to the way you've worked before.
The route we recommend is that you download and install the newly released software and take some time to learn and experiment with the new release. Explore your new version of Vectorworks for a while, before committing to doing all your design work on it. Open some blank files and, see where the new tools are and try them out. Read up on what is new, consult with your distributor and check the Vectorworks Community Forum. What are others saying? Have a few challenges arisen? Does it make sense to move everything on Day 1 of a release?
The majority of our Vectorworks users are working hard on current projects. Most will likely keep many existing and well-established projects on an older version of Vectorworks until they have had a chance to ensure that their files will convert smoothly to the new version. Equally important is the need to become familiar with the tools and commands that are used on a daily basis.
Generally, within a month or two after the initial release of Vectorworks, there is a Service Pack (SP) release. We frequently suggest to our clients that they wait until at least SP1 before committing the majority of their projects to the newer version.
We hope this guidance helps.