Migrating from Other Revit Tools

If your firm currently uses DiRoots, Ideate, custom Dynamo scripts, or a mix of point solutions, this guide maps what you have today to what Pyvoid provides. It also covers what Pyvoid does not replace, so you can make an informed decision about which tools to keep, which to retire, and in what order.

Migrating from DiRoots

DiRoots provides 10 tools focused on data exchange, selection filtering, sheet creation, and family management. Pyvoid covers all of these workflows and adds entire categories DiRoots does not address.

What DiRoots migration gains you

Beyond replacing the 10 DiRoots tools, Pyvoid adds entire workflow categories DiRoots does not offer:

• Standards enforcement: Conform Names, Conform Worksets, Template Manager, Spell Check
• Visualization and diagnostics: Warning Visualizer, Health Visualizer, X-Ray (53 visibility conditions)
• Cleanup framework: Wipe Hub (71 registered cleaners), Overkill (geometric overlap detection)
• View template management: Meta View Template Manager with diff, audit, and sync groups
• Governance loop that closes: Audit → Visualize → Fix → Clean → Enforce ↺ — enforcement closes the loop so the next cycle finds fewer issues, with Diagnose folded into Visualize via X-Ray

---

Migrating from Ideate Software

Ideate's core product is BIMLink, a mature Excel-Revit sync tool with 15+ years of development. Pyvoid's DataLink matches BIMLink's core workflow and adds capabilities BIMLink does not have. The practical migration strategy is coexistence first, then gradual transition.

Recommended approach: coexistence

Do not rip out Ideate on day one. Instead:

1. Week 1-2: Install Pyvoid alongside Ideate. Run both.
2. Week 3-4: Use DataLink for one project's Excel sync workflow. Compare results with BIMLink.
3. Month 2: Start using Pyvoid's governance tools (ReViewer, Warning Visualizer, Conform Names) for workflows Ideate does not cover.
4. Month 3-6: Gradually shift Excel sync workflows to DataLink as your team builds familiarity.
5. Month 6+: Evaluate whether Ideate licenses are still needed.

The goal is not to replace Ideate overnight. It is to discover that Pyvoid handles 90%+ of your BIM workflows, and BIMLink was only covering one of them.

---

Replacing Custom Dynamo Scripts

Most firms with 25+ Revit users have accumulated 20-100 custom Dynamo scripts. Some are maintained by people who no longer work there. Every script is technical debt: fragile, undocumented, and dependent on specific Dynamo package versions.

Common scripts Pyvoid replaces

Why framework-backed tools beat scripts

• Preview before apply. Every Pyvoid tool that modifies the model shows a preview. Dynamo scripts execute blind.
• Undo support. All Pyvoid operations use Revit transactions and appear in undo history. Dynamo scripts vary.
• Zero configuration. Click the tool and it works. No graph setup, no package version management, no "ask the person who wrote it."
• Maintained. Tools are tested against Revit 2025-2027 with each release. Scripts break silently when Revit updates.

Migration checklist for scripts

1. Inventory your firm's Dynamo scripts (ask each office to list theirs)
2. For each script, check if a Pyvoid tool covers the same workflow (use CommandHub search)
3. Mark scripts as "replaced," "partially replaced," or "still needed"
4. Retire "replaced" scripts immediately - they are now maintenance liability with no value
5. For "partially replaced" scripts, evaluate whether the gap matters in practice
6. Keep "still needed" scripts but document them as technical debt

---

What Pyvoid Does Not Replace

Honest gaps where you will still need other tools:

Model review markup and persistent annotations. DiRoots ReViewer and Ideate Sticky provide in-model annotation workflows for formal reviews. Pyvoid's ReViewer is a model health dashboard (severity-scored QC), not a markup tool. Most firms use Bluebeam or Revit's revision clouds for formal document review, so this gap rarely blocks adoption.

Proactive style hygiene auditing. Ideate StyleManager provides a dedicated interface for managing line styles, fill patterns, and object styles. Pyvoid covers cleanup (Type Swap, Wipe Hub) but does not have a dedicated style management dashboard.

Enterprise deployment infrastructure (in development). Ideate ships a signed MSI with license server support. Pyvoid's MSI installer is in development (Phase 8). For pilot teams, network-path deployment works. For firm-wide Intune rollout, wait for Phase 8. See Deploying Pyvoid for Your Firm for current options.

---

Phased Migration Plan

For a Digital Practice Lead planning a firm-wide evaluation:

Phase 1: Pilot (Weeks 1-4)

• Install Pyvoid on 3-5 machines via network path
• Run alongside existing tools (do not remove anything yet)
• Focus on one project going through a milestone
• Use ReViewer to baseline model health, then run the governance loop

Phase 2: Expand (Months 2-3)

• Extend to 10-15 users across 2-3 projects
• Start using DataLink instead of BIMLink/SheetLink for Excel sync
• Begin retiring Dynamo scripts that Pyvoid replaces
• Collect time-savings data for ROI reporting

Phase 3: Standardize (Months 3-6)

• Deploy firm-wide via network path or MSI (when available)
• Retire DiRoots and/or Ideate licenses where Pyvoid covers the workflow
• Document remaining script gaps
• Establish the governance loop as a standard milestone-prep workflow

Phase 4: Optimize (Months 6+)

• Configure firm-level settings for naming conventions, template standards
• Train new hires on Pyvoid workflows rather than legacy scripts
• Use Pyvoid MCP for automated governance checks

Last updated: 2026-04-16