Home / Apps / Graft
Setup panelGraft

Your standards. Every model. Only the parts you choose.

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.

Any open model, link or .rvt on disk as the sourceRevit 2024–2027Fully reversible — every pass is a named undo step
▶Video guideComing soon on BIMIO’s YouTube
FileArchitectureStructureInsertAnnotateViewManageAdd-InsModify
The BIMIO tab: the apps, each with its own licence.
Why Graft exists

Native Transfer Project Standards is all-or-nothing — and blind.

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.

Revit on its own
  • Transfer a whole category — every view template, or none.
  • No preview of what's new, what differs, or what's already identical.
  • Nothing warns you before you overwrite a type that's in use.
  • Schedules, legends, groups and loadable families aren't on Transfer Project Standards' list at all.
The same job, with Graft
  • Pick one view template, three filters, that wall type — item by item.
  • Every standard flagged: new, differs, identical, or locked.
  • In-use types are never overwritten; templates keep their views and bring their filters.
  • Schedules, legends, drafting views, model and detail groups and loadable families travel too.
How Graft works · input → output

One person curates the transfer. The model gets exactly that — safely.

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.

Isolate:
INInput · you pick it
A source + the exact standardsBIM Manager
Any open model or linkCompared vs the active modelTicked item by item
OUTOutput · the model gets it
✓New · copied in
!Differs · overwritten — your call
•Locked · never touched — the row says why
–Identical · skipped
consistent standards — a named undo step away

Tap Input or Output to isolate a half — the other collapses.

INThe input · pick the source and the standards

Point Graft at a model, and choose standard by standard.

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.

Who does this: BIM Manager / Coordinator

Curates the transfer. Chooses the source and the exact standards; the model only ever gets what's ticked.

Step 1 · Point it at a source

Any open model, link or file on disk is a source — the active model is the target.

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.

Who: BIM Manager picks the source
BIMIO · Graft — Standards transfer
Graft
Transfer project standards with item-level control.
1264 standards loaded across 63 categories. Pick what to graft.
SourceLink · Practice Standards 2026RefreshProfileOffice 2026ApplySaveDelete
Search everything…Select allClearnewdiffersidenticallockedOnly differences
▾Views7 categories · 212 items
Search this group…
▸Browser Organisation1 new1 in use0/5
▸Filters9 new6 differ0/52
▸Schedules17 new8 differ2 in use0/64
▾View Templates4 new2 differ3/7
Search this category…
A-3D — Model Review3 viewshere: 2 views
A-CEILING PLAN — Presentation9 views
A-ELEVATION — Presentation14 views
A-FLOOR PLAN — Working41 views
A-SECTION — Coordination34 viewshere: 6 views⇄compare
A-SITE — Context2 views
S-FRAMING — Coordination8 viewshere: 3 views⇄compare
▸Drafting Views12 new3 differ2/38
▸Legends6 new3 differ1/40
▸Scope Boxes2 new0/6
▸Families31 categories · 438 items
▸Groups2 categories · 46 items
▸Manage18 categories · 534 items
▸BIMIO app data5 categories · 34 items
Tick what to bring into the current model · view templates pull in their filters automatically · the counts show how much of each model leans on a standardRename what arrivesDeviation…PreviewGraft 10 selected →
Families come with their types

Loadable families cross over too — family by family, type by type.

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."

BIMIO · Graft — Standards transfer
▾Families31 categories · 438 items
Search this group…
▾Doors1 new1 differs1 in use2/3
Search this category…
▾M_Double-Flush6 placedⓘ
1526 x 2040mm6 placed
▾M_Single-Flush48 placedhere: 39 placedⓘ⇄compare
0826 x 2040mm18 placedhere: 12 placed⇄compare
0926 x 2040mm22 placedhere: 27 placed
1026 x 2040mm8 placed
▸M_Sliding-2 Panel14 placedhere: 31 placedⓘ⇄compareCompared on type parameters (and layer structure where a type has one). A family's geometry, formulas and nested families can't be read without opening it, so two same-named types that differ ONLY inside read as identical here.
Step 2 · See before you touch

