Has anyone done this yet and if so, what has your experience been? Would you advise to leave a project in the version it was started in, or to move to the current version to take advantage of new functionality? I had some hiccups with AutoCAD MEP when moving a project forward from one release to another and am wondering if something similar would happen in Revit world. Thanks.
As a best practice from my experience - What ever version you started - finish in.
This prevents several issues.... If you are working with other firms, they may not be able to make the jump to the new version. So you are no longer in sync and that just does not work.
This also prevents any possible data loss in the upgrade, I am not saying this will happen - but no one will 100% guarantee that it won't happen. Is it really worth the chance? If you are at the beginning of a project - i would take the chance but if i am beyong midpoint - it will stay where it is.
Everyone is different and will approach it differently.
I would leave your project in 2011. We have upgraded one project as a test and keep running into issue after issue with 2012. All of our consultants have upgraded as well. But as of right now it's not worth the hassle.
Our policy has been to not upgrade projects that are over 90% complete, or that are within 4 weeks of being issued for construction. All other projects are upgraded once the new release has been vetted for potential issues (not all issues, obviously, but as many as can be reasonably expected).
Caveat: if any consultants are using Revit, and aren't on subscription or will not be upgrading on an equal timetable, then the project stays in the original version.
Reading all of these responses leads me to ask:
What about older projects, what about a project that was created in 2008 and you have upgraded Revit every year.
Now you need to work with this old project again. (e.g. building additions or whatever)
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register