Convert personal geodatabase data (.mbd) to file geodatabase (.gdb) feature classes

Summary

The personal geodatabase (.mdb) data model was developed by Esri, based on the 32-bit Access database from Microsoft for use in ArcGIS Desktop and ArcMap to fill the need for a lightweight, flexible geodatabase that stores feature geometry and  complex relationships, as well as tabular data.

This data model has been in use for more than two decades and has been of great value during it's useful life.

With the introduction of the 64-bit ArcGIS Pro application, the 32-bit personal geodatabase is no longer supported in the next generation software with the new more flexible and powerful software program.

The urgent question arises on how to extract data from the personal geodatabase and write that data to the file geodatabase data model.

Procedure

There are currently three approaches to resolve this issue. 

• The Data Inteoperability Extension for ArcGIS Pro includes the Quick Import tool in ArcToolbox.  This tool, starting with ArcGIS Pro version 3.5, converts the feature classes from the original personal geodatabase .mdb format to the file geodatabase .gdb format. There is additional cost associated with this extension. but if the extension is available this is a useful option.
• While ArcGIS Desktop (ArcMap) is still available, from ArcCatalog in the Catalog tree, right-click each personal geodatabase feature class, and Export each feature classes from the .mdb to a shapefile.  Remember that a shapefile can only contain one feature type. Create one shapefile for each feature type; point, line, polygon, and annotation.  This also works for 3D data.
• Note that if the client has annotation in the personal geodatabase format, that annotation can also be "rescued" in ArcCatalog or in ArcMap. The steps are as follows:

1. 1. Right-click the annotation feature class in the Catalog tree.
   2. Select Export > Shapefile.
      This creates a polygon shapefile with the annotation text in the TEXTSTRING field.  The Font, Font Size, Angle and other properties of the orginal text are preserved in the attribute table for each polygon so the annotation can be re-created.  The client can then import the shapefile to a file geodatabase feature class and re-create the annotation from the attribute.