May 26

How to Set Up a New Microvellum Configuration from an Export

Get Our Starter Configuration Here!
Subscribe to download the DuckWorks Starter Config used in this guide:
👉 Subscribe & Download

If you’ve received exported files from a client or team and need to set up a new Microvellum configuration, this tutorial outlines every step. You’ll learn how to configure a clean environment, copy over files, adjust link IDs, and verify the setup—all based on DuckWorks’ internal standards.

What You’ll Need

  • A starter configuration (e.g., DuckWorks Starter Configuration)
  • Microvellum SQL CE Viewer (Download it here)
  • Exported files from your client (e.g., Clipboard, Drawing Template, Graphics, Database Exports folders)

1. Check the Link ID of Your Base Library

Before importing anything, you need to check and update the Link ID of your starter configuration to avoid conflicts when importing a new library.

  1. Open the MicrovellumFactory.sdf file from your base config in SQL CE Viewer.
  2. Go to the Libraries table.
  3. Confirm the current Link ID (e.g., 1234dw) and change it if necessary.
  4. Double-click the Link ID cell to modify it.

2. Copy Over Exported Files

Now, take the data from your client and copy it into your starter config folders:

  • Clipboard
  • Drawing Template
  • Graphics

đź“ť Choose to replace files if prompted.

3. Open Microvellum and Copy the Starter Configuration

  1. Launch Microvellum.
  2. Go to Manage Configurations.
  3. You can either import the starter configuration or copy and existing one. 
  4. Launch the new configuration. 
  5. If you have copied an existing configuration, go to Toolbox Setup > Options > Utilities > Change path to Microvellum data. And browse to the new configuration folder in the location you have placed it in (typically C: drive) 

4. Import the Library

In the new configuration:

  1. Go to Toolbox Setup > Database Utilities > Import.
  2. Navigate to your export folder > Database Exports.
  3. Select the .exp file
  4. When prompted to “select all records,” choose No.
  5. Select only Library, deselect everything else.
  6. Click Transfer, then OK.

5. Restart Microvellum

After importing the library, restart Microvellum to refresh the configuration.

  1. Upon restart, check that the new library appears as the current one (not the DuckWorks Starter).

6. Import Additional Components in Batches

Repeat the import process to bring in other configuration elements. Do this in separate steps to avoid crashing:

  • Products
  • Subassemblies
  • Materials
  • Reports
  • Processing Station & Tool Files
  • Projects

đź’ˇ Pro tip: For large datasets (e.g., thousands of materials), import in batches.

7. Verify Link ID Match Between Configurations

Now double-check that the imported library link ID matches the one from your client’s configuration.

  1. Open both .sdf files (your factory database and your client’s export) in SQL CE Viewer. 
  2. Compare the Library Link ID between the two.
  3. They must match exactly for exports to work correctly.

8. Replace the Factory Workbook

The F Workbook doesn’t import automatically—you’ll need to replace it manually.

  1. In SQL CE Viewer, go to Factory > Workbook.
  2. Right-click > Import File from Disk.
  3. Select F Workbook.xlsx from your export folder.
  4. After importing, right-click and select Update.

9. Import Specification Group Files

  1. Go to Options > Database Explorer in Microvellum.
  2. Navigate to:
    • Imperial Component Library > Specification Groups
  3. Locate the spec group files from your export.
  4. Drag and drop them into the corresponding folder in Database Explorer.
  5. Confirm overwrite or merging if prompted.

10. Restart and Finalize the Configuration

  1. Close and restart Microvellum. 
  2. Go back to “Configuration Manager” from the start menu, export the newly created configuration .mvg 
  3. A .mvg config file will now appear in your configuration folder folder (e.g., C:\ProgramData\Microvellum\Config\). 
  4. This file can now be shared with others for quick setup. 

11. Validate the Configuration (Highly Recommended)

Before sharing your configuration:

  1. Create a test project using the new config.
  2. Add products, generate elevations and sections.
  3. Export the project.
  4. Have your client test the export to confirm:
    • All prompts function
    • No broken components
    • Everything appears as expected

Summary Checklist

  • Starter config copied and renamed
  • Exported files copied (clipboard, templates, graphics)
  • Link ID checked and matched
  • Library and components imported
  • F Workbook replaced
  • Spec group templates added
  • Project tested and verified

Need Help?

If anything breaks along the way or you run into compatibility issues, reach out to the DuckWorks team—we’re happy to help.

Nicolae Cespedes – Director of Operations