Complete guide to migrating custom files from AutoCAD to BricsCAD

1. Overview of custom files to migrate and their paths

BricsCAD uses a variety of files that store your personal settings, customizations, profiles, and application data to assist you in creating your drawings.

File type Extension Found in Path
Partial customization files
  • CUI or CUIX
  • MNU
  • RSZ
 Support folder
  • Windows: %AppData%\Bricsys\BricsCAD\V26x64\en_US\Support
  • Mac: /Users/<UserName>/Library/Application Support/Bricsys/BricsCAD/<Version>/en_US/Support
  • Linux: /home/<UserName>/Bricsys/BricsCAD/<Version>/en_US/Support
Linetypes LIN
Hatch patterns PAT
Tool palettes
  • XTP
  • XPG
  • ATC
  • BTC
Command aliases PGP
Shape files SHP
Drawing templates DWT Templates folder
  • Windows%LocalAppData%\Bricsys\BricsCAD\V26x64\en_US\Templates
  • Mac: /Users/<UserName>/Library/Application Support/Bricsys/BricsCAD/<Version>/en_US/Templates
  • Linux: /home/<UserName>/Bricsys/BricsCAD/<Version>/en_US/Templates
Plot files Plot Styles
  • CTB
  • STB
 PlotStyles folder
  • Windows:%AppData%\Bricsys\BricsCAD\V26x64\en_US\Support\PlotStyles
  • Mac: /Users/<UserName>/Library/Application Support/Bricsys/BricsCAD/<Version>/en_US/PlotStyles
  • Linux: /home/<UserName>/Bricsys/BricsCAD/<Version>/en_US/PlotStyles
Plot Config
  • PC3
  • PMP
 PlotConfig folder
  • Windows:%AppData%\Bricsys\BricsCAD\V26x64\en_US\Support\PlotConfig
  • Mac: /Users/<UserName>/Library/Application Support/Bricsys/BricsCAD/<Version>/en_US/PlotConfig
  • Linux: /home/<UserName>/Bricsys/BricsCAD/<Version>/en_US/PlotConfig
LISP files LSP Support folder
  • Windows:
  • Windows:%AppData%\Bricsys\BricsCAD\V26x64\en_US\Support
  • Mac:
  • Mac: /Users/<UserName>/Library/Application Support/Bricsys/BricsCAD/<Version>/en_US/Support
  • Linux: /home/<UserName>/Bricsys/BricsCAD/<Version>/en_US/Support
Note:

Use the SETTINGS command to configure how BricsCAD locates and loads custom files. In the Settings dialog, you can define all support file paths, including folders for linetypes, shapes, fonts, Xrefs, plotters, and other resources required during migration.

Use the CUSTOMIZE command to modify how BricsCAD user interface behaves. In the Customize dialog box, you can change the actions of interface elements such as menus, ribbons, toolbars, and mouse buttons, ensuring that migrated custom files are properly integrated into your workspace.

Manual migration of custom files
Use the manual migration method when you want to transfer specific customization resources from AutoCAD®, a previous BricsCAD version, or BricsCAD installed on a different computer. Manual migration involves locating, copying, and loading individual customization files to the current BricsCAD installation.

2. Migrating custom files

2.1 Migrating partial customization files

CUI or CUIX files can load and save full or partial custom workspaces. Only partial customization files should be migrated. Loading a partial CUI file adds custom menus, toolbars, ribbon elements, and other interface customizations to the existing user interface. When you install BricsCAD, the default CUI file is copied to the Support folder.

Note:
  • A CUIX file is a zipped package that contains all files required by the user interface. When loaded, it is automatically converted to a CUI file. Bitmap resources contained in a CUIX file are copied to a .RESZ resource file, which can be used as an alternative to a resource DLL. Supported image formats include BMP, JPG, PNG, ICO, GIF, TIFF, XBM, and XPM.
  • When migrating a partial customization file, make sure that any referenced support files, custom icons, scripts and LISP routines are also transferred and that their file paths are correctly configured in BricsCAD.
