Pirros can convert your firm's families and details to a different Revit version on demand — no need to open the file locally or install the older/newer Revit. The upgrade runs in the cloud, completes in the background, and the upgraded file becomes available for download once it's done.
Prerequisite: Multi-version upgrades use credits. Your firm gets a starting credit balance — admins can top up at any time from Settings → Workspace → Credits. Credits hold while an upgrade runs and finalize when it completes; cancelled or unused credits are released back to your balance.
When to Use Multi-Version Upgrades
Pirros stores each family and detail in the Revit version it was originally uploaded from. When a teammate downloads, Pirros automatically delivers the matching version if available, or upgrades the closest lower version on the fly.
Use a manual multi-version upgrade when:
You need the upgraded file as an artifact in your library — for example, you're standardizing on Revit 2025 and want every typical detail to have a native 2025 version stored alongside the originals
You're preparing a project for a Revit version transition and want all relevant content available in the new version up front
You need many files upgraded at once — batch upgrades are more efficient than upgrading one-by-one as people download
You don't have access to the source Revit version on your machine and need the file in a version you can open
Upgrading a Single Family or Detail
Open the family or detail's page in Pirros
Look at the Available Revit Versions badges — these show every version Pirros can deliver natively right now
Click Upgrade to another version (button label may vary slightly)
Pick the target Revit version from the dropdown — only versions higher than the source are available (upgrades are one-way)
Confirm — Pirros holds the credit cost and queues the upgrade job
The upgrade typically completes in a few minutes. While it runs, the artifact moves through the following states:
Queued — scheduled, waiting to start
Running — Pirros is converting the file in the cloud
Success — upgrade complete, file ready to download
Failed — something went wrong; you can retry without paying again for the same hold
Cancelled — you cancelled before completion (held credits return to your balance)
Once the artifact is in Success, the new Revit version appears as a badge on the asset and is selectable from the search filters across your library.
Batch Upgrades
If you need many items in a new Revit version (e.g., your whole typical library upgraded for next year's projects), use a batch upgrade.
Go to the Details or Families page
Filter or select the items you want upgraded
Click Bulk actions → Upgrade to version
Pick the target Revit version
Pirros shows you a cost estimate for the batch (sum of per-item credit costs) and your current available balance
Confirm — Pirros holds the total cost and queues all artifacts
Batch upgrades run in parallel where possible. As each artifact completes, its credits move from "held" to "consumed." Any items that fail or are cancelled release their held credits back to your balance during settlement (the final reconciliation after every artifact in the batch reaches a terminal state).
Heads up: If you cancel a running batch, only items that haven't finished are stopped. Successfully upgraded artifacts stay in your library and their credits are consumed normally.
How Credits Work
Per-item cost depends on the file's complexity — larger families and details with more nested content cost more credits to upgrade
Hold first, consume on success — when you start an upgrade, Pirros holds the estimated credits so two batches don't fight over the same balance. The hold becomes a charge only when the artifact succeeds
Free if it fails — failed and cancelled artifacts release their held credits. You aren't charged for an upgrade that didn't deliver a file
Same source = no re-upgrade cost — once an artifact exists for a given source + target version pair, future requests deliver the existing artifact instead of running a new upgrade
Base versions are free — the original Revit version of any asset (the version it was uploaded from) is always available without consuming credits
Check your firm's current credit balance in Settings → Workspace → Credits. Admins with the appropriate permission can top up there.
Filtering Search by Available Versions
Search results across details and families include a Revit Version filter on the left sidebar. The filter shows every Revit version available across your library — including base versions and any successfully completed upgrade artifacts.
When you upgrade an item, the new version appears in the filter automatically once the artifact reaches Success. There's no manual reindex step.
What Multi-Version Upgrades Can and Can't Do
Can:
Convert a family or detail to a higher Revit version (e.g., 2022 → 2025)
Run multiple upgrades in parallel
Resume failed batches (failed items can be retried)
Show progress and status in real time
Can't:
Downgrade. Revit version upgrades are one-way — you cannot convert a 2025 file to 2024. Upload the file again from Revit 2024 if you need a 2024 version
Upgrade content with Revit-side errors. If the source file has corruption or a Revit error that prevents opening, the upgrade will fail. Fix the source in Revit and re-upload, then re-run the upgrade
Skip Revit's version-locking rules. The target version must be one Pirros supports (see Revit version compatibility matrix)
If an Upgrade Fails
When an artifact ends in Failed, the held credits are released back to your balance and you can retry without re-paying. To retry:
Open the failed artifact's status panel on the asset's page (or in the batch summary)
Click Retry
If the retry fails again, open the Logs link on the artifact — it surfaces the underlying Revit error
Common causes of failure:
The source family/detail uses a Revit feature that doesn't exist or behaves differently in the target version
The source file has corruption or unresolved warnings
The cloud upgrade timed out (very large files only — contact support if this happens repeatedly)
Frequently Asked Questions
Q: Do I need Revit installed locally to run a multi-version upgrade?
A: No. The upgrade runs entirely in Pirros's cloud. You can request and download upgrades from any machine with a browser.
Q: What's the difference between this and Pirros automatically delivering a matching version when I download?
A: Auto-delivery happens at download time and produces a one-off file for your immediate use — it doesn't store an artifact in your library. A multi-version upgrade creates a persistent artifact that everyone in your firm can use, and it gets indexed in search filters.
Q: Can I upgrade to a Revit version older than the source?
A: No. Revit's file format is forward-only — once a file is saved in a newer version, it can't be opened in an older one. If you need a downgrade-equivalent, upload the file again from the older Revit version (Pirros will store both as separate native versions under the same Pirros ID).
Q: How long does an upgrade take?
A: Most upgrades complete in 1–5 minutes. Larger families with many nested types or complex geometry can take longer. Batch upgrades run in parallel, so a batch of 50 items typically finishes in around the time of the slowest single upgrade — not 50× the per-item time.
Q: What happens to the original version after I upgrade?
A: Nothing — it stays exactly as it was. Upgrades produce new artifacts; they don't replace or modify the source. Your Revit 2022 version remains downloadable for anyone on Revit 2022, alongside the new 2025 artifact.
Q: Where do I see how many credits I have?
A: Settings → Workspace → Credits. The page shows your current available balance, any active holds, and a recent ledger of consumed credits. Admins with billing permission can top up from the same page.
Q: Can I cancel an upgrade in progress?
A: Yes — until it reaches Success. Cancelling a queued or running artifact stops it and releases the held credits. You can't undo a successful upgrade, but you can ignore the artifact (it doesn't have to be downloaded by anyone).
Q: Does upgrading affect my Pirros ID or version history?
A: No. The Pirros ID is shared between the source and all its artifacts, and the original detail or family's history is unchanged. The artifact is an additional file under the same identity.
Q: Can members request upgrades, or only admins?
A: Permissions vary by firm role configuration. By default, admins request upgrades and members consume the resulting artifacts. Contact your CSM if you'd like to change which roles can spend credits on upgrades.