Convert MDB to DWG

A survey, asset, or GIS application may deliver geometry and attributes in an .mdb database while the recipient needs an editable drawing for AutoCAD, Civil 3D, or another DWG-based system. Conversion is required to turn database features into CAD entities; changing the extension does not perform that conversion.

What the MDB format is

In CAD and GIS workflows, MDB usually identifies one of two database types: a Microsoft Access database or an Esri Personal Geodatabase. Both use relational tables, but neither is inherently a CAD drawing.

An Access MDB can contain coordinate tables, vertex records, layer names, units, asset identifiers, and project metadata. An Esri Personal Geodatabase stores feature classes with geometry, attributes, indexes, and geodatabase information. Older ArcGIS and some survey, asset-management, and GIS systems commonly use the Personal Geodatabase format.

The database type must be identified before conversion. An ordinary Access table with X and Y columns is not equivalent to a spatial feature class, and a Personal Geodatabase should be opened with software that supports its Esri structure rather than treated as an arbitrary Access table.

What the DWG format is

DWG is the native drawing format associated with AutoCAD and is supported by applications including Civil 3D, Map 3D, BricsCAD, and DraftSight. It stores editable CAD entities such as points, lines, polylines, arcs, blocks, text, dimensions, layers, and, depending on the application, 3D solids or civil objects.

DWG is useful for drafting, measurement, plotting, external references, and exchange with engineering and architectural CAD systems. It preserves drawing geometry more directly than PDF or raster export, but it does not preserve Access forms, queries, database relationships, geodatabase topology, or every GIS feature type.

How to convert an MDB database to DWG

FME Form for mixed Access and GIS data

1. Make a copy of the source file and determine whether it is an Access database or an Esri Personal Geodatabase. Use Microsoft Access for ordinary Access files; use ArcGIS software or FME inspection tools for Esri geodatabases.
2. Inventory the source before building the export. Record feature classes or tables, geometry types, coordinate reference system, units, elevation fields, feature identifiers, vertex order, layer fields, and tables that contain attributes without geometry.
3. In FME Workbench, add the matching reader: Microsoft Access for Access tables or the appropriate Esri Personal Geodatabase reader for an Esri MDB. Select only the required tables or feature classes.
4. Add an Autodesk AutoCAD DWG writer and select the DWG version required by the recipient. Map points, lines, polygons, and annotation to separate CAD layers or destination feature types.
5. Use FME transformers to reproject coordinates, assign layer names, map elevation values, construct geometry from coordinate records, and convert unsupported curves or polygons to linework when necessary.
6. Run the workspace and open the result in AutoCAD, Civil 3D, Map 3D, or a compatible viewer. Check the coordinate location, units, layer assignments, elevations, text, closed boundaries, and exported feature count against the source.

FME Form is the most flexible desktop option when the MDB contains mixed tables, spatial features, coordinate transformations, or attribute mappings. Its database readers and DWG writer may require specific licenses, drivers, or Windows components.

ArcGIS export for a Personal Geodatabase

When the MDB is an Esri Personal Geodatabase and its feature classes open correctly in ArcGIS, add the required layers and run Geoprocessing → Export To CAD. Choose a DWG output version, select the input feature classes, and configure CAD layer fields or output properties as required by the target application.

This method is preferable to treating an Esri geodatabase as a collection of generic Access tables because ArcGIS can read its feature classes and spatial metadata. Confirm that the installed ArcGIS product and version support the Personal Geodatabase and the required DWG output format.

Access tables and AutoCAD-based alternatives

AutoCAD by itself does not convert an MDB database into a drawing. AutoCAD Map 3D may connect to compatible database or spatial sources through available FDO or ODBC providers, and Civil 3D can import particular survey and point-table structures. The exact command depends on the schema, provider, and installed product.

If an Access table contains only coordinates, create explicit features before writing DWG. Points require coordinate fields; lines and polygons additionally require a feature ID, vertex sequence, grouping rules, and, for polygons, boundary closure. A converter cannot infer whether successive rows form one line, several features, or unrelated points.

Online converters

There is no generally reliable, schema-aware public service for direct MDB-to-DWG conversion. Services such as CloudConvert and Zamzar may support some database or CAD conversions, but their advertised format lists do not establish that they can read Access tables or Esri Personal Geodatabases and generate correctly mapped DWG entities.

Use an online service only when it explicitly lists the exact MDB type and DWG output and the data is not confidential. A safer online workflow is to perform the database interpretation and geometry construction locally, export to a supported intermediate vector format, and use an online GIS converter only when its documented input, output, coordinate-system handling, and privacy terms meet the project requirements.

Quality and compatibility limits

• Coordinate reference systems: Identify the source CRS and reproject it explicitly when necessary. An unknown or incorrect datum or projection can displace otherwise valid geometry by a large distance.
• Database semantics: Relationships, queries, forms, domains, topology rules, attachments, and many geodatabase behaviors do not transfer to DWG. Export needed values as attributes, object data, blocks, or text only when the receiving CAD workflow supports them.
• Geometry: Curved, multipart, 3D, raster, annotation, and GIS-specific features may be simplified or converted. Confirm how the chosen writer represents each type.
• Units and elevation: DWG does not automatically correct inconsistent source units. Map elevation fields deliberately and verify vertical units separately from horizontal units.
• Version compatibility: Select a DWG release supported by the recipient. A newer AutoCAD version may require a separate save operation before an older CAD application can open the file.
• Validation: Compare extents, feature counts, sample coordinates, layer names, labels, and closed boundaries after export. A DWG that opens successfully can still contain incorrect geometry or scale.