Revit's Transfer Project Standards moves whole categories, blind. Graft is the granular, safe version: one list shows every standard a source model has, verdict by verdict, against what you already have — you pick standard by standard, and nothing you can't safely replace is ever overwritten.
Revit moves a whole category of standards or none of it, with no view of what already exists, what has drifted, or what's risky to replace. So teams either flood the model or avoid the tool entirely.
Graft has two halves. A BIM Manager inputs the pick — a source model and the exact standards to bring. The active model gets the output — only those standards, in named, reversible steps. Here is the whole loop.
Tap Input or Output to isolate a half — the other collapses.
Any project open in the session — a link loaded in your model, or a .rvt picked straight from disk — becomes the source. Graft reads its standards, compares them to yours, and hands you one pick list where every name carries its verdict.
Pick a source from the drop-down: another project open in the session (Open · name), a Revit link loaded in your model (Link · name) — or Select model… to open a .rvt straight from disk. Until you do, the list says just that: Select a model to graft from…. Graft then loads every transferable standard and lines it up against your current model in one list, folded the way the Project Browser is — Views, Families, Groups — then Manage and BIMIO app data, each band a set of category cards in two columns. A colour before each name says it at a glance — green new, amber differs, grey identical, blue locked — and beside it, how much of each model leans on it: “34 views” over there, “here: 6 views” at home. Opened or closed a model mid-session? Refresh re-scans the sources — and keeps the one you picked selected.