To migrate, load the desired partial customization files in BricsCAD using the CUSTOMIZE command.

Go to AutoCAD® and launch the CUSTOMIZE command. On the Transfer tab, select the desired partial CUI file from the drop-down list and save it.

Then, go to BricsCAD and launch the CUSTOMIZE command to open the Customize dialog box. From the File menu, choose Load partial CUI file... to open the Choose a customization file dialog box. Select and load the desired partial customization file.

2.1 Migrating custom linetypes

LIN files store linetype definitions. BricsCAD provides two default LIN files that you can customize: default.lin for imperial linetypes and iso.lin for metric linetypes. To migrate custom linetypes, copy the required linetype definitions from these files. You can also store custom linetypes in a separate LIN file and load it in BricsCAD.

Note: If your custom linetypes contain custom text or symbols, make sure to copy the required SHX files (font SHX or shape SHX) along with the copied linetype definition or LIN file. BricsCAD needs these SHX files in its Support File Search Path (SRCHPATH system variable) to display the linetype correctly. Standard SHX fonts are included in BricsCAD, so you only need to copy custom SHX files. It is recommended to store the custom SHX files in BricsCAD Support folder.

To migrate custom linetypes, locate each file, copy the custom linetype definitions or the custom LIN file, and save them in the corresponding BricsCAD file.

Migrating imperial or metric custom linetypes
Go to AutoCAD® Support folder and open in a text editor the acad.lin file for imperial custom linetypes or the autocadiso.lin file for metric custom linetypes. Scroll down to the User Defined Linetype section, select the definition of the custom linetype and copy it.

Then, go to BricsCAD Support folder and open in a text editor the default.lin file for imperial custom linetypes or the iso.lin file for metric custom linetypes. Paste the definition of the custom linetype at the end of the file, then save and close it.

After migration, use the Load Linetypes dialog box to load the linetypes in BricsCAD.

Migrating custom LIN files
Go to BricsCADand run the LINETYPE command. Choose New to open the Load Linetypes dialog box and import your custom LIN file.

It is recommended to store the custom LIN files in BricsCAD Support folder.

2.3 Migrating custom hatch patterns

PAT files store the definition of the hatch patterns. There are two default PAT files, one for imperial hatch patterns and another for ISO hatch patterns. Custom hatch patterns can also be stored in an alternative PAT file.

To migrate custom hatch patterns, locate each file, copy the custom hatch patterns definitions or the custom PAT file, and save it in the corresponding BricsCAD file.

Migrating imperial or metric custom hatch patterns
Go to AutoCAD® Support folder and open in a text editor the acad.pat file for imperial custom hatch patterns or the acadiso.pat file for metric custom hatch patterns. Scroll down to the User Defined Hatch Patterns section, select the definition of the custom hatch patterns and copy it.

Then, go to BricsCAD Support folder and open in a text editor the default.pat file for imperial custom hatch patterns or the iso.pat file for metric custom hatch patterns. Paste the definition of the custom hatch patterns at the end of the file, then save and close it.

Migrating custom PAT files
Copy and store the custom PAT files as needed. To migrate them in BricsCAD choose one of the following:
  • (Recommended) Go to BricsCAD Support folder and save there the custom PAT files.
  • Add the location of your custom PAT files to the Support file search path section in the Settings dialog box (SRCHPATH system variable).

2.4 Migrating custom drawing templates

Drawing templates are DWT files that stores settings specific to the drawing and project requirements, such as units, layers, styles, layouts, etc.

To migrate custom drawing templates, locate each file, copy and save it in the corresponding BricsCAD folder.

Go to AutoCAD® and launch the OPTIONS command. Click the Files tab, go to the Template Settings section to find the location of the drawing template file and copy the files.

