How to Migrate Custom Files to BricsCAD

Quick answer: BricsCAD can take in nine types of custom files from AutoCAD or a previous BricsCAD release: partial customization files, linetypes, hatch patterns, drawing templates, plot files, tool palettes, command aliases, shape files, and LISP files. Most involve copying a definition from one specific file in AutoCAD’s Support folder into the equivalent file in BricsCAD’s. Upgrading between BricsCAD versions is different, and largely automatic.

Where BricsCAD Stores These Files

Two folders matter most:

• Installation folder: C:\Program Files\Bricsys\BricsCAD V26 en_US
• Support folder, where most user-customizable files live: C:\Users\%username%\AppData\Roaming\Bricsys\BricsCAD\V26x64\en_US\Support

Use the SETTINGS command to configure support paths, Xref locations, and plotter locations. Use CUSTOMIZE to change menus, ribbons, and mouse button actions.

Partial Customization Files (CUI/CUIX)

Only partial customization files migrate, not the main CUI or CUIX file itself. A CUIX file is a zipped package containing everything the interface needs.

Custom Linetypes

Both AutoCAD and BricsCAD keep linetype definitions in LIN files in their Support folders, with separate files for imperial and metric.

Imperial: Open AutoCAD’s acad.lin, find the User Defined Linetype section, and copy your custom definition. Open BricsCAD’s default.lin, paste it at the end, and save.

Metric: Same process, from AutoCAD’s acadiso.lin to BricsCAD’s iso.lin.

If your custom linetypes live in a separate file entirely, copy that file into BricsCAD’s Support folder and load it via the Load Linetypes dialog. For complex linetypes that reference shape files, copy the SHX or SHP files into the Support folder too.

Run the LINETYPE command afterwards to confirm the migration worked.

Custom Hatch Patterns

Same imperial/metric split as linetypes, but with PAT files.

Imperial: AutoCAD’s acad.pat to BricsCAD’s default.pat.

Metric: AutoCAD’s acadiso.pat to BricsCAD’s iso.pat.

For patterns stored elsewhere, either drop the file into BricsCAD’s Support folder or add its location to the Support file search path in the Settings dialog (the SRCHPATH system variable).

Confirm the migration by running HATCH and checking Predefined or Custom in the Type field.

Custom Drawing Templates

Drawing templates are DWT files. Find the source location in AutoCAD via OPTIONS > Files tab > Template Settings. Find the BricsCAD location via the TEMPLATEFOLDER command. Copy and paste between the two.

Test it by clicking More… on BricsCAD’s Start page.

Custom Plot Files

Two separate things here:

Plot style tables (CTB/STB): In AutoCAD, run STYLESMANAGER to open the Plot Styles folder and copy the files. In BricsCAD, the same command opens a folder called PlotStyles instead, paste the files there.

Plotter configuration files (PC3): In AutoCAD, run PLOTTERMANAGER to open the Plotters folder and copy. In BricsCAD, the same command opens a folder called PlotConfig, paste there.

Test either by running PLOT and checking the relevant drop-down in the Print dialog.

Custom Tool Palettes

BricsCAD reads XTP files (the shared format) plus ATC files (AutoCAD’s own palette format) and BTC files (BricsCAD’s equivalent).

In AutoCAD, run TOOLPALETTES, right-click the panel, choose Customize Palettes…, right-click the palette you want, and choose Export… to save it as an XTP file. In BricsCAD, run the same TOOLPALETTES command, right-click, Customize Palettes…, then Import and select that XTP file.

Worth creating a dedicated folder for custom tool palettes inside BricsCAD’s Support folder to keep them organized.

Custom Command Aliases

Command aliases live in PGP files. Open AutoCAD’s acad.pgp, find the User Defined Command Aliases section, and copy your definitions. Open BricsCAD’s default.pgp, paste them at the end, and save.

Custom Shape Files

Copy both the SHP and SHX files from AutoCAD’s Support folder into BricsCAD’s. Both files matter, not just one.

LISP Files

BricsCAD runs standard AutoLISP .lsp files directly, no conversion needed, just copy them over. What it can’t run are AutoCAD’s own compiled, encrypted formats, VLX and FAS files; those need converting first.

Auto-loading files: AutoCAD auto-loads acad.lsp and acaddoc.lsp. BricsCAD’s equivalents have different names: on_start.lsp and on_doc_load.lsp. Don’t edit the on_start_default.lsp or on_doc_load_default.lsp files that ship with BricsCAD; create your own on_start.lsp and on_doc_load.lsp instead and put your custom content there.

By default these load once per session; setting the ACADLSPASDOC system variable to 1 loads them per drawing instead, matching AutoCAD’s behaviour. You can also load LISP routines manually via the APPLOAD command, which lets you set files to auto-load in future sessions too.

Converting VLX and FAS files: These need recompiling from their original .lsp source using DEScoder.exe, found in the BricsCAD installation folder. Open the encoder, select your source LISP file, click the convert button, then copy the resulting DES file into BricsCAD’s Support folder.

Check everything loaded correctly by typing (vl-list-loaded-lisp) in the command line.

Migrating Between BricsCAD Versions

This works differently to migrating from AutoCAD. The first time you launch BricsCAD after an update, it automatically compares your custom files against the UserDataCache folder from the new installation. If your existing files are newer, a dialog appears letting you choose to keep them or overwrite them with the new defaults, no manual copying required.

If you’d rather migrate specific files manually instead, the same file-by-file steps above apply, just between two BricsCAD installations rather than AutoCAD and BricsCAD.

Frequently Asked Questions

Can I migrate my entire AutoCAD ribbon or menu setup at once? Only partial customization files, not the main CUI or CUIX file itself. A full one-to-one interface migration isn’t supported the way individual file types are.

Why can’t BricsCAD load my compiled AutoCAD LISP routines? VLX and FAS are AutoCAD’s own proprietary compiled formats. You’ll need the original .lsp source and BricsCAD’s DEScoder tool to convert them into a format BricsCAD can use.

Do I need to do anything manually when upgrading between BricsCAD versions? Not necessarily. BricsCAD checks for newer custom files automatically on first launch after an update and prompts you to keep or overwrite them, though manual migration is still available if you’d rather control it yourself.

How do I confirm a migrated file actually worked? Each type has its own quick check: run LINETYPE for linetypes, HATCH for patterns, click More on the Start page for templates, PLOT for plot styles and plotters, and type (vl-list-loaded-lisp) in the command line for LISP files.