Field note / CAD detail migration

Not every detail
needs converting.

Link, import, explode or redraw? Start with the decision the detail must support, not the command you know best.

Find a starting route Follow a synthetic example

Draft educational guide for 2D CAD details in Revit. No upload, sign-up or purchase. This page does not inspect files, run conversions or save your decisions.

01 / Check the premise

Does this detail deserve a place in the library?

First confirm the right to reuse the source, its current technical intent and an accountable reviewer. A familiar detail is not automatically an approved detail.

Rights, currency or technical intent uncertain? Hold for review. A conversion cannot resolve those questions.
Approved source, reference only? Decide whether updates must remain connected.
Approved source, native editing required? Compare an explode trial with a redraw.

These are Nova decision prompts, not Autodesk instructions or a compliance assessment. Confirm behavior in your own Revit version, view context and firm standards.

02 / Choose a test, not a promise

What must the next person be able to do?

Use it as a reference

Will the CAD source keep changing, with someone responsible for supplying and reloading revisions?

Yes: start with linking, then test the reload handoff.
No: compare linking with an unexploded import only if your firm's delivery rules allow it.
Unknown: hold until someone owns the source and its revision process.

Autodesk generally prefers linking for manageability and reloading changes. An import is not a native-detail conversion. See source 1.

Edit it as native detail content

Is the source approved and simple enough to compare a bounded trial against a manual rebuild?

Yes: test an explode on a disposable copy against a native redraw.
No, but intent is approved: scope a redraw with the reviewer.
Intent or acceptance criteria unclear: hold rather than automate the uncertainty.

A linked file cannot be exploded. Full explode can create Revit text, curves, lines and filled regions; it does not certify their suitability. See source 2.

Four routes. Different handoffs.

Reference / Connected source

Link

Test when: the CAD file stays authoritative and revisions are expected. Autodesk documents loading, unloading and updating links on reload.

Accept only after: checking units, position, layer visibility and plotted appearance, then reloading a deliberate test revision.

Handoff: name the source owner and approved file location. Test access from the receiving team's environment; a working local path is not a completed handoff.

Reference / Embedded snapshot

Import without exploding

Test when: a fixed reference is allowed and someone accepts responsibility for replacing it if the source changes. Do not treat it as a reloadable link.

Accept only after: checking units, position, visibility and plotted output against the approved source.

Handoff: record the source revision and replacement trigger. Embedding the drawing does not make its content technically current or editable as native detail elements.

Native editing / Controlled trial

Explode an imported copy

Test when: native editing is required and the source warrants a cleanup trial. Work in a disposable, non-production project, not the shared library.

Know the limit: partial explode can leave nested import symbols. Full explode creates Revit elements. Autodesk says linked files and imports yielding more than 10,000 elements cannot be exploded.

Accept only after: reviewing resulting styles, text, fills, geometry and plotted output. Include cleanup and review time; Autodesk warns that exploded imports can affect model performance.

Native editing / Deliberate rebuild

Redraw to the approved standard

Test when: native editing is needed but the source is inconsistent, or trial cleanup exceeds the effort cap agreed with the reviewer.

Accept only after: comparing the rebuilt geometry, annotations, dimensions and print output with the approved intent. Redrawing is not permission to redesign a construction detail.

Handoff: record the reviewer, accepted revision and any intentional departures. Do not call it approved just because it is native.

03 / A synthetic decision

The same drawing.
Two different needs.

Imagine an authorized training detail: a few lines, a filled area and notes. No project data, no engineering assertion and no measured productivity claim.

Need A: keep a changing CAD reference visible. The route is a link trial with a deliberate revision/reload check, not a conversion.

Need B: create reusable, natively editable library content. The route is a comparison between a full-explode trial and a redraw, with identical review criteria.

Illustrative planning example only. No Revit trial was performed for this guide; the outcome remains undecided until reviewed.

Decision / Not a benchmarkSynthetic example

Define the stop condition first.

Candidate: Training detail A, approved test copy
Native requirement: Editable lines, notes and filled region
Review owner: Designated library reviewer
Effort cap: 30 minutes per route, then review
Evidence: Preparation + execution + cleanup + review + rework time
Stop condition: Intent cannot be verified or cap is reached
Decision: Pending trial; neither route accepted yet

The effort cap is a made-up planning choice, not a recommended duration or savings estimate.

04 / Leave a usable decision

A short record beats an undocumented conversion.

Copy these prompts into your own approved local notes. Nothing you write there is submitted to this site. Use synthetic identifiers for a trial and do not send client drawings.

Detail ID and source revision:
Reuse authority and technical-intent reviewer:
Required outcome: reference / native editing / hold
Revit version, view context and firm standard:
Candidate route(s) and reason:
Source owner and revision/reload or replacement trigger:
Acceptance checks: units, position, geometry, text,
  dimensions, fills, styles and plotted output
Effort cap and stop condition:
Observed preparation / execution / cleanup / review / rework:
Unresolved issues and who can resolve them:
Decision: accept / revise / hold / propose retirement
Reviewer, decision date and next review trigger:

Compare total observed effort for the same accepted outcome, not the speed of one command. A route that produces more cleanup or an unapproved result has not demonstrated a saving.

Optional / After the decision

Use the guide without buying anything.

The route and review record above are a complete starting point. If the next problem is organizing a repeatable migration, these separate draft offers may be relevant.

Need a common mapping and review method?

See the proposed mapping workbook, migration playbook and QA checklist. They are planning resources, not automated converters.

Draft catalog; purchasing and downloads are not enabled.

Explore the draft migration resources

Considering a software trial later?

Review the proposed Codex evaluation scope before deciding whether a DXF-focused workflow belongs in your comparison. This guide demonstrates no Codex capabilities or results.

Invite-only early-access plan, subject to eligibility and release gates; not a public download or an availability guarantee.

Read the draft evaluation criteria

Sources, edition and limits

The software behavior summarized here comes from the official Revit 2025 help pages below, checked 13 November 2026. These external links leave this site only when you follow them. No Autodesk content is embedded.

Autodesk: About Importing or Linking CAD Files (Revit 2025). Source for link management, reload behavior and the performance caution for exploded imports.
Autodesk: Explode Imported Geometry (Revit 2025). Source for partial/full explode, linked-file restrictions and the element limit.

The decision path, review prompts and synthetic example are original Nova guidance. They have not been independently practitioner-validated. They do not establish technical adequacy, standards compliance, product compatibility or a project-specific design decision. Obtain the appropriate professional and firm review before reuse; confirm instructions for your installed release.

Local draft preview. Entity, domain, legal, content and product release checks remain outstanding. This guide is not publication approval.

Back to the resource collection