Then, go to BricsCAD and launch the TEMPLATEFOLDER command to open the folder where the drawing template files are stored. Paste the files.

2.5 Migrating custom plot files

Custom plot styles are stored in CTB or STB files. Plotter configurations are stored in PC3 files, and plotter model parameters associated with a PC3 are stored in PMP files.

Note:
  • CTB and STB files are fully compatible. A drawing can use either CTB or STB plot styles, so the plot style table is displayed based on the current drawing plot style mode (see the CONVERTPSTYLES command article).
  • In BricsCAD, PC3 plotter configuration files are supported only for Windows system printers, while AutoCAD® supports additional printer configuration types.
  • Some PC3 configurations also require their associated PMP file when migrated.

To migrate custom plot files, locate each file, copy the files and save them in the corresponding BricsCAD file.

Migrating Color-Dependent Plot Style Table (CTB) or Named Plot Style Table (STB)
Go to AutoCAD® and launch the STYLESMANAGER command to open the Plot Styles folder and copy the files.

Then, go to BricsCAD and launch the STYLESMANAGER command to open the PlotStyles folder and paste the files.

Migrating Plotter Configuration File (PC3)
Go to AutoCAD® and launch the PLOTTERMANAGER command to open the Plotters folder and copy the files.

Then, go to BricsCAD and launch the PLOTTERMANAGER command to open the PlotConfig folder and paste the files.

Migrating Plotter Model Parameters (PMP)
Go to AutoCAD® and launch the PLOTTERMANAGER command to open the Plotters folder. Open the PMP Files folder and copy the files.

Then, go to BricsCAD and launch the PLOTTERMANAGER command to open the Plotters folder. Open the PMP Files folder and copy the files.

After migration, launch the PLOT or PRINT command to open the Print dialog box. Choose the associated Printer / Plotter configuration, then click the Manage Custom Sizes option. The Open modified paper sizes data file dialog box opens, allowing you to select the PMP files you want to attach.

2.6 Migrating custom tool palettes

BricsCAD supports importing tool palettes from XTP, ATC and BTC files, and tool palette groups from XPG and BWS files. Tool palettes can be exported to BTC files, and tool palette groups to XPG files.

BricsCAD stores tool palettes in BTC files and indexes all existing palettes in the BcTpCatalog.btc file. When you create or import a new palette, BricsCAD updates the catalog and automatically generates a separate BTC file that contains the palette’s content. All palette files are stored in the default Tool Palettes folder inside the Support directory.

Note: If your custom tool palettes reference external resources, including hatch pattern files, images, linetypes or other support files, these resources must be migrated separately to ensure that all palette tools remain functional after migration.

To migrate custom tool palettes, export each file and import it into BricsCAD.

Go to AutoCAD® and launch the TOOLPALETTES command to open the Tool Palettes panel. Right-click the panel and choose Customize Palettes... to display the Customize dialog box. Then, right-click the custom palette or palette groups you want and select the Export... option to open the Export Palette or Export Group dialog box. Save the custom palette file as an XTP file or the custom palette group as an XPG file.

Then, go to BricsCAD and launch the TOOLPALETTES command to open the Tool Palettes panel. Right-click the panel and choose Customize Palettes... to display the Customize dialog box. Then, right-click any palette or palette group and select the Import option to open the Import Palette or Import Palette Group dialog box. Choose the XTP or XPG file you want to import.

Note: Tool Palettes can contain various tool types. During migration, some tool types may not be supported.

2.7 Migrating custom command aliases

Command aliases are alternative names for commands, and they are saved in a PGP file.

To migrate custom command aliases, locate each file, copy the custom command aliases definitions, and save them in the corresponding BricsCAD file.

Note: Make sure there are no conflicts between the migrated custom aliases and those already used by BricsCAD.

Go to AutoCAD® Support folder, open the acad.pgp file in a text editor and scroll down to the User Defined Command Aliases section. Select the definition of the custom command aliases and copy it.

