Excel Param Sync
PremiumExport and import element parameters via CSV for bulk editing. · 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 Excel Param Sync 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
Excel Param Sync appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · Parameters
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why Excel Param Sync exists
The data lives in Revit. The person who owns the data works in Excel. So it goes out as a schedule export, gets edited in a spreadsheet, comes back as a list of changes, and someone types them into the model. Every round trip is a chance for a row to shift, a mark to be mistyped, or the whole thing to be based on last week's export.
How Excel Param Sync works
Pick your scope - the current Revit selection, everything in the active view, or a whole category - with an optional level filter, and choose instances or types.
Choose which parameters to include. The list is discovered from a sample of the elements in scope and colour-coded, so you can see at a glance what is an instance parameter, what is a type parameter that affects every element of that type, and what is read-only.
Export to an Excel workbook or a CSV. The colour coding travels with the workbook, and an instructions sheet tells whoever edits it not to touch the ElementId column, rename the sheets or remove the header rows - that column is the key the import matches on.
Load the edited file back and you get a diff before anything is written: how many values changed, how many are type-level changes, how many conflict, how many are unchanged.
Review the proposed changes, untick anything you disagree with, and commit only what you approved. Approving a type-level change raises a warning first that counts how many elements it would reach, and the whole commit lands as one undo entry.
Before
Changes come back as a marked-up spreadsheet and get retyped into Revit by hand, with no record of what actually differed.
After
The workbook goes back in the way it came out, and you approve a reviewed list of differences instead of trusting a file.
When to reach for it
- Room data sheets maintained by a client or a specialist consultant.
- Equipment and asset schedules owned by an FM team who will never open Revit.
- Any parameter set that is easier to review as a grid than in the Properties palette.
What it does not do
- It syncs values on elements that already exist. It does not create parameters, families or elements.
- Read-only parameters are marked as such and cannot be written on import - they export for reference only.
- It is a deliberate export-and-import round trip, not a live link to an open spreadsheet.
- Type parameters change every element of that type. They are flagged separately in the diff for exactly that reason.
- Rows the tool cannot write - a read-only parameter, or a value that does not fit the parameter's type - are flagged as conflicts and their checkboxes are disabled. You cannot approve those; they need dealing with at the source.
- The parameter list comes from a sample of the elements in scope, so on a mixed set a parameter that only a handful of elements carry can miss the sample and never be offered.
- Two rows for the same element resolve last-value-wins, and the result dialog tells you when that happened.
- On a workshared model, elements owned by other users are checked out where possible; the ones that stay locked are dropped and counted as failures, with no warning beforehand. Family documents and read-only documents are refused outright.
Questions
- Can I edit Revit parameters in Excel and push them back?
- That is what this does. Export the parameters to a workbook, edit it, load it back, and review the differences before committing them.
- Does it overwrite values that changed in Revit since the export?
- The diff is computed against the current model rather than against the export, so a value someone changed in Revit since you exported appears as an ordinary change with the live value in the current column. You see it before it is written, but the tool does not flag it as a clash - read that column. What it does flag as conflicts are the rows it cannot write at all: read-only parameters, and values that do not fit the parameter's type.
- What happens if I delete a row from the spreadsheet?
- That element is simply not part of the import. Removing a row does not delete anything from the model.
- How do I know which parameters are safe to edit?
- The exported file keeps the colour coding from the dialog - instance, type, and read-only are visually distinct, so the person editing the sheet can tell without asking you.