Cross Project Transfer
PremiumTransfer element types between open Revit projects. · Explore the live interface below - every control works exactly as it does inside Revit®.
Architecture
Structure
Steel
Precast
Systems
Insert
Annotate
Analyze
Massing & Site
Collaborate
View
Manage
Add-Ins
NexionTools
Select
Highlight
Rooms
Parameters
Sheets & Views
Data
Manage
QC
Test it Live - exactly as if you are in Revit
Loading interactive demo…
Get Started in Minutes
Four simple steps to bring Cross Project Transfer directly into your Revit® environment.
1
Create Account
Sign up for a free NexionTools account - no credit card required.
2
Download Installer
One installer, 52 professional Revit® tools. Under 15 MB.
3
Open Revit
Cross Project Transfer appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · Manage
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why Cross Project Transfer exists
Revit's Transfer Project Standards is one dialog with a long checkbox list and no idea what is already in the target. You tick what you think you need, run it, and find out afterwards what it overwrote, what it duplicated, and what it did not bring because a dependency was missing.
How Cross Project Transfer works
Open both projects, then pick a source and a target from the documents already open.
The source is scanned and its standards listed by category with counts - families, materials, view templates, filters, types, schedules, sheets, groups, levels, grids, schemes and more.
The target is scanned too, so you can see what already exists there before deciding what to send.
Tick what you want and add it to a queue, building the queue up over as many passes as you need. Then pick how conflicts should be handled and run it. Selecting a family brings all of its types with it - there is no per-type opt-out.
Warning-level messages raised during the copy are dismissed as it goes, so a large transfer does not stop on every minor complaint. Errors still surface.
Before
Standards are transferred blind and the consequences are discovered in the target project afterwards.
After
You can see both sides before committing, so a transfer is a comparison rather than a guess.
When to reach for it
- Setting up a new project from an office template plus a live reference project.
- Rolling a revised standard out to projects already running.
- Bringing a specific set of view templates or filters across without taking everything else with them.
What it does not do
- Both projects must be open in the same Revit session before you launch it. It cannot pull from a file on disk, and a document opened after the dialog is already up does not appear in the lists - you have to relaunch.
- You choose what a conflict means: skip it and keep the target's version, overwrite it - which deletes the target's element and copies yours in its place - or rename, where Revit auto-suffixes the incoming name. Skip is the default.
- A straight transfer is one undo entry. An overwrite is two: one Ctrl+Z removes what was copied, a second restores what was deleted. And if a batch copy fails and the tool retries item by item, each item lands as its own undo entry.
- It transfers standards and the document-level content in the list above - types, templates, schemes, sheets, levels and grids. It does not transfer modelled geometry.
- On a workshared target the elements are not checked out before the copy. The copy fails and the per-item retry is what surfaces the real cause. There is no progress indicator either, so a queue of several hundred items looks frozen while it works.
Questions
- How is this different from Transfer Project Standards?
- The mechanism is similar; the visibility is not. Revit's dialog shows you the source categories and nothing about the target. Here both are scanned and shown side by side, so you know what already exists before you overwrite it - and you choose per run whether a conflict means skip, overwrite or rename.
- Do I need both projects open?
- Yes. Both must be open in the same Revit session - the tool lists the open documents and you pick a source and a target from them.
- What happens if the target already has the same view template?
- You decide, before it runs. Skip mode leaves the target's version untouched. Overwrite deletes the target's version and copies yours in. Rename brings yours in under an auto-suffixed name so both survive. Where a type name collides, the target's type definition wins and the incoming duplicate is discarded.