Products / Version Transfer
Prygenix Version Transfer · for Autodesk Revit

Take a Revit model back to an older version

Revit cannot save to an older version. Version Transfer reads the model in the newer Revit, writes a package, and rebuilds it as native, editable elements in the older Revit — with an audit report of everything that was rebuilt, approximated or left out.

Revit 2027 → 2024Runs on your PC — nothing uploadedAudit report with every import

A rebuild, not a file conversion

The .rvt format is closed, so no tool can rewrite the file itself. Version Transfer goes through the Revit API in both versions instead:

  • Export in the newer Revit → Model.pryxvt
  • Import in the older Revit → native elements
  • Report → what came back, what did not, and why

Keep the original model. Check the result before you rely on it.

3versions back: from Revit 2027 down to 2024
0files uploaded — export and import run in your Revit
Freeexport, so anyone can send you a package
14day trial, up to 200 elements per import
How it works

Two buttons, two Revit versions

Export in the newer Revit

Open the model and click Export Package on the Prygenix tab → Version Transfer. It writes one .pryxvt file and changes nothing in the model. Free, no licence needed.

Start a project in the older Revit

Create a new project from your office template for that version, so your types, standards and families are there to match.

Import the package

Click Import Package, pick the file and, if you have them, your family library folders. Each stage runs on its own, so one problem never stops the rest.

Read the audit report

The report opens at the end: checks against the source, families to supply, and every element that was not rebuilt exactly. Press F1 on any button for the guide below.

What you get

  • Native walls, floors, roofs, ceilings, doors, windows, columns, beams and rooms
  • Levels, grids, materials, types and parameter values carried over
  • Everything else 3D kept as shapes in the right category
  • An HTML and CSV audit report next to the package
  • Shared coordinates kept, so links still line up
  • Your model never leaves your computer
  • Support by e-mail from the people who built it
What comes back

Native where Revit allows it, shapes where it does not

Every element ends up in one of three places, and the report tells you which.

Native, editable

  • Project information, units, shared coordinates and project base point
  • Materials, line and fill patterns, line styles
  • Shared and project parameters with bindings and values
  • Levels (with floor plans), grids incl. multi-segment, reference planes
  • Wall, floor, roof and ceiling types with their layers
  • Basic, curtain and stacked walls; floors, ceilings, footprint roofs
  • Wall and floor openings, shafts
  • Doors, windows, columns, beams and other families found in your template or library
  • Rooms, room separation lines, phases, worksets
  • Views: floor, ceiling and structural plans, sections, elevations, callouts, 3D and drafting views, dependent views, view templates
  • Sheets with title blocks and viewports; schedules with their fields, filters and sorting
  • Annotation: text, detail and model lines, filled regions, detail items, tags, room tags, linear dimensions
  • Model and detail groups
  • Revit links and CAD links, relinked at the same position

As shapes

  • Families not found in the template or library folders
  • In-place families
  • Extrusion roofs
  • Stairs and railings
  • MEP elements
  • Toposolids and anything else 3D

Shapes are DirectShapes in the right category with the source parameter values, so they schedule and tag. Doors and windows that become shapes still cut their wall.

Not yet

  • Design options: Revit's API cannot create them, so the primary option comes across and every element in the other options is listed in the report
  • Legend components (legends come with their text, lines and regions)
  • View filters and graphic overrides (hidden categories come across)
  • Area plans and areas; revisions and revision clouds
  • Key schedule rows; spot, radial and angular dimensions

Elements left out at export are listed in the report too, so nothing disappears silently.

Audit report

Proof of what was rebuilt

Written as HTML and CSV next to the package and opened when the import ends.

Checks

Wall length, floor area, room count and room area of the rebuilt model against the source, with the difference in %.

By category

For every category: how many were in the package, rebuilt natively, approximated as shapes or skipped.

Families to supply

Each family that became shapes, how many elements use it and why — so you know exactly which .rfa to find.

Element by element

Every element not rebuilt exactly, with its source and new ID (Manage › Select by ID) and the reason. The same list is in the CSV.

Family library folders

Real families, not just boxes