Know exactly what drifted — before you overwrite.

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.

Who: BIM Manager compares
BIMIO · Graft
What differs
A-SECTION — Coordination
FieldSourceDestination
Changed value4
Detail Level21
View Scale50100
Structural Columnsvisible · cut pattern <Solid fill> · cut pattern colour RGB 255,0,0visible
Walls › Cut Patternhiddenvisible
Only in the source1
Filter “FIL-Existing-Demolished”visible · halftonenot applied
Hover a value to read it in full · Ctrl+C copies the selected rows with their headers
Explain with AIClose
How far off are we?

One press measures how far the whole project has drifted.

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.”

New to Revit: a measure of how far a project has drifted from the office standard, category by category and standard by standard.
Who: BIM Manager measures
this model — deviation from Link · Practice Standards 2026
How far this project has drifted
Standards deviation
this model measured against Link · Practice Standards 2026
2026-08-29 09:32 · ajones
81%
match the reference
96
differ
133
missing here
14
differ but in use
Where it diverges
GroupCategoryDivergesOfMatch
FamiliesWindows419657%
FamiliesFloor Types315847%
ViewsSchedules276458%
ManageMaterials2214084%
ViewsDrafting Views153861%
ViewsFilters155271%
FamiliesWall Types124774%
The two settings that were one tick

Object styles and project units stopped being one tick each — and every refusal names itself.

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."

