DEV Community

cadguide.tools
cadguide.tools

Posted on

Should You Migrate Your AutoLISP Library? A Decision Framework for CAD Managers

Every CAD manager evaluating a platform switch eventually hits the same wall: the LISP library. It's 10 years of accumulated automation — title-block fillers, layer standardizers, batch plotters — and it's the real switching cost that no pricing calculator accounts for.

Having indexed scripting and API support across 170+ CAD tools at CADGuide.tools, here's the decision framework that actually works.

The compatibility tiers

Tier 1 — runs as-is (GstarCAD, ZWCAD, BricsCAD, DraftSight Professional). These platforms implement AutoLISP with near-identical syntax and function libraries. Most straightforward routines — entity manipulation, layer operations, text handling — work without edits. Command names match; entity models match.

Tier 2 — runs with edits (most platforms with LISP). Expect friction on: routines that call AutoCAD-specific commands missing in the target; file path handling differences; dialog (DCL) edge cases. Budget hours per routine, not days.

Tier 3 — full rewrite required (Revit, SolidWorks, Fusion 360). These don't run LISP at all. Their automation runs on .NET, Python, or proprietary APIs. A LISP-heavy office migrating here is budgeting a complete automation rewrite — often the largest invisible cost of the migration.

The audit protocol

Before choosing a platform, run this:

  1. Inventory every .lsp/.vlx/.fas file with a one-line description and a "used weekly/monthly/never" tag
  2. Test top-ten routines in the target platform's trial — measure success/fail/edit-count
  3. Find the compiled orphans — .vlx and .fas are compiled formats; if you only have the binary without source, that routine is unrecoverable on a new platform. Start rewriting these now regardless of your migration decision
  4. Check Express Tools dependencies — many routines call Express Tools functions; verify the target includes equivalents

The platform recommendation matrix

Your situation Recommendation
2D drafting, cost-sensitive, LISP-heavy GstarCAD ($499 perpetual) or ZWCAD
3D/BIM roadmap + LISP BricsCAD (from $590/yr) — LISP + direct modeling + BIM
2D budget + lowest entry DraftSight Professional ($249/yr)
LISP library is irreplaceable and massive Stay on AutoCAD; negotiate the subscription instead

The meta-lesson

LISP compatibility is the CAD industry's greatest switching-cost mechanism — and the challengers' greatest selling point. The tools that support it do so deliberately, because they know the routine library is the moat. Evaluate accordingly: demo files always work, but your LISP routines vote with real votes.

We track LISP support, API availability, and scripting ecosystems across 170+ CAD tools at CADGuide.tools — free, no signup, no vendor pay-for-placement. Plus a free browser-based PGP alias editor for the command-alias half of your migration.

Top comments (0)