A family saved in a newer Revit cannot be loaded into an older one either. Version Transfer looks for each family in this order:

Your project or template

Same family and type name: used as it is.

Your library folders

Point to your .rfa folders for the older version (sub-folders are searched too). The family is loaded and missing types are created with the source's type values.

A shape, for now

If neither has it, the element becomes a shape and the report lists the family. Add it to a library folder and import again: the shapes are replaced by the real family.

Good to know

  • Library .rfa files must be saved in the target Revit version or older
  • A file saved in a newer version is reported as such, and that element becomes a shape
  • Autodesk's own content for the older version works well as a library
  • The same folders are searched for linked models (.rvt) and CAD files (.dwg, .dxf, .dgn); a linked model must already be in the target version, so transfer it first
  • The import window remembers your folders
Versions

From Revit 2027 down to 2024

Install it in both Revit versions. Export runs in the newer one, import in the older one; the import refuses a package from the same or an older version.

RevitExportImportNotes
2027✔—Nothing newer to import from
2026✔✔
2025✔✔
2024—✔Oldest version supported

Windows 10 / 11 · workshared projects (worksets by name) · one installer for every Revit version on the PC.

Guide

The three buttons

F1 on a Version Transfer button in Revit opens its section here.

Export Package

  1. Open the model in the newer Revit (2025 or later).
  2. Click Export Package and choose where to save the .pryxvt file.
  3. Send the file to whoever works in the older version — they need Version Transfer installed there.

Read-only: the model is not changed. Free, no licence or trial needed.

Import Package

  1. In the older Revit, start a new project from your template and keep it open.
  2. Click Import Package and pick the .pryxvt file.
  3. Add your family library folders (optional, recommended).
  4. Tick Create floor plans for the levels and a 3D view if you want them, then Import.
  5. Read the report. To fill in families later, add them to a library folder and import again with Replace shapes ticked.

Licence

Shows the trial status and this PC's Machine ID. Enter the key from your order e-mail — an annual licence or a 30-day pass — and click Activate (internet needed once). Deactivate frees the key for another PC.

During the 14-day trial each import rebuilds up to 200 model elements. After activating, import the same package again: what is there is kept and the rest is added.

Pricing

Pay for the import, export for free

Export is free. Buy a year for regular use, or a 30-day pass for a single project; the 14-day trial imports up to 200 elements each time.

Prices of every Prygenix product →

FAQ

Questions we hear often

Is it a lossless conversion?

No, and no tool can be: Revit's file format is closed and cannot be saved backwards. Version Transfer rebuilds the model through the Revit API. Most of the model comes back as native elements; the rest comes back as shapes or is listed as left out. The audit report shows exactly what happened to every element.

Is my model uploaded anywhere?

No. Export and import both run inside Revit on your computer. The package is a file you keep and send yourself. Only licence activation talks to the Prygenix licence server.

Does the person who exports need a licence?

No. Export is free, so a consultant or client on a newer Revit can install Version Transfer and send you a package. The licence is only needed to import.

Will doors, windows and furniture come back as families?

Yes, when the family is in your template or a library folder for the older version. Otherwise it becomes a shape with the right category and parameter values, and the report lists the family so you can supply it and import again.

Can I import into an existing project?

It is meant for a new project from your template. Importing the same package again into that project keeps what is already there and adds the rest, or replaces shapes with families that are now found.

What about views and sheets?

They come across from version 1.1: plans, sections, elevations, 3D and drafting views with their crop, scale and view templates, sheets with title blocks and viewports, schedules, and the annotation in them, including tags and dimensions. Legend components and view filters are not transferred yet; the report lists them.

Windows says "Windows protected your PC". Is the setup safe?

Yes. Windows shows this for new downloads it hasn't seen often. Click More info, check the app name is Prygenix Version Transfer Setup, then click Run anyway.

Something went wrong — what should I send?

The audit report, the error message and the file %APPDATA%\Prygenix\VersionTransfer\errors.log to support@prygenix.com.

Try Version Transfer free for 14 days

Download the installer and install it in both Revit versions. Export is free; the trial imports up to 200 elements at a time.