> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/t4r/list-of-features/bulk-upgrade-of-families.md).

# Bulk Upgrade of Families

Automatic conversion of projects and families to the current version

**Icon:** <img src="https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/GTmiqdZ1004TjmnxN0Yf/image" alt="" data-size="line">

**Location:** ribbon Be.Smart T4R, panel Project

**Packages:** Holixa T4R Silver

{% hint style="info" %}

#### Main functionalities and benefits:

* Improved productivity while working with multiple Revit versions
* Help save time - no need to upgrade projects, families one by one
* Solves the need to upgrade all libraries, templates, etc., when moving to a newer Revit version
  {% endhint %}

### **Overview**

The function allows to batch upgrade Revit projects, families and templates to the current Revit version.

In addition, it can save upgraded projects and families to new destinations, add prefix and suffix, and replace parts of names.

You also have the option to audit files during the upgrade process, detach from central and discard/preserve worksets, or automatically reload the path of external references

![](https://content.gitbook.com/content/qtUsszuAWXIZhQhrvjnb/blobs/Fuwf01nYSTiwFmQKtYXo/image)

### Tutorial

{% file src="/files/n5H1L3cR5fLoZGkyJYzb" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.besmart.software/3d-modeling-and-design/t4r/list-of-features/bulk-upgrade-of-families.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.