The Microvellum BricsCAD Transition: What Shops Need to Know

Microvellum stopped updating its OEM version, which embedded an AutoCAD engine, after July 20, 2025. Its replacement, released July 21, 2025, is Microvellum BSB, which bundles the software with BricsCAD Pro. Microvellum AC, which runs on full AutoCAD, remains supported. Microvellum says existing projects, libraries and configurations work in BSB without migration, though some CAD commands behave differently.
- What changed
- OEM updates ended July 20, 2025; the BricsCAD bundle (BSB) shipped July 21, 2025
- Who is affected
- Shops on the OEM version; Microvellum AC users on full AutoCAD are not
- Your library
- Microvellum says it carries over without migration; test it on real jobs anyway
For years, many Microvellum shops ran the OEM version of the software, which came with an AutoCAD engine built in. In July 2025 Microvellum ended development of that version and released a replacement built on BricsCAD. The change affects licensing, daily drafting habits and anyone who exchanges Microvellum data with an outside party. It does not change how your products are built.
This guide summarizes what Microvellum has published about the transition, separates what is confirmed from what you should verify for your own account, and lays out a test plan. Vendor terms change, so treat the dates and conditions below as a starting point and confirm them with your Microvellum account manager.
What actually changed
Microvellum is woodworking design and manufacturing software that runs inside a host CAD program. Until 2025 there were two common ways to run it: on a full AutoCAD installation, or as the OEM version with an embedded AutoCAD engine. The software itself was called Toolbox for most of that time. Microvellum's help center notes that it was rebranded simply as Microvellum in 2025, so older articles say Toolbox BSB and newer ones say Microvellum BSB for the same product.
According to Microvellum's announcement and its published FAQ:
- Development of the OEM version ended on July 20, 2025. After that date it receives no updates, and full installation files are no longer distributed.
- Microvellum BSB was released on July 21, 2025. It is a single installation that includes a licensed copy of BricsCAD Pro together with Microvellum.
- Microvellum AC, the version that runs on full AutoCAD, continues to be supported. Shops already on AC are not required to do anything.
- A later release, BSB 2026, moved the bundle to BricsCAD Pro 2026 and is included for existing BSB subscribers.
Microvellum describes the move as part of a CAD-agnostic strategy and a way to widen the CAD options for its users. BricsCAD is a professional CAD program from Bricsys that uses DWG as its native file format and shares most of AutoCAD's command structure.
The options for an OEM shop
If your seats are OEM, you have three realistic paths.
Stay on OEM for now
Microvellum states that existing OEM installations keep working and that you are not required to convert. The risks it names are practical ones: if you lose your installation files, reinstalling may be difficult or impossible, and you receive no further fixes or features. Microvellum also warns that an unmaintained version will eventually become incompatible. Staying put is a short-term position, not a plan.
Convert to Microvellum BSB
This is the route Microvellum built for OEM users. It offers a 45-day trial through its customer portal, which can be extended by a further 45 days, and allows OEM and BSB to be installed side by side during evaluation. Conversion is handled by a portal administrator.
Move to Microvellum AC
If your team prefers to stay in AutoCAD, AC remains available. Microvellum states that AC requires your own AutoCAD subscription, purchased from Autodesk, so the CAD cost moves to a separate line.
One further point: Microvellum's FAQ says that installing its software on a BricsCAD license bought directly from Bricsys is not currently supported and is planned for a future release. If you already own BricsCAD seats, ask Microvellum for the present status before you assume they can be used.
Licensing questions to settle
We are not going to quote prices, because they depend on your seat count and agreement. These are the points Microvellum has published and the questions worth asking in writing.
- Conversion cost. Microvellum's FAQ describes the OEM-to-BSB conversion as having no out-of-pocket cost for existing licenses if completed within an 18-month window from the release, with existing maintenance fees applied toward the BSB subscription. One version of that FAQ gives January 10, 2027 as the end of the window and says price increases may apply afterward. Confirm the date that applies to your account.
- Subscription versus perpetual. Microvellum states that modules you bought under a perpetual model remain yours, and that the component that becomes a subscription is the bundled CAD platform. Ask what happens to that platform license if maintenance lapses.
- Added seats. New users or a higher seat count carry additional charges. Get a quote for the number of seats you expect to run in two years, not only today.
- Remote environments. Microvellum states that BSB is not compatible with Windows Remote Desktop Services environments, though a standard remote connection to an individual workstation is not affected. If your drafters work through a terminal server, raise this before converting.
What carries over
Microvellum's published position is that the transition requires no database migration. Specifically, it states that:
- Existing projects, library data, databases and configuration files created in OEM work in BSB without changes.
- Tokens and machining tools function in BSB as they do in OEM, so engineering and production workflows are unchanged.
- Templates, layers, block libraries, linetypes and dimension styles are DWG content and typically need no conversion.
- Existing interface customization (CUI) files can be imported so toolbars and shortcuts can be rebuilt quickly.
- Open projects do not have to be finished first; you can open a job in BSB and continue.
That is reassuring, and it matches what you would expect when the manufacturing logic lives in Microvellum and its database, not in the CAD engine. It is still a vendor statement about libraries in general. Your library has years of local edits in it. The only evidence that counts for your shop is your own jobs producing the same parts, which is what the test plan below is for.
What behaves differently
Microvellum maintains a help article listing the differences between OEM and BSB. Most are drafting-level, not manufacturing-level, but they are the things your drafters will hit on day one.
- PRESSPULL. In OEM it was possible to extrude the gap between two entities. Microvellum states this is not possible in BSB because the command works differently in BricsCAD, and it points to DMPUSHPULL as the alternative for solids.
- Design Center. AutoCAD's Design Center is not present. BricsCAD's Drawing Explorer covers layers, blocks, styles and similar content.
- MEASUREGEOM. The command is not natively available. DIST, AREA and LIST cover most of the same needs.
- Dynamic blocks. Existing dynamic blocks can be used as they are. Microvellum advises against modifying them in BSB if the drawing will go back to AutoCAD-based software, because edited definitions may no longer be compatible.
- PDF import. PDF underlays are handled differently by default, and a setting controls whether an imported PDF stays as a single reference.
- Fonts. Some older templates reference fonts that do not exist in BricsCAD and trigger a missing-font notice. Microvellum's article describes updating the library template or reassigning the text style.
- Import and export formats. Microvellum says BSB does not support exactly the same set of formats as OEM by default. If you routinely receive STEP or other 3D files from designers, check the current format list.
There are gains as well. Microvellum notes that AutoLISP routines and Express Tools, which were not included in OEM, are available in BSB.
A test plan before you convert
Use the trial period for a structured comparison, not a tour of the interface.
- Back up first. Copy your configuration, library data and databases, and store your current OEM installer somewhere safe.
- Bring OEM to its final build. Microvellum recommends installing and testing the last OEM build first, so that any differences you see afterward come from the CAD platform and not from a version jump.
- Pick three or four representative jobs. Include standard casework, a job with heavy custom products, and one with imported architect backgrounds and PDF underlays.
- Process each job in both environments. Compare cut lists, material and hardware reports, nest results and the machine code itself. A file comparison of the G-code is more reliable than a visual check.
- Run the drawing set. Regenerate 2D views, plot to PDF, and compare title blocks, dimension styles, fonts and lineweights against a set you have already issued.
- Test your add-ons. List every LISP routine, custom block, plot style and third-party integration your team relies on and try each one.
- Cut something. Before production depends on BSB, run at least one small job on the machine from BSB output.
- Convert all workstations together. Microvellum states that workstations sharing data should be on the same software version, so plan a cutover date instead of a slow seat-by-seat drift.
Record what you find. A short written list of differences and workarounds is the most useful training document your drafters will get. If the drawing standard itself needs attention, our guide to commercial millwork shop drawings is a useful reference point.
Working with outside drafters
The transition adds one more thing to check when someone outside the shop works on your Microvellum jobs. A vendor on a different host or build is not automatically a problem, since the project data and DWG format are shared, but it needs to be stated up front.
- Tell the vendor which version you run (OEM, BSB or AC) and your current build number, and ask for theirs.
- If you are still on OEM, agree that dynamic blocks in your templates will not be edited in a BricsCAD-based environment.
- Ask for the first returned job to be opened and processed on your side before any others are released.
- Do not schedule your own cutover in the middle of a large outsourced job. Finish the phase or convert first.
Millmetric provides Microvellum drafting and also works in plain AutoCAD and BricsCAD, and these checks apply to us as much as to anyone. Whoever you use, the questions in our guide on how to vet a Microvellum drafting service apply, and the comparison in Microvellum vs Cabinet Vision vs AutoCAD may help if the transition has you reconsidering platforms altogether.
Frequently asked questions
Is Microvellum dropping AutoCAD?
No. Microvellum ended updates to its OEM version, which embedded an AutoCAD engine, after July 20, 2025. Microvellum AC, which runs on a full AutoCAD installation that you license from Autodesk, continues to be supported. The BricsCAD-based bundle, Microvellum BSB, is the replacement for OEM and an alternative to AC, not a replacement for it.
Will my existing Microvellum library and projects work in BricsCAD?
Microvellum states that projects, library data, databases and configuration files created in the OEM version work in BSB with no migration, and that tokens and machining tools function the same way. You should still verify this on your own jobs by processing them in both environments and comparing reports and machine code before converting.
Do I have to convert from Microvellum OEM to BSB?
No. Microvellum says existing OEM installations continue to function and conversion is optional. However, OEM no longer receives updates, installation files are no longer distributed, and Microvellum warns that incompatibilities will eventually occur. Most shops should plan a move to either BSB or AC instead of remaining on OEM indefinitely.
What works differently in Microvellum BSB compared with OEM?
Microvellum documents several CAD-level differences. PRESSPULL cannot extrude the gap between two entities, AutoCAD's Design Center is replaced by BricsCAD's Drawing Explorer, MEASUREGEOM is not available, and dynamic blocks edited in BSB may not remain compatible with AutoCAD-based software. BSB is also not compatible with Windows Remote Desktop Services environments.
Send the architectural drawings and specs. You get a fixed scope and price back within 24–48 business hours, before any drafting starts.
Get an Estimate →