Migrating Your AutoLISP Routines to a New CAD Platform: A Field Checklist

The biggest hidden asset in an established CAD office isn't the software license — it's the folder of AutoLISP routines that accumulated over a decade. The drawing title-block filler, the layer standardizer, the batch plotter. When teams evaluate switching platforms, "does our LISP survive?" is the make-or-break question.

The good news: GstarCAD, ZWCAD, BricsCAD, and DraftSight Professional all support AutoLISP. The honest news: "support" has degrees. Here's the field checklist we give teams doing this migration.

Phase 1: Inventory before anything moves

• Catalog every routine with a one-line description of what it does and who uses it. You'll find a third are dead code — deprecated standards, tools for retired clients
• Rank by business value: daily-use utilities first, weekly tools second, archive the rest
• Check for external dependencies: routines that shell out to exe files, read specific registry paths, or hardcode network folders need those targets verified on the new platform

Phase 2: The compatibility triage

Test each routine in a trial install of the target platform and sort into three buckets:

Bucket 1 — runs as-is. Most straightforward routines (entity manipulation, layer operations, text handling) land here. Command names and entity model are compatible across the LISP-supporting platforms.

Bucket 2 — runs with edits. The usual suspects:

• Routines calling AutoCAD-specific commands that differ or don't exist in the target (check each command call against the target's command set)
• VLX/FAS compiled routines — the compiled formats are platform-specific; you need the original LSP source. If the source is lost, that routine is effectively dead — plan a rewrite
• File path and dialog calls (DCL dialogs mostly port, but test them)

Bucket 3 — replace or rewrite. Routines deep in ActiveX/COM automation against AutoCAD's object model, or reliant on Express Tools functions, may have no equivalent. Budget rewrites for these based on the business value ranking from Phase 1.

Phase 3: The migration itself

• Move in waves by value: daily-use routines first, with real-project testing — not synthetic drawings
• Version-control the library before you start (a plain git repo beats a folder named "LISP_final_v2_REALLY")
• Standardize the load path (suite loader / startup suite) on every workstation once, not per-user
• Keep one AutoCAD seat alive during transition for the routines that haven't moved yet

Phase 4: Prove it on production work

Run a live project in parallel: same drawings, old platform and new, routines exercised daily. The DWG round-trip test matters as much as the LISP test — open your messiest production file, run the routine suite, save, reopen in AutoCAD, verify. Two weeks of this catches 95% of what demo testing misses.

The platform reality check

From our index: GstarCAD ($499 perpetual) and ZWCAD (from $899) carry AutoLISP with near-identical command aliases; BricsCAD (from $590/yr) supports LISP plus many AutoCAD plugins directly and is the strongest choice if a 3D/BIM roadmap matters; DraftSight Professional ($249/yr) includes LISP at the lowest entry price. Revit and SolidWorks users don't get LISP at all — that ecosystem runs on different APIs (.NET, VSTA), so LISP-heavy teams migrating there face full rewrites, not ports.

Whichever way you lean, the trial is free and the checklist above is the difference between "our tools work" and month three of regret. We track API/scripting support across 170+ CAD tools at CADGuide.tools — free, no signup — plus a browser-based PGP alias editor for the command-alias part of the move.