Convert .mdb to .gdb without the use of desktop or microsoft access

[sophered]

Hello! I need help creating a tool that can be used for converting Personal Geodatabases to File Geodatabase. Our organization no longer has access to Microsoft Access and, as we know, ArcMap is going away soon so we would like to find a solution that does not involve either.

I have tested with a few different scripts, utilizing arcpy in an ArcGIS Pro Notebook, however, it doesnt seem to recognize that there are even feature classes within the mdb so these scripts have not worked. The mdb that I am utilizing contains both feature classes and tables and I need all to be transferred over into an fgdb.

Please let me know of any solutions that would work! I am willing to part from the ArcGIS Pro Notebook and instead use Jupyter or even just a py file. It looks like this is an issue that MANY people have encountered and I have tried a lot of the approaches suggested on other posts. Any help is much appreciated!

[AyanPalit]

@sophered The easy method is to use ArcMap while it is still available and convert all Personal Geodatabases to File Geodatabase. A timeline should be defined for the transition as Personal Geodatabase is unsupported. 

Here are some available tools that saves you from coding: Migrating Data: Tools to migrate a personal geodatabase to a file or mobile geodatabase

[sophered]

@AyanPalit Unfortunately, we're looking into methods that don't involve the use of ArcMap. Whilst it is certainly the easy route, we're trying to explore other routes just in case. I do not mind taking a coding approach, however, the scripts that I have tried so far do not work. 

[RhettZufelt]

you can use arcpy.management.CopyFeatures to do this as long as you use the 2.7.x version that shipped with ArcMap.

R_

[KimOllivier]

Use FME. That will work forever, they never deprecate earlier readers. It is also called Data Interop for the Esri addon if you want to pretend that it is an Esri extension.

[PROBERT68]

I agree with KimOlliver to use FME.  I don't know if there is a way around in ArcGIS Pro.