Then, go to BricsCAD Support folder and open the default.pgp file in a text editor. Paste the definition of the custom command aliases at the end, save the file, and exit.

2.8 Migrating custom shape files

SHX files store the definition of the fonts and SHP files store the definition of the shapes. These files are usually stored in the Support folder.

To migrate custom command aliases, locate each file, and copy both the SHP and SHX files to the BricsCAD Support folder.

Go to AutoCAD® Support folder and copy both the SHP and SHX files.

Then, go to BricsCAD Support folder and paste the SHP and SHX files.

2.9 Migrating LISP files

LISP (List Processing) is an interpreted programming language used to automate tasks, create custom commands, and extend BricsCAD functionality. LISP routines can interact with BricsCAD commands, system variables, dialog boxes, and drawing entities.

BricsCAD is compatible with AutoCAD® AutoLISP, so it can load and run LSP files. However, the VLX and FAS file formats are AutoCAD® specific encrypted LISP files, and BricsCAD cannot load such files.

To migrate LISP routines, locate the desired LSP files, then copy and save them in the corresponding BricsCAD file. LISP files are usually stored in the Support folder (from the installation folder) but can also be stored in a folder added to the support search path using the SRCHPATH system variable.

Note: Make sure that all dependent resources, such as DCL files, scripts, custom icons and configuration files, are also transferred and that any referenced file paths are updated accordingly.

Two LISP files are automatically loaded in AutoCAD® from acad.lsp and acaddoc.lsp. The equivalents of these two files on BricsCAD are on_start.lsp and on_doc_load.lsp.

Important: It is not recommended to edit on_start_default.lsp and on_doc_load_default.lsp. Instead, you should create two new files named on_start.lsp and on_doc_load.lsp.
Migrating ACAD.LSP into ON_START.LSP
Go to AutoCAD® Support folder and open in a text editor the acad.lsp file. Select the custom content and copy it.

Then, go to BricsCAD Support folder and create a new text editor file named on_start.lsp. Paste the custom content and save it.

Migrating ACADDOC.LSP into ON_DOC_LOAD.LSP
Go to AutoCAD® Support folder and open in a text editor the acaddoc.lsp file. Select the custom content and copy it.

Then, go to BricsCAD Support folder and create a new text editor file named on_doc_load.lsp. Paste the custom content and save it.

Migrating encrypted VLX files, FAS files, VLX projects (PRV) and FAS projects (PRJ)
Compiled and encrypted VLX and FAS files cannot be loaded in BricsCAD. Migration of VLX and FAS based applications requires access to the original LISP source files and the PRV or PRJ project files.

BricsCAD supports the creation of encrypted applications through DEScoder.exe. Using DEScoder.exe, multiple LISP, DCL, and other application resource files can be packaged and encrypted into a single DES application file. PRV and PRJ project files are used to define the application contents and generate the encrypted DES file.

  • After migration, the on_start.lsp is loaded per session by default, but it can also be loaded for each drawing if the ACADLSPASDOC system variable is set to 1. The on_doc_load.lsp file is always loaded for each drawing.
  • Another way to load your LISP routines is with the APPLOAD command. After you run the command, the Load Application Files dialog box is displayed to select the application files you want to run inside BricsCAD. The AutoLoad option specifies whether a file is loaded automatically or not in the next BricsCAD session (see the Load Application Files dialog box article for more information).

The path of the DES Encoder is: C:\Program Files\Bricsys\BricsCAD V26 en_US.

  1. Open the encoder.
  2. Select the LISP file in the Source field.
  3. Click the Convert selected source Lisp file into DES encrypted file button next to the Target field.
  4. After the DES file is converted, copy it to BricsCAD Support folder (from the installation folder): %AppData%\Bricsys\BricsCAD\V26x64\en_US, or to a folder you have added to the support path using the SRCHPATH system variable.