Revit's own Transfer Project Standards cannot carry a loadable family at all. In Graft they sit in the Families band, where the Project Browser lists them, beside the system types: one card per family category — discovered from the source model rather than hardcoded, and titled with Revit's own category names, so nothing lands in an "Other" bucket. A row is the family; open it and its types sit underneath. Tick the family and every type comes; tick one type and only that one moves. In-place families are left out, because Revit refuses to load them into another model anyway. And every family row carries its own limit on its face: geometry, formulas and nested families can't be read without opening the family, so "two same-named types that differ ONLY inside read as identical here."
On anything that differs, a compare chip opens What differs — one grouped table, field by field, the source value against yours: what changed value, what exists only in the source, what exists only here. So you decide from data, not memory. The match is by name, within each category, across every readable parameter — per-model noise (Workset, Edited by, IfcGUID) excluded so it never cries wolf — and it goes deeper than parameters: a wall type's layer stack, a view template's graphic overrides down to each subcategory and fill, a filter's rules and a schedule's whole definition are all fingerprinted, so a change hiding in any of them still flips the verdict. The one thing Revit gives no way to read — a schedule's formula column — is flagged on the row rather than guessed at. And when a diff needs words, Explain with AI turns the rows on screen into one plain sentence, through the AI provider you connected in Synapse.
| Field | Source | Destination |
|---|---|---|
| Changed value4 | ||
| Detail Level | 2 | 1 |
| View Scale | 50 | 100 |
| Structural Columns | visible · cut pattern <Solid fill> · cut pattern colour RGB 255,0,0 | visible |
| Walls › Cut Pattern | hidden | visible |
| Only in the source1 | ||
| Filter “FIL-Existing-Demolished” | visible · halftone | not applied |
Deviation… answers a different question from a graft: not what to bring, but whether this project is still on the reference at all. It needs nothing ticked — it reports over everything loaded — and opens one self-contained page in your browser: the share of standards that match the reference, how many differ, how many are missing here, how many differ but are in use, then every category worst first, then every diverging standard by name. It measures distance FROM the reference, so a standard the reference hasn't got is not counted as drift, and nothing is written to either model. The status line keeps the answer: “243 of 1264 standards diverge from 'Link · Practice Standards 2026' — report opened in your browser.”
| Group | Category | Diverges | Of | Match |
|---|---|---|---|---|
| Families | Windows | 41 | 96 | 57% |
| Families | Floor Types | 31 | 58 | 47% |
| Views | Schedules | 27 | 64 | 58% |
| Manage | Materials | 22 | 140 | 84% |
| Views | Drafting Views | 15 | 38 | 61% |
| Views | Filters | 15 | 52 | 71% |
| Families | Wall Types | 12 | 47 | 74% |
Both used to be a single checkbox, and one tick rewrote every line weight, colour and pattern in the project, or replaced its whole unit set. Now they are cards in the Manage band, each named for what it is: Object styles · Model objects and its two siblings, a row per category and subcategory across the three tabs of Revit's Object Styles dialog; Units · Common and the other Manage ▸ Project Units disciplines, a row per unit — 155 of them in a real model. Neither is matched by the label Revit prints: a category is its BuiltInCategory number, a unit is its schema id, both the same in every language, so a Spanish source reads correctly into an English project. A unit that differs says how on its ⓘ — both formats, and what differs between them. And a row that cannot move says why on the row, including the case nobody thinks to check: "The source leaves material blank, and Revit's API can only SET one of these, never clear it."
The Manage band also lists the parameters the source binds, one card per properties group — Parameters · Identity Data, Parameters · Constraints… A row is a binding: what the parameter is, Instance or Type, and the categories it is bound to, all on its ⓘ. A shared parameter pairs with yours by its GUID, so a rename on either side is still the same row; a project parameter, which has no GUID, pairs by name and data type. And each row says how it will travel: a new project parameter is "copied as a project parameter, the way Transfer Project Standards does"; a shared one missing from your shared-parameter file is "rebuilt with the source's own GUID", and Graft points Revit back at your file afterwards. Categories are only ever added — Graft never unbinds one, because the values stored against it would go with it — an existing parameter keeps its Instance or Type binding, and the whole pass is its own undo step, "BIMIO Graft — shared parameters".
Graft doesn't stop at Revit's standards. The last band, BIMIO app data, holds the rule books and presets the suite's own apps keep in each model, one card per app's set: Canon rule books, Clash rules, Palette filter sets, Plot's file naming and publish presets, Select rules, Synapse's authored rules, keynote memories and more. Each app reads and writes its own payload — Graft compares fingerprints and carries exactly what you tick — so a project's whole working standard, Revit's and BIMIO's, moves in one pick.
A profile is a saved pick — the category and name of each standard you ticked, never the standards themselves — kept as one small file per profile under %AppData%\BIMIO\Graft\profiles, so copying the folder shares it with the team. Tick the set once, press Save and name it. In the next project, read its source, choose the profile and press Apply: it ticks every loaded standard the profile names and says out loud what it couldn't — "Profile 'Office 2026': ticked 41 of 46 · 2 in use (can't be grafted here) · 3 not in this source." A family ticked whole is remembered as the family, so it follows one that gained a type; a family ticked in part is remembered type by type, so the ones you left out stay out.
Tick Rename what arrives, beside the graft button, and a card opens above it with one rule: find and replace, then a prefix and a suffix. Under the fields the rule is read as a result, on a real name from your list — «FIL-Existing-Demolished» lands as «PS-FIL-Existing-Demolished». It names every NEW type, view template, filter, phase filter, material and pattern as it lands; what is already here keeps its name, and so do families, groups, views, schedules, phases and line styles. The rename happens after the copy, so whatever points at a new standard still points at it, and a name Revit won't take — already used here, or a character it doesn't allow — leaves that standard under its own name, with a note in the receipt saying so.
and only the standards you ticked are copied into the active model, in one transaction named “BIMIO Graft — transfer standards.” Object styles, units, parameters, groups and BIMIO's own data land in their own named, equally reversible steps.
The transfer runs as named, reversible steps. Conflicts are yours to resolve — item by item — in-use types are locked out, and the receipt says exactly what happened.
If anything you ticked already exists with differences, Graft asks once — and item by item. Each conflict gets its own call: Overwrite mine takes the source version, Keep mine leaves yours exactly as it is, Bring as lands the source version under another name and keeps yours too. Select several rows and the answer you give one goes to all of them. A filter that only a ticked view template brought along gets a row of its own — overwrite it or keep yours, never under another name, because the template finds its filter by name. Identical twins never even ask — they're kept either way — and with no differing conflicts there is no dialog: the graft just runs. With Rename what arrives on, a Bring as name starts from the one the rule gives; otherwise it comes filled in with the name and, in brackets, the source model.
A type that differs from your model but is in use — instances placed — gets a blue dot and a disabled checkbox, so you can't even try to overwrite it: deleting it would take those instances down with it. Hover it and Graft tells you exactly why, and what to use instead. Everything you can pick lands with its dependencies already in order, a named undo step away.
When it's done, Graft shows exactly what happened: new copied, overwritten, protected (left untouched to save what hangs off them), and skipped — the skip broken down by cause underneath, and a note for everything it kept, re-applied, renamed or refused. The coloured dots re-read automatically, so a freshly grafted row settles to grey — identical. Export report… writes the receipt to a single self-contained HTML file, in the language BIMIO's interface speaks. And the panel writes the graft into the model's own record, so “is this project on the office standard?” stops living in somebody's memory — and Deviation… answers it in full.
After a transfer, Graft re-checks every row the graft touched instead of re-reading the whole source model — which is the wait this design exists to remove. So it says out loud what that leaves open: "Copying can also bring in materials, patterns and nested families nobody ticked, so a row still marked “not here” may already be in the project." If a row couldn't be re-checked, or a tick had to be cleared because that item turned out to be in use here, the note counts those too. It has no close button, on purpose: dismissing it would take away the warning and leave the badges it warns about. Only a real re-read — its own Refresh button — clears it.

Overwriting normally means deleting your copy and copying the source one in — and everything hanging off the old element goes with it. So Graft avoids the delete, element by element; the picture is another graft, filters only. A filter whose rules only test built-in parameters is rewritten in place: the element never dies, so every view it drives keeps its own overrides. A rule that pins a type or a level — Type = X, Level = L2 — is rebuilt for this model by name (the type, the level, the parameter, a shared one by its GUID) and written in place too. All or nothing: if one of those names has no twin here, the whole filter is left exactly as it was, and the receipt says so. Where the delete is unavoidable — a rule on a shared or project parameter's value — Graft captures each view's overrides, visibility and enabled state first and re-attaches them after. A line or fill pattern takes the source's definition in place, so every line style and material that points at it keeps it; a material, a scope box, a colour fill scheme, a phase filter or a browser organisation — things other elements point at — is locked on its row instead, with the reason. A schedule whose definition can be reconciled is rebuilt in place, so its sheet placements survive. And a filter Revit fails to re-create rolls the whole transfer back.
This is an actual HTML report Graft exports — self-contained, works offline, shareable as one file. Scroll it right here, or open it full-screen.
Graft is on the BIMIO tab, in the Setup panel: one button, nothing to configure.