If you have ever upgraded a Revit project to the next version you have probably experienced some issues or inconsistencies in that project. Consider then that upgrading a Revit project template can often literally infect future Revit projects with similar performance impeding abnormalities.
I have experienced this first hand with one of our own customers, which is why we prefer to migrate project template setup into a new Revit version template instead of upgrading your old templates. Autodesk's Revit Performance Technical Notes have not addressed this subject, but recently the 2012 certification testing undertaken by Autodesk VAR Technical Resources discouraged upgrading Revit project templates to the next version. I learned my lesson and have since recommended migrating Revit templates as opposed to upgrading them as a "Best Practice" in Revit or any Autodesk product for that matter.
This is a more time consuming process...but compared to the productivity it can save your staff it is time well spent. However, if you long for the days when you could easily upgrade you templates...I have a set of mechanical pencils that I will let you have cheap!
Protect your Data
- Backup the current Project Template before starting this process
Transfer Project Standards
- Transfer project settings, system families and related component families from your project template into a current version project template.
- Identify component families in your project template that need to be added to the new project template you are creating. Save those families to a temporary folder. In the new version project template you can load all of these component families from that temporary folder.
Create a new project with your existing project template and save it to the temporary folder. From the Insert tab use the Insert from File>Insert View from File option to load Views, Schedules and Sheets into the new version project template.
(Sheet Views cannot be inserted if they have views referenced to them...open the project and remove the references first and then re-place the views in the current project template.)
- These views cannot be inserted from one project to another. Create new corresponding legend views in the current version template you are defining and copy/paste the information from the same legend views in the temporary project to the new view.
- Review Grids, Levels, Section, Elevation and Detail view settings in the current version project template to verify the component family assignments for proper display of these items.
- Review the current version project templates family list in the project browser to identify and eliminate duplicated or other unwanted family definitions.
- Finally you want to use the Save As command to overwrite your original default project template with this newly migrated project template for the current version.