BIMIO · Graft — Standards transfer
▾Manage18 categories · 534 items
▾Object styles · Model objects2 differ1 locked2/58
Search this category…
▸Ceilings
▸Doors
▾Windows
(the category's own style)The source leaves material blank, and Revit's API can only SET one of these, never clear it. Clear it by hand in Manage ▸ Object Styles if you want the two to match.
▾Units · Common2 differ1/25
Search this category…
Angleⓘ
Lengthⓘ
Parameters travel too

Project parameters cross over — copied the way Revit's own transfer does.

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".

Who: BIM Manager picks the parameters
BIMIO · Graft — Standards transfer
▾Parameters · Identity Data2 new1 differs3/4
Search this category…
Acoustic Ratingⓘ
Fire Compartmentⓘ
Hardware SetⓘText · Type · Doors · project parameter (not shared) · copied as a project parameter, the way Transfer Project Standards does
Room Functionⓘ
Your BIMIO standards travel too

The suite's own rule books ride the same gesture.

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.

New to Revit: a transfer that carries the office's add-in standards, not just Revit's.
BIMIO · Graft — Standards transfer
▾BIMIO app data5 categories · 34 items
Search this group…
▸Canon — Standards rules3 new1 differs4/12
▾Palette — Filter sets2 new1 differs3/4
Search this category…
Acoustics
Existing / demolition
Façade
Fire rating
▸Plot — Publish presets4 new2 differ0/11
▸Clash — Rules2 new2/6
▸Plot — File naming1 differs1/1
One pick, every project

Save the pick as a profile, and roll one office standard across every project.

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.

Who: BIM Manager keeps the office set
Save profile
Save profile
Name for this profile (46 standard(s)). Saving over an existing name replaces it.
Office 2026
CancelOK
Your naming, on arrival

What lands can take the office's naming on the way in.

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.

Who: BIM Manager names what lands
BIMIO · Graft — Standards transfer
FindReplace withPrefixPS-Suffix
«FIL-Existing-Demolished» lands as «PS-FIL-Existing-Demolished»
Tick what to bring into the current model · view templates pull in their filters automatically · the counts show how much of each model leans on a standardRename what arrivesDeviation…PreviewGraft 10 selected →
One click on Graft N selected →

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.

OUTThe output · the model gets exactly the pick

Only what you chose — resolved, protected, reversible.

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.

Who lives this: the whole project team

Gets a model aligned to the standard, without losing anything already placed or assigned.

Step 3 · Your call on conflicts

Already there? Overwrite, keep yours, or keep both — you decide.

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.

Who: BIM Manager confirms
BIMIO · Graft
Some items already exist
10 item(s) selected — 3 already exist here with differences. Decide each one:
1 more are already identical and will be kept as-is (nothing to decide).
DECIDE EACH ONEOverwrite allKeep all mine
A-SECTION — CoordinationView Templates
Overwrite mineKeep mineBring asA-SECTION — Coordination (Practice Standards 2026)
INT 100 PartitionWall Types
Overwrite mineKeep mineBring asINT 100 Partition (Office)
FIL-Fire-EI60Filters · used by a ticked view template
Overwrite mineKeep mineBring as
Overwrite replaces yours with the source version · Keep leaves yours alone · Bring as lands the source version under another name and keeps yours too. Types in use are never offered here.
CancelKeep allGraft
Step 4 · Safe by construction

It refuses to break your 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.

New to Revit: Revit's own Transfer Project Standards can't cherry-pick a single standard, or show you what differs before you commit — it moves whole categories, blind.
Who: Graft guarantees it
BIMIO · Graft — Standards transfer
▾Wall Types1 new1 differs2 in use2/4
Search this category…
EXT — Brick cavity 300mm26 placed
EXT — Rendered block 250mm12 placedhere: 48 placed⇄compare
INT 100 Partition64 placed⇄compare
INT 75 Partition37 placedhere: 112 placed⇄compareIn use in this model — Revit can't replace it in place, so it can't be grafted here. Update it with Revit's Transfer Project Standards.
Step 5 · The receipt

Four numbers, one honest summary.

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.

Who: The team gets the aligned model
BIMIO · Graft
Standards grafted
The selected standards were transferred into the current model.
9new
1overwritten
0protected
1 already identical · 1 kept by your choice
• Kept existing: FIL-Fire-EI60
• Re-applied template 'A-SECTION — Coordination' to 6 view(s).
• Brought 'INT 100 Partition' in as 'INT 100 Partition (Office)' — yours was left untouched.
• Overwritten standards reuse this project's existing sub-standards (materials, patterns, embedded profiles) wherever names matched.
Export report…Done
What it can't be sure of

Then it tells you how its own list could now be wrong.

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.

BIMIO · Graft — Standards transfer
Graft
Transfer project standards with item-level control.
Grafted 9 new · 1 overwritten · 1 already identical · 1 kept.
Last grafted from 'Link · Practice Standards 2026' on 2026-08-29 09:40 by ajones — 10 standard(s).
Every row the graft touched was re-checked against this model. 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. Refresh to re-read everything.RefreshRe-read the source model so every mark is measured again.
Replacing without replacing

The safest way to replace a standard is not to replace 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.

BIMIO · Graft
Standards grafted
The selected standards were transferred into the current model.
0new
3overwritten
1protected
1 already identical · 1 kept by your choice
• Kept existing: FIL-Phase-Temporary
• Protected filter 'FIL-Zone-Existing': one of its rules pins a specific type or element (e.g. Type = X, Level = L2), which Graft can't reliably remap to this model, so it was left unchanged. Update it with Revit's Transfer Project Standards.
• Re-applied filter 'FIL-Demolition' to 23 view(s), keeping their overrides (re-added at the END of each view's filter list — if you layer overlapping filters, check the order).
• ⚠ Filter 'FIL-Demolition' couldn't be re-applied to 2 view(s) — the new version's categories no longer match them. Re-add it there by hand if you need it.
• Overwritten standards reuse this project's existing sub-standards (materials, patterns, embedded profiles) wherever names matched.
Export report…Done
See the real output

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.

Open full report

Bring your standards across — exactly, and safely.

Graft is on the BIMIO tab, in the Setup panel: one button, nothing to configure.

← PreviousDatum